SIST EN 61158-5-14:2015

SLOVENSKI STANDARD
01-marec-2015
1DGRPHãþD
SIST EN 61158-5-14:2012
Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 5-14. del:
Definicija opravil na aplikacijski ravni - Elementi tipa 14 (IEC 61158-5-14:2014)
Industrial communication networks - Fieldbus specifications - Part 5-14: Application layer
service definition - Type 14 elements (IEC 61158-5-14:2014)
Industrielle Kommunikationsnetze - Feldbusse - Teil 5-14: Dienstfestlegungen des
Application Layer (Anwendungsschicht) - Typ 14-Elemente (IEC 61158-5-14:2014)
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 5-14:
Définition des services de la couche application - Eléments de type 14 (CEI 61158-5-
14:2014)
Ta slovenski standard je istoveten z: EN 61158-5-14:2014
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.100.70 Uporabniški sloj Application layer
35.110 Omreževanje Networking
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN 61158-5-14

NORME EUROPÉENNE
EUROPÄISCHE NORM
October 2014
ICS 25.040.40; 35.100.70; 35.110 Supersedes EN 61158-5-14:2012
English Version
Industrial communication networks - Fieldbus specifications -
Part 5-14: Application layer service definition - Type 14 elements
(IEC 61158-5-14:2014)
Réseaux de communication industriels - Spécifications des Industrielle Kommunikationsnetze - Feldbusse -
bus de terrain - Partie 5-14: Définition des services de la Teil 5-14: Dienstfestlegungen des Application Layer
couche application - Eléments de type 14 (Anwendungsschicht) - Typ 14-Elemente
(CEI 61158-5-14:2014) (IEC 61158-5-14:2014)
This European Standard was approved by CENELEC on 2014-09-22. CENELEC members are bound to comply with the CEN/CENELEC
Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the
same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2014 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 61158-5-14:2014 E
Foreword
The text of document 65C/763/FDIS, future edition 3 of IEC 61158-5-14, prepared by
SC 65C “Industrial networks” of IEC/TC 65 “Industrial-process measurement, control and automation"
was submitted to the IEC-CENELEC parallel vote and approved by CENELEC as
The following dates are fixed:
• latest date by which the document has to be (dop) 2015-06-22
implemented at national level by
publication of an identical national
standard or by endorsement
(dow) 2017-09-22
• latest date by which the national
standards conflicting with the
document have to be withdrawn
This document supersedes EN 61158-5-14:2012.

Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such
patent rights.
This document has been prepared under a mandate given to CENELEC by the European Commission
and the European Free Trade Association.

Endorsement notice
The text of the International Standard IEC 61158-5-14:2014 was approved by CENELEC as a
European Standard without any modification.
In the official version, for Bibliography, the following notes have to be added for the standards indicated:

IEC 60870 Series NOTE Harmonized as EN 60870 Series (not modified).
IEC 61375 Series NOTE Harmonized as EN 61375 Series (not modified).
IEC 61784-1 NOTE Harmonized as EN 61784-1.
IEC 61784-2 NOTE Harmonized as EN 61784-2.

- 3 - EN 61158-5-14:2014
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications

The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.

NOTE 1 When an International Publication has been modified by common modifications, indicated by (mod), the relevant
EN/HD applies.
NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is available here:
www.cenelec.eu
Publication Year Title EN/HD Year

IEC 61131-3 -  Programmable controllers - EN 61131-3 -
Part 3: Programming languages
IEC 61158-1 2014 Industrial communication networks - EN 61158-1 2014
Fieldbus specifications -
Part 1: Overview and guidance for the
IEC 61158 and IEC 61784 series
1)
IEC 61158-4-14 -  Industrial communication networks - EN 61158-4-14 -
Fieldbus specifications -
Part 4-14: Data-link layer protocol
specification - Type 14 elements
1)
IEC 61158-6-14 -  Industrial communication networks - EN 61158-6-14 -
Fieldbus specifications -
Part 6-14: Application layer protocol
specification - Type 14 elements
IEC 61588 -  Precision clock synchronization protocol - -
for networked measurement and control
systems
ISO/IEC 646 -  Information technology - ISO 7-bit coded - -
character set for information interchange
ISO/IEC 7498-1 -  Information technology - Open Systems - -
Interconnection - Basic reference model:
The basic model
ISO/IEC 8822 -  Information technology - Open Systems - -
Interconnection - Presentation service
definition
ISO/IEC 8824-1 -  Information technology - Abstract Syntax - -
Notation One (ASN.1): Specification of
basic notation
ISO/IEC 9545 -  Information technology - Open Systems - -
Interconnection - Application layer
structure
1)
To be published.
Publication Year Title EN/HD Year

