Service-Oriented Architecture in Industrial Automation Systems - The case of IEC 61499: A Review

In the paper by W. Dai et al. (IEEE Trans. On Industrial Informatics, vol. 11, no. 3, pp. 771-781, June 2015), a formal model is described for the application of SOA in the distributed automation domain in order to achieve flexible automation systems. A service-based execution environment architecture based on the IEC 61499 Function Block model is proposed and a case study is used to demonstrate dynamic reconfiguration. In this letter, a review of the literature related to the use of SOA in Industrial Automation Systems is given to set up a context for the discussion of the proposed in the above paper SOA IEC61499 formal model. The presented, in the above paper, formal model and execution environment architecture are commented towards a better understanding of the potentials for the exploitation of the SOA paradigm in the industrial automation domain.

💡 Research Summary

The paper by W. Dai and colleagues proposes a formal model that integrates Service‑Oriented Architecture (SOA) with the IEC 61499 function‑block (FB) paradigm to create a more flexible, distributed automation system. IEC 61499 defines control logic as encapsulated FBs that communicate through event and data ports, enabling event‑driven, modular design. The authors map each FB to a service description analogous to WSDL, register these services in a central repository, and allow runtime discovery and binding. Their execution environment is organized into three layers: a communication layer that supports standard protocols (OPC UA, SOAP, REST), a service layer that handles registration, discovery, and composition, and an application layer where engineers design FB networks with graphical tools that are automatically transformed into service definitions.

The core contributions are (1) a systematic mapping between IEC 61499 FB interfaces and SOA service contracts, providing a theoretical bridge for converting traditional FB‑based control systems into service‑based architectures, and (2) an execution platform that supports dynamic reconfiguration without halting the plant. To validate the approach, a case study involving a robotic cell and material‑handling logic on a production line is presented. When a new material‑handling service is deployed, the system automatically redirects the control flow to the new service, achieving reconfiguration within a few seconds—far faster than conventional PLC reprogramming.

Despite these promising results, the paper leaves several critical issues unaddressed. Real‑time performance guarantees and Quality‑of‑Service (QoS) mechanisms are not detailed, raising concerns about latency in safety‑critical loops. Security aspects such as authentication, authorization, and secure communication are omitted, which is a major obstacle for industrial adoption. Moreover, IEC 61499 is still emerging in many factories, so interoperability with legacy IEC 61131‑3 devices requires additional bridging solutions. Finally, the scalability of the service registry and fault‑tolerance strategies for large‑scale deployments are not discussed.

In summary, the work demonstrates that coupling SOA with IEC 61499 can enable on‑the‑fly reconfiguration and improve system flexibility, offering a concrete pathway toward more adaptable industrial automation. Future research should focus on real‑time QoS enforcement, robust security frameworks, standardized interoperability layers, and scalable management of service registries to make the approach viable for production environments.