Access Official Technical PDF

Share Summary:LinkedInEmail

Edge computing in industrial automation is part of a broader shift in how organizations process data, connect systems and apply software. A 2020 technology-sector outlook identified edge computing, cybersecurity and AI-as-a-Service as important developing trends. For automation engineers, integrators and operations leaders, these themes raise practical questions about where data should be processed, how connected assets should be secured and how advanced analytics can be applied to specific operational needs.

These technologies are not interchangeable, and none removes the need to assess an application’s requirements. Together, however, they point to an increasingly distributed and software-driven technology environment—one in which industrial systems may need to exchange data across devices, local infrastructure and cloud services.

Edge computing in industrial automation: processing closer to the source

Edge computing means processing data near the place where it is generated rather than sending it to a distant centralized location for every operation. The main rationale described in the report is reducing latency: applications that depend on timely data may be affected when information has to travel to a remote cloud environment and back.

Early edge deployments were associated with reducing bandwidth costs for Internet of Things devices over long distances. The report also highlights the growing importance of applications that need local processing and storage. In industrial settings, its examples of complex edge devices include robots, drones, autonomous vehicles and operational systems. These are systems for which processing location can matter to application performance.

Edge computing does not necessarily mean replacing cloud computing. The report frames their relationship as an open question: edge could be considered alongside private and public cloud options, rather than as a straightforward substitute. For system architects, the implication is to evaluate the requirements of each workload, including its need for local processing and its relationship to centralized services.

Infrastructure is only one part of the edge

Deploying servers and storage at the edge is one approach, but the report also points to the role of platforms. An edge environment may need applications and workloads that make use of the infrastructure, alongside integration, analytics, monitoring and security. This makes platform capabilities relevant to organizations planning how edge resources will fit into a wider system.

Industrial cybersecurity must adapt to greater connectivity

Cloud adoption, increased network connectivity, regulation and public spending initiatives, and increasingly complex cyberattacks were identified as drivers of cybersecurity demand. The report also notes that cloud, mobile, social media, IoT and big data have expanded the attack surface. As industrial operations become more connected, security planning must account for the systems, services and data flows involved—not only individual devices.

Another shift is from prevention-only strategies toward greater emphasis on detection and response. AI and data-driven security tools are described as ways to help identify issues before they can be exploited. At the same time, organizations may face a crowded collection of tools and alerts, creating challenges for teams responsible for triage.

The report describes a platform approach as one possible response: consolidating security capabilities within a more integrated ecosystem rather than relying on many disconnected tools. This is a direction, not a guarantee that a single platform will meet every organization’s needs. Automation and security teams still need to consider how tools fit together and how alerts can be managed.

AI-as-a-Service could make specialized applications more accessible

Many organizations were already exploring AI to improve customer experience and streamline business operations, according to the report. However, limited availability of qualified practitioners, immature tools and frameworks, and the time and cost involved in obtaining large datasets can make AI difficult to implement.

AI-as-a-Service offers one way to address some of these barriers. Rather than building every capability internally, an organization can use a service platform, provide its own data and pay for algorithms or computing resources as needed. The report observes that broad, horizontal platforms may still require custom engineering to address a particular business task.

It anticipated wider adoption of more specialized, vertical AI services designed for particular challenges. In an industrial context, the useful question is not simply whether a provider offers AI, but whether an application is tailored to the task and can support the processes required to create, deploy, manage and operate models. The report describes these lifecycle activities as part of scaling AI within an enterprise.

What technology acquisition trends may signal

The report also describes technology-related mergers and acquisitions as a way for organizations in different sectors to obtain capabilities. Acquisitions can be viewed as an alternative to developing technology internally, which may be slower or riskier. It notes a growing interest among technology companies in acquisitions that open new markets or expand customer bases, rather than deals focused only on acquiring technology.

For industrial decision-makers, this is useful context when evaluating a changing supplier landscape. A provider’s strategic direction, partnerships and market expansion may influence how its offerings develop. These factors do not establish whether a product is suitable for a particular plant, but they reinforce the value of assessing technical fit and the role a technology will play in the wider system.

Practical implications for automation teams

These trends point to several considerations for planning connected industrial systems:

  • Match processing location to the application. Assess whether a workload needs local processing and storage or can rely on a centralized environment.
  • Plan for integration. Consider how edge platforms, applications, analytics, monitoring and security will work with existing systems.
  • Account for detection and response. Evaluate how security tools handle alerts and support teams responsible for investigating them.
  • Define the AI use case. Identify the specific operational challenge before choosing between internal development and a service-based or specialized solution.

Edge computing, cybersecurity and AI-as-a-Service are best understood as connected parts of a changing technology landscape, rather than standalone answers to operational challenges. For industrial automation teams, the practical priority is to align processing, security and software choices with each application’s requirements. That approach can help decision-makers evaluate where these technologies may contribute—and what integration and operational considerations must be addressed.

Access Official Technical PDF

About The Author