ISO/IEC 10731 -  Information technology - Open Systems - -
Interconnection - Basic Reference Model -
Conventions for the definition of OSI
services
IETF RFC 2030 -  Simple Network Time Protocol (SNTP) - -
Version 4 for IPv4, IPv6 and OSI
IEEE 754 -  IEEE Standard for Floating-Point - -
Arithmetic
IEC 61158-5-14 ®
Edition 3.0 2014-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
Industrial communication networks – Fieldbus specifications –

Part 5-14: Application layer service definition – Type 14 elements

Réseaux de communication industriels – Spécifications des bus de terrain –

Partie 5-14: Définition des services de la couche application – Eléments

de type 14
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX XD
ICS 25.040.40; 35.100.70; 35.110 ISBN 978-2-8322-1739-9

– 2 – IEC 61158-5-14:2014 © IEC 2014
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
1.1 General . 7
1.2 Specifications . 8
1.3 Conformance . 8
2 Normative references . 8
3 Terms, definitions, symbols, abbreviations and conventions . 9
3.1 ISO/IEC 7498-1 terms . 9
3.2 ISO/IEC 8822 terms . 9
3.3 ISO/IEC 9545 terms . 9
3.4 ISO/IEC 8824-1 terms . 10
3.5 Fieldbus application-layer specific definitions . 10
3.6 Abbreviations and symbols . 12
3.7 Conventions . 13
4 Concepts . 17
5 Data type ASE . 17
5.1 Overview . 17
5.2 Formal definition of data type objects . 17
5.3 FAL defined data types . 17
5.4 Data type ASE service specification . 39
6 Communication model specification . 39
6.1 General . 39
6.2 ASEs . 40
6.3 Application relationship . 93
6.4 Summary of application layer services . 96
Bibliography . 98

Figure 1 – Application layer entity . 39
Figure 2 – Received message processing procedure . 64
Figure 3 – AR ASE conveys APDUs between AP . 94

Table 1 – Attribute of variable normalised 2 octet . 26
Table 2 – Encoding of variable normalised 2 octet . 26
Table 3 – Attribute of normalised 4 Octet . 26
Table 4 – Encoding of normalised 4 Octet . 26
Table 5 – Attribute of variable normalised 2 octet . 27
Table 6 – Encoding of variable normalised 2 octet . 27
Table 7 – Attribute of variable normalised 4 Octet . 27
Table 8 – Encoding of variable normalised 4 Octet . 28
Table 9 – Attribute of unipolar 2 octet . 28
Table 10 – Encoding of unipolar 2 octet . 28
Table 11 – Attribute of Fixed point value 2 Octet . 29
Table 12 – Encoding of Fixed point value 2 Octet . 29

IEC 61158-5-14:2014 © IEC 2014 – 3 –
Table 13 – Attribute of Fixed point value 4 Octet . 29
Table 14 – Encoding of Bit sequence 2 Octet . 30
Table 15 – Encoding of Nibble 4 Octet . 30
Table 16 – Attribute of multiple time constant 2 octets . 35
Table 17 – Attribute of multiple time constant 4 octets . 36
Table 18 – Attribute of fraction time constant 2 octets . 36
Table 19 – Encoding of reciprocal time constant 2 octets . 36
Table 20 – Management object base. 42
Table 21 – Access group assignment . 56
Table 22 – Access rights assignment . 57
Table 23 – Services for domain object . 57
Table 24 – Service for report object . 59
Table 25 – FAL management entity services . 66
Table 26 – EM_DetectingDevice service parameters. 67
Table 27 – EM_OnlineReply service parameters . 68
Table 28 – EM_GetDeviceAttribute service parameters . 69
Table 29 – EM_ActiveNotification service parameters . 71
Table 30 – EM_ConfiguringDevice service primitives . 72
Table 31 – EM_SetDefaultValue service parameter . 74
Table 32 – Parameters for domain download service . 76
Table 33 – Parameters for domain upload service . 78
Table 34 – EventReport service parameters. 79
Table 35 – AcknowledgeEventReport service parameters . 80
Table 36 – ReportConditionChanging service parameters . 81
Table 37 – Read service parameters . 83
Table 38 – Write service parameters . 84
Table 39 – VariableDistribute service parameters . 85
Table 40 – FRTVariableDistribute service parameters. 86
Table 41 – FRTRead service parameters . 86
Table 42 – FRTWrite service parameters . 87
Table 43 – Parameters for Block Transmission Open service . 89
Table 44 – Parameters for Block Transmission Close service . 90
Table 45 – Parameters for BlockTransmit service . 91
Table 46 – Parameters for Block Transmission Heartbeat service . 93
Table 47 – Summary of application layer services . 97

