Organized and Sponsored by
Home  Contact Us  
Execution semantics of IEC 61499 Function Block Applications
ChairAlois Zoitl 
ChairGeorg Frey 
The list of track sessions and articles can be found here.

The IEC 61499 function block standard has been finally adopted and published by the International Electrotechnical Commission in 2005. However, early attempts of implementation by industry and numerous research works in academia have revealed a number of 'semantic loopholes' - i.e. incomplete definitions of how function blocks must be interpreted during their execution. This creates a room for multiple interpretations, which, in turn, shrinks the portability potential of IEC 61499 applications and hinders IEC 61499 adoption by industry.

The IEC 61499 standard has a built-in mechanism of answering such 'incompleteness' problems known as 'Compliance profiles' which, according to the Part 4 of IEC 61499, specify the features of IEC 61499-1 and 61499-2 to be implemented in order to promote the following attributes of IEC 61499-based systems, devices and software tools:

  • Interoperability of devices from multiple suppliers;
  • Portability of software between software tools of multiple suppliers; and
  • Configurability of devices from multiple vendors by software tools of multiple suppliers.
Several compliance profiles may be necessary to provide for implementations. This list serves as basis for the topics that should be presented within this special session:
  • Execution of a basic function block;
  • Execution of a composite function block;
  • Scheduling of function blocks in resource and of resources in a device;
  • Execution of Service Interface Function Blocks;