Access Official Technical PDF

Share Summary:LinkedInEmail

Industrial automation software is increasingly expected to do more than control a single machine or process. Connected equipment, richer sensor data and more capable processors are bringing sophisticated computing closer to the point where operational data is generated. For automation engineers and system integrators, this shift makes the software foundation of an edge device an important part of system design—particularly when reliability, security and functional safety matter.

BlackBerry’s fiscal 2025 annual report describes this broader move toward the intelligent edge across industries including manufacturing, healthcare and robotics. Its QNX division supplies embedded software for industrial automation and other mission-critical applications. The filing also highlights several engineering themes relevant to automation projects: processing data locally, managing system complexity, separating workloads and supporting development against safety requirements.

Why industrial automation software is moving to the edge

Edge computing places processing capabilities within or near connected devices rather than relying solely on centralized systems. In an industrial setting, that can enable equipment to use local sensor data to make context-aware decisions. The annual report identifies reduced latency, enhanced security and efficiency as potential benefits of intelligent edge systems; it does not suggest that every application will realize the same outcomes.

The shift is supported by increased connectivity, more capable hardware and the growing availability of data from sensors and other devices. As embedded systems take on more work, software must help capture, process and interpret operational information while meeting the requirements of the application.

Software-defined devices can also be updated as needs change. That flexibility may help organizations adapt systems to evolving customer demands or industry requirements, but it increases the importance of a sound software architecture. Teams need to consider how updates, integrations and new functions will affect the complete system—not just the individual device receiving a change.

Foundational software for complex automation systems

Embedded operating systems, development tools and virtualization technologies form part of the software foundation for connected devices. A real-time operating system is designed for embedded applications in which predictable system behavior is important. For industrial automation teams, selecting foundational software is therefore connected to the intended use of the device, its operating environment and the consequences of a system malfunction.

As computing hardware and software stacks grow more sophisticated, multiple functions may need to run on shared hardware. A hypervisor can support the separation of systems or workloads. BlackBerry’s filing describes QNX Hypervisor for Safety as designed to prevent safety systems from being affected by malfunctions in other systems. In an automation architecture, this points to a broader design consideration: how functions are isolated and how dependencies between them are managed.

Virtualization and embedded platforms do not remove the need for system-level engineering. Integrators still need to evaluate interfaces, hardware dependencies, failure behavior and the specific safety and security requirements that apply to their application. The right platform is one that fits those requirements and can be maintained across the system lifecycle.

Functional safety and security belong in the design

Industrial devices may operate in applications where failures have consequences for equipment, production or people. The annual report identifies high-performance foundational software that maintains functional safety and security as an industry need as edge systems become more capable and complex.

For developers, safety considerations affect both the software platform and the process used to build the application. BlackBerry describes its QNX portfolio as including safety-certified software and tools intended to support compliance with standards such as ISO 26262, an automotive functional safety standard. This is an automotive example rather than an industrial certification claim, but it illustrates a general engineering point: safety requirements influence platform selection, software partitioning and development workflows.

Security also needs to be considered across device and network boundaries. Connected equipment can exchange data with other systems, so architecture decisions should account for how devices communicate and how unauthorized access could affect operation. The filing discusses security as a foundational concern for edge devices, alongside reliability and safety.

Reducing development friction without losing control

Software complexity can increase development effort, especially when applications must integrate multiple functions or accommodate changing hardware. BlackBerry identifies reducing developer friction as one of its QNX strategic priorities and describes development tools, pre-qualified toolchains and engineering services within its portfolio.

For automation teams, the practical aim is not simply to accelerate coding. A more manageable development environment can help teams build, test and maintain embedded applications while addressing the requirements of the target system. When assessing a platform, engineers and decision-makers can consider:

  • Application requirements: Determine the timing, availability, safety and security needs of the device.
  • Hardware strategy: Assess how software choices affect hardware dependencies and future changes.
  • System separation: Understand whether functions need to be isolated and how failures in one area could affect another.
  • Lifecycle support: Consider development tools, integration needs and how software will be maintained as requirements evolve.

These questions help connect platform decisions to operational objectives rather than treating embedded software as a component selected in isolation.

What the shift means for automation decision-makers

The growth of connected, software-defined equipment is extending the role of embedded software in industrial automation. Local processing can support responsive applications, while more capable devices also bring greater architectural complexity. Real-time behavior, functional safety, cybersecurity, workload separation and maintainability should therefore be considered together during system design.

For plant managers and technical decision-makers, the practical implication is to evaluate the software foundation alongside hardware, integration and lifecycle requirements. For engineers and system integrators, the task is to make those requirements explicit early and select platforms and development approaches that fit the application. As automation moves further toward the intelligent edge, disciplined software architecture will remain central to building systems that meet operational needs without overlooking safety, security or reliability.

Access Official Technical PDF

About The Author