– 4 – IEC 61158-5-14:2014 © IEC 2014
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-14: Application layer service definition –
Type 14 elements
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
Attention is drawn to the fact that the use of some of the associated protocol types is
restricted by their intellectual-property-right holders. In all cases, the commitment to limited
release of intellectual-property-rights made by the holders of those rights permits a layer
protocol type to be used with other layer protocols of the same type, or in other type
combinations explicitly authorized by their respective intellectual property right holders.
NOTE Combinations of protocol Types are specified in IEC 61784-1 and IEC 61784-2.
International Standard IEC 61158-5-14 has been prepared by subcommittee 65C: Industrial
networks, of IEC technical committee 65: Industrial-process measurement, control and
automation.
This third edition cancels and replaces the second edition published in 2010. This edition
constitutes a technical revision. The main changes with respect to the previous edition are
listed below:
IEC 61158-5-14:2014 © IEC 2014 – 5 –
• corrections of the edit error;
• specification changes for CPF4;
• update of the requirements for all conformance classes;
• update of the requirements for all conformance services.
The text of this standard is based on the following documents:
FDIS Report on voting
65C/763/FDIS 65C/773/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with ISO/IEC Directives, Part 2.
A list of all parts of the IEC 61158 series, published under the general title Industrial
communication networks – Fieldbus specifications, can be found on the IEC web site.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication will be:
• reconfirmed;
• withdrawn;
• replaced by a revised edition, or
• amended.
– 6 – IEC 61158-5-14:2014 © IEC 2014
INTRODUCTION
This part of IEC 61158 is one of a series produced to facilitate the interconnection of
automation system components. It is related to other standards in the set as defined by the
“three-layer” fieldbus reference model described in IEC 61158-1.
The application service is provided by the application protocol making use of the services
available from the data-link or other immediately lower layer. This standard defines the
application service characteristics that fieldbus applications and/or system management may
exploit.
Throughout the set of fieldbus standards, the term “service” refers to the abstract capability
provided by one layer of the OSI Basic Reference Model to the layer immediately above. Thus,
the application layer service defined in this standard is a conceptual architectural service,
independent of administrative and implementation divisions.

IEC 61158-5-14:2014 © IEC 2014 – 7 –
INDUSTRIAL COMMUNICATION NETWORKS –
FIELDBUS SPECIFICATIONS –
Part 5-14: Application layer service definition –
Type 14 elements
1 Scope
1.1 General
The fieldbus application layer (FAL) provides user programs with a means to access the
fieldbus communication environment. In this respect, the FAL can be viewed as a “window
between corresponding application programs.”
This standard provides common elements for basic time-critical and non-time-critical
messaging communications between application programs in an automation environment and
material specific to Type 14 fieldbus. The term “time-critical” is used to represent the
presence of a time-window, within which one or more specified actions are required to be
completed with some defined level of certainty. Failure to complete specified actions within
the time window risks failure of the applications requesting the actions, with attendant risk to
equipment, plant and possibly human life.
This standard defines in an abstract way the externally visible service provided by the Type
14 fieldbus application layer in terms of
a) an abstract model for defining application resources (objects) capable of being
manipulated by users via the use of the FAL service,
b) the primitive actions and events of the service;
c) the parameters associated with each primitive action and event, and the form which they
take; and
d) the interrelationship between these actions and events, and their valid sequences.
The purpose of this standard is to define the services provided to
a) the FAL user at the boundary between the user and the application layer of the fieldbus
reference model, and
b) Systems Management at the boundary between the application layer and Systems
Management of the fieldbus reference model.
This standard specifies the structure and services of the Type 14 fieldbus application layer, in
conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application
layer structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-entities (AE) contained within the
application processes. The FAL AE is composed of a set of object-oriented application service
elements (ASEs) and a layer management entity (LME) that manages the AE. The ASEs
provide communication services that operate on a set of related application process object
(APO) classes. One of the FAL ASEs is a management ASE that provides a common set of
services for the management of the instances of FAL classes.
Although these services specify, from the perspective of applications, how request and
responses are issued and delivered, they do not include a specification of what the requesting
and responding applications are to do with them. That is, the behavioral aspects of the
applications are not specified; only a definition of what requests and responses they can

