What is BS EN 61499-1 - Architecture of function blocks about?
BS EN 61499-1 is the first part of the multiple series that defines a generic architecture and presents guidelines for the use of function blocks in distributed industrial-process measurement and control systems (IPMCSs). BS EN 61499-1 architecture is presented in terms of implementable reference models, textual syntax, and graphical representations. These models, representations, and syntax can be used for:
- The specification and standardization of function block types
- The functional specification and standardization of system elements
- The implementation-independent specification, analysis, and validation of distributed IPMCSs
- The configuration, implementation, operation, and maintenance of distributed IPMCSs
- The exchange of information among software tools for the performance of the above functions
Note: BS EN 61499-1 does not restrict or specify the functional capabilities of IPMCSs or their system elements, except as such capabilities are represented using the elements defined herein. IEC 61499-4 addresses the extent to which the elements defined in BS EN 61499-1 may be restricted by the functional capabilities of compliant systems, subsystems, and devices.
Who is BS EN 61499-1 - Architecture of function blocks for?
BS EN 61499-1 on Functional blocks is useful for: 
- Manufacturers of functional blocks-based devices (control devices) 
- Software companies/IT firms 
- Engineers responsible for the specification, engineering, and implementation of control systems 
- Automation industries 
Why should you use BS EN 61499-1 - Architecture of function blocks?
A function block instance is a software functional unit that consists of a single, named copy of a data structure on which associated operations can be performed as specified by a function block type.
BS EN 61499-1 includes:
- General requirements, including scope, normative references, definitions, and reference models
- Rules for the declaration of function block types, and rules for the behaviour of instances of the types so declared
- Rules for the use of function blocks in the configuration of distributed industrial-process measurement and control systems (IPMCSs)
- Rules for the use of function blocks in meeting the communication requirements of distributed IPMCSs
- Rules for the use of function blocks in the management of applications, resources, and devices in distributed IPMCSs
Overall, BS EN 61499-1 provides reference models for the use of function blocks in other standards dealing with the support of the system life cycle, including system planning, design, implementation, validation, operation, and maintenance.
What’s changed since the last update?
BS EN 61499-1:2013 supersedes BS EN 61499-1:2005 which is withdrawn.
EN 61499-1:2013 includes the following significant technical changes with respect to EN 61499-1:2005:
- Execution control in basic function blocks (5.2) has been clarified and extended:
- Dynamic and static parts of the EC transition condition are clearly delineated by using the EC transition event [guard condition] syntax of the Unified Modelling Language (UML) (5.2.1.3, B.2.1)
- The terminology "crossing of an EC transition" (3.10) is used preferentially to "clearing" to avoid the misinterpretation that the entire transition condition corresponds to a Boolean variable that can be "cleared."
- Operation of the ECC state machine in 5.2.2.2 has been clarified and made more rigorous
- Event and data outputs of adapter instances (plugs and sockets) can be used in EC transition conditions, and event inputs of adapter instances can be used as EC action outputs
- Temporary variables (3.97) can be declared (B.2.1) and used in algorithms of basic function blocks
- Service sequences (6.1.3) can now be defined for basic and composite function block types and adapter types, as well as service interface types
- The syntax for mapping FB instances from applications to resources has been simplified (Clause B.3)
- Syntax for the definition of segment types (7.2.3) for network segments of system configurations has been added (Clause B.3)
