Formal modeling and verification of IEC 61499 function blocks on the basis of transition systems

Victor Dubinin, Valeriy Vyatkin, Anatoly Shalyto

Research output: Chapter in Book/Report/Conference proceedingConference contributionScientificpeer-review

2 Citations (Scopus)


The IEC 61499 standard has become one of the key approaches to building distributed component-based control systems in industrial automation. The problem of adoption of this standard in industrial practice is often associated with incompletely defined semantics of functional blocks (FB), which are main design artifacts of the standard. In this paper we propose formal (operational) semantics of IEC 61499 FB using transition systems (by example of FB systems operating in accordance with the cyclic execution model). The proposed FB operational semantics is most convenient for the formal verification of FB systems on the basis of model checking as it describes the direct transitions between states. A limitation of this approach is the need to map hierarchical FB systems to flat models. The technique of code generation used for transforming FB transition systems to SMV models is briefly discussed followed by a simple case study.

Original languageEnglish
Title of host publication2016 International Siberian Conference on Control and Communications, SIBCON 2016 - Proceedings
Number of pages4
ISBN (Electronic)978-1-4673-8383-7
Publication statusPublished - 14 Jun 2016
MoE publication typeA4 Article in a conference publication
EventInternational Siberian Conference on Control and Communications - Moscow, Russian Federation
Duration: 12 May 201614 May 2016


ConferenceInternational Siberian Conference on Control and Communications
Abbreviated titleSIBCON
Country/TerritoryRussian Federation


  • formal semantics
  • function block
  • IEC 61499
  • model checking
  • SMV
  • transition system


Dive into the research topics of 'Formal modeling and verification of IEC 61499 function blocks on the basis of transition systems'. Together they form a unique fingerprint.

Cite this