– 8 – IEC 61158-5-14:2014 © IEC 2014
send/receive is specified. This permits greater flexibility to the FAL users in standardizing
such object behavior. In addition to these services, some supporting services are also defined
in this standard to provide access to the FAL to control certain aspects of its operation.
1.2 Specifications
The principal objective of this standard is to specify the characteristics of conceptual
application layer services suitable for time-critical communications, and thus supplement the
OSI Basic Reference Model in guiding the development of application layer protocols for time-
critical communications.
A secondary objective is to provide migration paths from previously-existing industrial
communications protocols. It is this latter objective which gives rise to the diversity of services
standardized as the various types of IEC 61158.
This specification may be used as the basis for formal Application Programming-Interfaces.
Nevertheless, it is not a formal programming interface, and any such interface will need to
address implementation issues not covered by this specification, including
a) the sizes and octet ordering of various multi-octet service parameters, and
b) the correlation of paired request and confirm, or indication and response, primitives.
1.3 Conformance
This standard does not specify individual implementations or products, nor do they constrain
the implementations of application layer entities within industrial automation systems.
There is no conformance of equipment to this application layer service definition standard.
Instead, conformance is achieved through implementation of conforming application layer
protocols that fulfill the Type 14 application layer services as defined in this standard.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
NOTE All parts of the IEC 61158 series, as well as IEC 61784-1 and IEC 61784-2 are maintained simultaneously.
Cross-references to these documents within the text therefore refer to the editions as dated in this list of normative
references.
IEC 61131-3, Programmable controllers – Part 3: Programming languages
IEC 61158-1:2014, Industrial communication networks – Fieldbus specifications – Part 1:
Overview and guidance for the IEC 61158 and IEC 61784 series
IEC 61158-4-14, Industrial communication networks – Fieldbus specifications – Part 4-14:
Data-link layer protocol specification – Type 14 elements
IEC 61158-6-14, Industrial communication networks – Fieldbus specifications – Part 6-14:
Application layer protocol specification – Type 14 elements
IEC 61588, Precision clock synchronization protocol for networked measurement and control
systems
ISO/IEC 646, Information technology – ISO 7–bit coded character set for information
interchange
IEC 61158-5-14:2014 © IEC 2014 – 9 –
ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference
Model: The Basic Model
ISO/IEC 8822, Information technology – Open Systems Interconnection – Presentation
service definition
ISO/IEC 8824-1, Information technology – Abstract Syntax Notation One (ASN.1):
Specification of basic notation
ISO/IEC 9545, Information technology – Open Systems Interconnection – Application Layer
structure
ISO/IEC 10731, Information technology – Open Systems Interconnection – Basic Reference
Model – Conventions for the definition of OSI services
RFC 2030, Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI, available
at
ANSI/IEEE 754, IEEE Standard for Binary Floating-Point Arithmetic
3 Terms, definitions, symbols, abbreviations and conventions
For the purposes of this document, the following terms, definitions, symbols, abbreviations
and conventions as defined in these publications apply:
3.1 ISO/IEC 7498-1 terms
a) application entity
b) application process
c) application protocol data unit
d) application service element
e) application entity invocation
f) application process invocation
g) application transaction
h) real open system
i) transfer syntax
3.2 ISO/IEC 8822 terms
a) abstract syntax
b) presentation context
3.3 ISO/IEC 9545 terms
a) application-association
b) application-context
c) application context name
d) application-entity-invocation
e) application-entity-type
f) application-process-invocation
g) application-process-type
h) application-service-element

– 10 – IEC 61158-5-14:2014 © IEC 2014
i) application control service element
3.4 ISO/IEC 8824-1 terms
a) object identifier
b) type
3.5 Fieldbus application-layer specific definitions
3.5.1
access control
control on the reading and writing of an object
3.5.2
access Path
association of a symbolic name with a variable for the purpose of open communication
3.5.3
communication macrocycle
set of basic cycles needed for a configured communication activity in a macro network
segment
3.5.4
communication scheduling
algorithms and operation for data transfers occurring in a deterministic and repeatable
manner
3.5.5
configuration (of a system or device)
step in system design: selecting functional units, assigning their locations and defining their
interconnections
3.5.6
cyclic
repetitive in a regular manner
3.5.7
destination FB Instance
FB instance that receives the specified parameters
3.5.8
domain
part of memory used to store code or data
3.5.9
domain download
operation to write data in a domain
3.5.10
domain upload
operation to read data from a domain
3.5.11
entity
particular thing, such as a person, place, process, object, concept, association, or event

IEC 61158-5-14:2014 © IEC 2014 – 11 –
3.5.12
bridge
DL-relay entity which performs synchronization between links (buses) and may perform
selective store-and-forward and routing functions to connect two micro network segments
3.5.13
identifier
16-bit word associated with a system variable
3.5.14
index
address of an object within an application process
3.5.15
instance
actual physical occurrence of an object within a class that identifies one of many objects
within the same object class
3.5.16
instantiation
creation of an instance of a specified type
3.5.17
management information
network-visible information for the purpose of managing the field system
3.5.18
management information base
organized list of management information
3.5.19
mapping
set of values having defined correspondence with the quantities or values of another set
3.5.20
message filtering
decision on a message according to a special rule
3.5.21
micro segment
part of a network, where special scheduling is implemented
3.5.22
offset
number of octets from a specially designated position
3.5.23
phase
elapsed fraction of a cycle, measured from some fixed origin
3.5.24
process interface
data exchange and information mapping between physical process and application unit
3.5.25
real-time
ability of a system to provide a required result in a bounded time

– 12 – IEC 61158-5-14:2014 © IEC 2014
3.5.26
real-time communication
transfer of data in real-time
3.5.27
real-time Ethernet
RTE
ISO/IEC 8802-3-based network that includes real-time communication
Note 1 to entry:  Other communication can be supported, providing the real-time communication is not
compromised.
Note 2 to entry:  This definition is dedicated, but not limited, to ISO/IEC 8802-3. It could be applicable to other
IEEE 802 specifications, for example IEEE 802.11.
3.5.28
schedule
temporal arrangement of a number of related operations
3.5.29
scheduling macrocycle
time interval to implement a specific schedule
3.5.30
source FB Instance
FB instance that sends a specific parameter
3.5.31
time offset
time difference from a specially designated time
3.6 Abbreviations and symbols
AAE Application Access Entity
AE Application Entity
AL Application Layer
ALME Application Layer Management Entity
ALP Application Layer Protocol
APO Application Object
AP Application Process
APDU Application Protocol Data Unit
API Application Process Identifier
AR Application Relationship
ARP Address Resolution Protocol
AREP Application Relationship End Point
ASE Application Service Element
Cnf Confirmation
CR Communication Relationship
CREP Communication Relationship End Point
CSMA/CD Carrier Sense Multiple Access Protocol with Collision Detection
DD Device Description
DHCP Dynamic Host Configuration Protocol
DL- (as a prefix) Data Link-
DLCEP Data Link Connection End Point

IEC 61158-5-14:2014 © IEC 2014 – 13 –
DLL Data Link Layer
DLE Data Link Entity
DLM Data Link-management
DLS Data Link Service
DLSAP Data Link Service Access Point
DLSDU DL-service-data-unit
ECSME Type 14 communication scheduling management entity
Type 14 Ethernet for Plant Automation
EM_ (as a prefix) Type 14 Management
ESME Type 14 Socket Mapping Entity
FB Function Block
FBAP Function Block Application Process
FRT Fast Real-time
Ind Indication
IP Internet Protocol
LLC Logical Link Control
LMP Link Management Protocol
MAC Medium Access Control
MAU Medium Attachment Unit
MOB Management Object Base
PAD Pad (bits)
PDU Protocol Data Unit
P/S Publisher/Subscriber
Req Request
Rsp Response
RTE Real-Time Ethernet
RT-Ethernet Real-Time Ethernet
SAP Service Access Point
SDU Service Data Unit
SME System Management Entity
SNTP Simple Network Time Protocol
TCP Transmission Control Protocol
UDP User Datagram Protocol
3.7 Conventions
3.7.1 Overview
The FAL is defined as a set of object-oriented ASEs. Each ASE is specified in a separate
subclause. Each ASE specification is composed of two parts, its class specification, and its
service specification.
The class specification defines the attributes of the class. The attributes are accessible from
instances of the class using the Object Management ASE services specified in Clause 5. The
service specification defines the services that are provided by the ASE.
3.7.2 Conventions for class definitions
Class definitions are described using templates. Each template consists of a list of attributes
for the class. The general form of the template is shown below:

– 14 – IEC 61158-5-14:2014 © IEC 2014
FAL ASE: ASE Name
CLASS: Class name
CLASS ID: #
PARENT CLASS: Parent class name
ATTRIBUTES:
1 (o) Key Attribute: numeric identifier
2 (o) Key Attribute: name
3 (m) Attribute: attribute name(values)
4 (m) Attribute: attribute name(values)
4.1 (s) Attribute: attribute name(values)
4.2 (s) Attribute: attribute name(values)
4.3 (s) Attribute: attribute name(values)
5. (c) Constraint: constraint expression
5.1 (m) Attribute: attribute name(values)
5.2 (o) Attribute: attribute name(values)
6 (m) Attribute: attribute name(values)
6.1 (s) Attribute: attribute name(values)
6.2 (s) Attribute: attribute name(values)
SERVICES:
1 (o) OpsService: service name
2. (c) Constraint: constraint expression
2.1 (o) OpsService: service name
3 (m) MgtService: service name

(a) The "FAL ASE:" entry is the name of the FAL ASE that provides the services for the class
being specified.
(b) The "CLASS:" entry is the name of the class being specified. All objects defined using this
template will be an instance of this class. The class may be specified by this standard, or
by a user of this standard.
(c) The "CLASS ID:" entry is a number that identifies the class being specified. This number is
unique within the FAL ASE that will provide the services for this class. When qualified by
the identity of its FAL ASE, it unambiguously identifies the class within the scope of the
FAL. The value "NULL" indicates that the class cannot be instantiated. Class IDs between
1 and 255 are reserved by this standard to identify standardized classes. They have been
assigned to maintain compatibility with existing national standards. CLASS IDs between
256 and 2048 are allocated for identifying user defined classes.
(d) The "PARENT CLASS:" entry is the name of the parent class for the class being specified.
All attributes defined for the parent class and inherited by it are inherited for the class
being defined, and therefore do not have to be redefined in the template for this class.
NOTE The parent-class "TOP" indicates that the class being defined is an initial class definition. The parent class
TOP is used as a starting point from which all other classes are defined. The use of TOP is reserved for classes
defined by this standard.
(e) The "ATTRIBUTES" label indicate that the following entries are attributes defined for the
class.
1) Each of the attribute entries contains a line number in column 1, a mandatory (m) /
optional (o) / conditional (c) / selector (s) indicator in column 2, an attribute type label
in column 3, a name or a conditional expression in column 4, and optionally a list of
enumerated values in column 5. In the column following the list of values, the default
value for the attribute may be specified.
2) Objects are normally identified by a numeric identifier or by an object name, or by both.
In the class templates, these key attributes are defined under the key attribute.
3) The line number defines the sequence and the level of nesting of the line. Each
nesting level is identified by period. Nesting is used to specify
i) fields of a structured attribute (4.1, 4.2, 4.3),

IEC 61158-5-14:2014 © IEC 2014 – 15 –
ii) attributes conditional on a constraint statement (5). Attributes may be mandatory
(5.1) or optional (5.2) if the constraint is true. Not all optional attributes require
constraint statements as does the attribute defined in (5.2).
iii) the selection fields of a choice type attribute (6.1 and 6.2).
(f) The "SERVICES" label indicates that the following entries are services defined for the
class.
1) An (m) in column 2 indicates that the service is mandatory for the class, while an (o)
indicates that it is optional. A (c) in this column indicates that the service is conditional.
When all services defined for a class are defined as optional, at least one has to be
selected when an instance of the class is defined.
2) The label "OpsService" designates an operational service (1).
3) The label "MgtService" designates a management service (2).
4) The line number defines the sequence and the level of nesting of the line. Each
nesting level is identified by period. Nesting within the list of services is used to specify
services conditional on a constraint statement.
3.7.3 Conventions for service definitions
3.7.3.1 General
This standard uses the descriptive conventions given in ISO/IEC 10731.
The service model, service primitives, and time-sequence diagrams used are entirely abstract
descriptions; they do not represent a specification for implementation.
3.7.3.2 Service parameters
Service primitives are used to represent service user/service provider interactions
(ISO/IEC 10731). They convey parameters which indicate information available in the
user/provider interaction.
NOTE 1 See the note under 3.7.3.3 relative to the non-inclusion of service parameters that are appropriate to a
protocol specification or programming interface specification or implementation specification, but not to an abstract
service definition.
This standard uses a tabular format to describe the component parameters of the service
primitives. The parameters that apply to each group of service primitives are set out in tables
throughout the remainder of this standard. Each table consists of up to six columns: a column
for the name of the service parameter, and a column each for those primitives and parameter-
transfer directions used by the service. The possible six columns are:
a) the parameter name;
b) the request primitive’s input parameters;
c)
...