EN 62541-10:2015

SLOVENSKI STANDARD
01-september-2015
1DGRPHãþD
SIST EN 62541-10:2012
Enotna arhitektura OPC - 10. del: Programi (IEC 62541-10:2015)
OPC Unified Architecture - Part 10:Programs (IEC 62541-10:2015)
OPC Unified Architecture - Teil 10: Programme (IEC 62541-10:2015)
Architecture unifiée OPC - Partie 10: Programmes (IEC 62541-10:2015)
Ta slovenski standard je istoveten z: EN 62541-10:2015
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN 62541-10

NORME EUROPÉENNE
EUROPÄISCHE NORM
April 2015
ICS 25.040.40; 35.100 Supersedes EN 62541-10:2012
English Version
OPC unified architecture - Part 10: Programs
(IEC 62541-10:2015)
Architecture unifiée OPC - Partie 10: Programmes OPC Unified Architecture - Teil 10: Programme
(IEC 62541-10:2015) (IEC 62541-10:2015)
This European Standard was approved by CENELEC on 2015-04-14. 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
© 2015 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 62541-10:2015 E
Foreword
The text of document 65E/383/FDIS, future edition 2 of IEC 62541-10, prepared by SC 65E “Devices
and integration in enterprise systems” of IEC/TC 65 “Industrial-process measurement, control and
automation" was submitted to the IEC-CENELEC parallel vote and approved by CENELEC as EN
62541-10:2015.
The following dates are fixed:
• latest date by which the document has to be (dop) 2016-01-14
implemented at national level by
publication of an identical national
standard or by endorsement
(dow) 2018-04-14
• latest date by which the national
standards conflicting with the
document have to be withdrawn
This document supersedes EN 62541-10: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 62541-10:2015 was approved by CENELEC as a European
Standard without any modification.

- 3 - EN 62541-10:2015
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

1)
IEC 62541-3 2015 OPC Unified Architecture -- Part 3: EN 62541-3
Address Space Model
1)
IEC 62541-4 2015 OPC Unified Architecture -- Part 4: EN 62541-4
Services
1)
IEC 62541-5 2015 OPC Unified Architecture -- Part 5: EN 62541-5
Information Model
IEC 62541-7 -  OPC Unified Architecture -- Part 7: Profiles EN 62541-7 -
IEC/TR 62541-1 -  OPC unified architecture -- Part 1: CLC/TR 62541-1 -
Overview and concepts
1) To be published.
IEC 62541-10 ®
Edition 2.0 2015-03
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
OPC Unified Architecture –
Part 10: Programs
Architecture unifiée OPC –
Partie 10: Programmes
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100 ISBN 978-2-8322-2274-4

– 2 – IEC 62541-10:2015 © IEC 2015
CONTENTS
FOREWORD . 4
1 Scope . 6
2 Normative references . 6
3 Terms, definitions and conventions . 6
3.1 Terms and definitions . 6
3.2 Abbreviations . 7
4 Concepts . 7
4.1 General . 7
4.2 Programs . 8
4.2.1 Overview . 8
4.2.2 Security considerations . 9
4.2.3 Program Finite State Machine . 9
4.2.4 Program states . 10
4.2.5 State transitions . 11
4.2.6 Program state transition stimuli . 11
4.2.7 Program Control Methods . 11
4.2.8 Program state transition effects . 12
4.2.9 Program result data . 12
4.2.10 Program lifetime . 13
5 Model . 13
5.1 General . 13
5.2 ProgramType . 14
5.2.1 Overview . 14
5.2.2 ProgramType Properties . 16
5.2.3 ProgramType components . 16
5.2.4 ProgramType causes (Methods) . 21
5.2.5 ProgramType effects (Events) . 23
5.2.6 AuditProgramTransitionEventType . 25
5.2.7 FinalResultData . 26
5.2.8 ProgramDiagnostic DataType . 26
5.2.9 ProgramDiagnosticType VariableType . 27
Annex A (informative) Program example . 28
A.1 Overview. 28
A.2 DomainDownload Program . 28
A.2.1 General. 28
A.2.2 DomainDownload states . 29
A.2.3 DomainDownload transitions . 30
A.2.4 DomainDownload Methods. 30
A.2.5 DomainDownload Events . 31
A.2.6 DomainDownload model . 31

Figure 1 – Automation facility control . 8
Figure 2 – Program illustration . 9
Figure 3 – Program states and transitions . 10
Figure 4 – Program Type . 14

IEC 62541-10:2015 © IEC 2015 – 3 –
Figure 5 – Program FSM References . 17
Figure 6 – ProgramType causes and effects . 21
Figure A.1 – Program example . 28
Figure A.2 – DomainDownload state diagram . 29
Figure A.3 – DomainDownloadType partial state model . 35
Figure A.4 – Ready To Running model . 38
Figure A.5 – Opening To Sending To Closing model . 40
Figure A.6 – Running To Suspended model . 41
Figure A.7 – Suspended To Running model . 42
Figure A.8 – Running To Halted – Aborted model . 43
Figure A.9 – Suspended To Aborted model . 44
Figure A.10 – Running To Completed model . 45
Figure A.11 – Sequence of operations . 46

Table 1 – Program Finite State Machine . 9
Table 2 – Program states . 10
Table 3 – Program state transitions . 11
Table 4 – Program Control Methods . 12
Table 5 – ProgramType . 15
Table 6 – Program states . 17
Table 7 – Program transitions . 19
Table 8 – ProgramType causes. 22
Table 9 – ProgramTransitionEventType . 23
Table 10 – ProgramTransitionEvents . 24
Table 11 – AuditProgramTransitionEventType . 25
Table 12 – ProgramDiagnosticDataType structure . 26
Table 13 – ProgramDiagnosticDataType definition . 26
Table 14 – ProgramDiagnosticType VariableType . 27
Table A.1 – DomainDownload states . 30
Table A.2 – DomainDownload Type . 32
Table A.3 – Transfer State Machine Type . 32
Table A.4 – Transfer State Machine – states . 33
Table A.5 – Finish State Machine Type . 33
Table A.6 – Finish State Machine – states . 34
Table A.7 – DomainDownload Type Property Attributes variable values . 34
Table A.8 – Additional DomainDownload transition types . 36
Table A.9 – Start Method additions . 38
Table A.10 – StartArguments . 39
Table A.11 – IntermediateResults Object . 40
Table A.12 – Intermediate result data Variables . 41
Table A.13 – FinalResultData . 44
Table A.14 – Final result Variables . 45

– 4 – IEC 62541-10:2015 © IEC 2015
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
OPC UNIFIED ARCHITECTURE –
Part 10: Programs
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.
International Standard IEC 62541-10 has been prepared by subcommittee 65E: Devices and
integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.
This second edition cancels and replaces the first edition published in 2012. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) Based on NIST review, security considerations have been included as 4.2.2;
b) Fixed the definition of the Program Diagnostic Type into a data type (5.2.8) and added
missing data type for the Program Diagnostic Variable in the ProgramType in Table 5.
c) Corrected the BrowseName of the audit events for Program Transitions in Table 7.

IEC 62541-10:2015 © IEC 2015 – 5 –
The text of this standard is based on the following documents:
FDIS Report on voting
65E/383/FDIS 65E/409/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 the ISO/IEC Directives, Part 2.
A list of all parts of the IEC 62541 series, published under the general title OPC Unified
Architecture, can be found on the IEC website.
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.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
– 6 – IEC 62541-10:2015 © IEC 2015
OPC UNIFIED ARCHITECTURE –
Part 10: Programs
1 Scope
This part of IEC 62541 is part of the overall OPC Unified Architecture (OPC UA) standard
series and defines the information model associated with Programs. This includes the
description of the NodeClasses, standard Properties, Methods and Events and associated
behaviour and information for Programs.
The complete address space model including all NodeClasses and Attributes is specified in
IEC 62541-3. The services such as those used to invoke the Methods used to manage
Programs are specified in IEC 62541-4.
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.
IEC TR 62541-1, OPC Unified Architecture – Part 1: Overview and Concepts
IEC 62541-3:2015, OPC Unified Architecture – Part 3: Address Space Model
IEC 62541-4:2015, OPC Unified Architecture – Part 4: Services
IEC 62541-5:2015, OPC Unified Architecture – Part 5: Information Model
IEC 62541-7, OPC Unified Architecture – Part 7: Profiles
3 Terms, definitions and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC TR 62541-1,
IEC 62541-3, as well as the following apply.
3.1.1
function
programmatic task performed by a server or device, usually accomplished by computer code
execution
3.1.2
Finite State Machine
sequence of states and valid state transitions along with the causes and effects of those state
transitions that define the actions of a Program in terms of discrete stages
3.1.3
ProgramType
type definition of a Program and is a subtype of the FiniteStateMachineType

IEC 62541-10:2015 © IEC 2015 – 7 –
3.1.4
Program Control Method
Method having specific semantics designed for the control of a Program by causing a state
transition
3.1.5
Program Invocation
unique Object instance of a Program existing on a Server
Note 1 to entry: A Program Invocation is distinguished from other Object instances of the same ProgramType by
the object node’s unique browse path.
3.2 Abbreviations
DA Data Access
FSM Finite State Machine
HMI Human Machine Interfaces
PCM Program Control Method
PGM Program
PI Program Invocation
UA Unified Architecture
4 Concepts
4.1 General
Integrated automation facilities manage their operations through the exchange of data and the
coordinated invocation of system functions as illustrated in Figure 1. Services are required to
perform the data exchanges and to invoke the functions that constitute system operation.
These functions may be invoked through Human Machine Interfaces, cell controllers, or other
supervisory control and data acquisition type systems. OPC UA defines Methods and
Programs as an interoperable way to advertise, discover, and request these functions. They
provide a normalizing mechanism for the semantic description, invocation, and result
reporting of these functions. Together Methods and Programs complement the other OPC UA
Services and ObjectTypes to facilitate the operation of an automation environment using a
client-server hierarchy.
– 8 – IEC 62541-10:2015 © IEC 2015
Filling
Cleaning
Labelling
Palletizing
Packaging
IEC
Figure 1 – Automation facility control
Methods and Programs model functions typically have different scopes, behaviours, lifetimes,
and complexities in OPC Servers and the underlying systems. These functions are not
normally characterized by the reading or writing of data which is accomplished with the OPC
UA Attribute service set.
Methods represent basic functions in the Server that can be invoked by a Client. Programs, by
contrast, model more complex and stateful functionality in the system. For example, a method
call may be used to perform a calculation or reset a counter. A Program is used to run and
control a batch process, execute a machine tool part program, or manage a domain download.
Methods and their invocation mechanism are described in IEC 62541-3 and IEC 62541-4.
This standard describes the extensions to, or specific use of, the core capabilities defined in
IEC 62541-5 as required for Programs.
4.2 Programs
4.2.1 Overview
Programs are complex functions in a server or underlying system that can be invoked and
managed by a Client. Programs can represent any level of functionality within a system or
process in which client control or intervention is required and progress monitoring is desired.
Figure 2 illustrates the model.

IEC 62541-10:2015 © IEC 2015 – 9 –

Program
Control methods
________()
Manage
________()
________()
State machine
_________
Get description
_________
_________
Transition events
_________
Monitor
_________
_________
Result data
_________
Get results
_________
_________
IEC
Figure 2 – Program illustration
Programs are state full and transition through a prescribed sequence of states as they
execute. Their behaviour is defined by a Program Finite State Machine (PFSM). The elements
of the PFSM describe the phases of a Program’s execution in terms of valid transitions
between a set of states, the stimuli or causes of those transitions, and the resultant effects of
the transitions.
4.2.2 Security considerations
Since Programs can be used to perform advanced control algorithms or other actions, their
use should be restricted to personnel with appropriate access rights. It is recommended that
AuditUpdateMethodEvents are generated to allow monitoring the number of running Programs
in addition to their execution frequency.
4.2.3 Program Finite State Machine
The states, transitions, causes and effects that compose the Program Finite State Machine
are listed in Table 1 and illustrated in Figure 3.
Table 1 – Program Finite State Machine
No. Transition name Cause From state To state Effect
Report Transition 1
1 HaltedToReady Reset Method Halted Ready
Event/Result
Report Transition 2
2 ReadyToRunning Start Method Ready Running
Event/Result
Halt Method or Report Transition 3
3 RunningToHalted Running Halted
Internal (Error) Event/Result
Report Transition 4
4 RunningToReady Internal Running Ready
Event/Result
5 RunningToSuspended Suspend Method Running Suspended
Report Transition 5
– 10 – IEC 62541-10:2015 © IEC 2015
No. Transition name Cause From state To state Effect
Event/Result
Report Transition 6
6 SuspendedToRunning Resume Method Suspended Running
Event/Result
Report Transition 7
7 SuspendedToHalted Halt Method Suspended Halted
Event/Result
Report Transition 8
8 SuspendedToReady Internal Suspended Ready
Event/Result
Report Transition 9
9 ReadyToHalted Halt Method Ready Halted
Event/Result
HALTED
READY
4 7
RUNNING
SUSPENDED
IEC
Figure 3 – Program states and transitions
4.2.4 Program states
A standard set of base states is defined for Programs as part of the Program Finite State
Machine. These states represent the stages in which a Program can exist at an instance in
time as viewed by a Client. This state is the Program’s current state. All Programs shall
support this base set. A Program may or may not require a Client action to cause the state to
change. The states are formally defined in Table 2.
Table 2 – Program states
State Description
Ready The Program is properly initialized and may be started.
Running The Program is executing making progress towards completion.
The Program has been stopped prior to reaching a terminal state but may be
Suspended
resumed.
Halted
The Program is in a terminal or failed state, and it cannot be started or resumed
without being reset.
The set of states defined to describe a Program can be expanded. Program sub states can be
defined for the base states to provide more resolution of a process and to describe the cause
and effect(s) of additional stimuli and transitions. Standards bodies and industry groups may
extend the base Program Finite State Model to conform to various industry models. For
example, the Halted state can include the sub states “Aborted” and “Completed” to indicate if

IEC 62541-10:2015 © IEC 2015 – 11 –
the function achieved a successful conclusion prior to the transition to Halted. Transitional
states such as “Starting” or “Suspending” might also be extensions of the Running state, for
example.
4.2.5 State transitions
A standard set of state transitions is defined for the Program Finite State Machine. These
transitions define the valid changes to the Program’s current state in terms of an initial state
and a resultant state. The transitions are formally defined in Table 3.
Table 3 – Program state transitions
Transition no. Transition name Initial state Resultant state
1 HaltedToReady Halted Ready
2 ReadyToRunning Ready Running
3 RunningToHalted Running Halted
4 RunningToReady Running Ready
5 RunningToSuspended Running Suspended
6 SuspendedToRunning Suspended Running
7 SuspendedToHalted Suspended Halted
8 SuspendedToReady Suspended Ready
9 ReadyToHalted Ready Halted
4.2.6 Program state transition stimuli
The stimuli or causes for a Program’s state transitions can be internal to the Server or
external. The completion of machining steps, the detection of an alarm condition, or the
transmission of a data packet are examples of internal stimuli. Methods are an example of
external stimuli. Standard Methods are defined which act as stimuli for the control of a
Program.
4.2.7 Program Control Methods
Clients manage a Program by calling Methods. The Methods impact a Program’s behaviour by
causing specified state transitions. The state transitions dictate the actions performed by the
Program. This standard defines a set of standard Program Control Methods. These Methods
provide sufficient means for a client to run a Program.
Table 4 lists the set of defined Program Control Methods. Each Method causes transitions
from specified states and shall be called when the Program is in one of those states.
Individual Programs can optionally support any subset of the Program Control Methods. For
example, some Programs may not be permitted to suspend and so would not provide the
Suspend and Resume Methods.
Programs can support additional user defined Methods. User defined Methods shall not
change the behaviour of the base Program Finite State Machine.

– 12 – IEC 62541-10:2015 © IEC 2015
Table 4 – Program Control Methods
Method Name Description
Start Causes the Program to transition from the Ready state to the Running state.
Suspend Causes the Program to transition from the Running state to the Suspended state.
Resume Causes the Program to transition from the Suspended state to the Running state.
Halt Causes the Program to transition from the Ready, Running or Suspended state to the
Halted state.
Reset Causes the Program to transition from the Halted state to the Ready state.

Program Control Methods can include arguments that are used by the Program. For example,
a Start Method may include an options argument that specifies dynamic options used to
determine some program behaviour. The arguments can differ on each ProgramType. The
Method Call service specified in IEC 62541-4:2015, 5.11 defines a return status. This return
status indicates the success of the Program Control Method or a reason for its failure.
4.2.8 Program state transition effects
A Program’s state transition generally has a cause and also yields an effect. The effect is a by
product of a Program state transition that can be used by a Client to monitor the progress of
the Program. Effects can be internal or external. An external effect of a state transition is the
generation of an Event notification. Each Program state transition is associated with a unique
Event. These Events reflect the progression and trajectory of the Program through its set of
defined states. The internal effects of a state transition can be the performance of some
programmatic action such as the generation of data.
4.2.9 Program result data
4.2.9.1 Overview
Result data is generated by a running Program. The result data can be intermediate or final.
Result data may be associated with specific Program state transitions.
4.2.9.2 Intermediate result data
Intermediate result data is transient and is generated by the Program in conjunction with non-
terminal state transitions. The data items that compose the intermediate results are defined in
association with specific Program state transitions. Their values are relevant only at the
transition level.
Each Program state transition can be associated with different result data items. Alternately, a
set of transitions can share a result data item. Percentage complete is an example of
intermediate result data. The value of percentage complete is produced when the state
transition occurs and is available to the Client.
Clients acquire intermediate result data by subscribing to Program state transition Events.
The Events specify the data items for each transition. When the transition occurs, the
generated Event conveys the result data values captured to the subscribed Clients. If no
Client is monitoring the Program, intermediate result data may be discarded.
4.2.9.3 Terminal result data
Terminal result data is the final data generated by the Program as it ceases execution. Total
execution time, number of widgets produced, and fault condition encountered are examples of
terminal result data. When the Program enters the terminal state, this result data can be
conveyed to the client by the transition Event. Terminal result data is also available within the
Program to be read by a Client after the program stops. This data persists until the Program
Instance is rerun or deleted.
IEC 62541-10:2015 © IEC 2015 – 13 –
4.2.9.4 Monitoring Programs
Clients can monitor the activities associated with a Program’s execution. These activities
include the invocation of the management Methods, the generation of result data, and the
progression of the Program through its states. Audit Events are provided for Method Calls and
state transitions. These Events allow a record to be maintained of the Clients that interacted
with any Program and the Program state transitions that resulted from that interaction.
4.2.10 Program lifetime
4.2.10.1 Overview
Programs can have different lifetimes. Some Programs may always be present on a Server
while others are created and removed. Creation and removal can be controlled by a Client or
may be restricted to local means.
A Program can be Client creatable. If a Program is Client creatable, then the Client can add
the Program to the Server. The Object Create Method defined in IEC 62541-3:2015, 5.5.4, is
used to create the Program instance. The initial state of the Program can be Halted or Ready.
Some Programs, for example, may require that a resource becomes available after its
creation and before it is ready to run. In this case, it would be initialized in the Halted state
and transition to Ready when the resource is delivered.
A Program can be Client removable. If the Program is Client removable, then the Client can
delete the Program instance from the Server. The DeleteNodes Service defined in
IEC 62541-4 is used to remove the Program Instance. The Program shall be in a Halted state
to be removed. A Program may also be auto removable. An auto removable Program deletes
itself when execution has terminated.
4.2.10.2 Program instances
Programs can be multiple instanced or single instanced. A Server can support multiple
instances of a Program if these Program Instances can be run in parallel. For example, the
Program may define a Start Method that has an input argument to specify which resource is
acted upon by its functions. Each instance of the Program is then started designating use of
different resources. The Client can discover all instances of a Program that are running on a
Server. Each instance of a Program is uniquely identified on the Server and is managed
independently by the Client.
4.2.10.3 Program recycling
Programs can be run once or run multiple times (recycled). A Program that is run once will
remain in the Halted state indefinitely once it has run. The normal course of action would be
to delete it following the inspection of its terminal results.
Recyclable Programs may have a limited or unlimited cycle count. These Programs may
require a reset step to transition from the Halted state to the Ready state. This allows for
replenishing resources or reinitializing parameters prior to restarting the Program. The
Program Control Method “Reset” triggers this state transition and any associated actions or
effects.
5 Model
5.1 General
The Program model extends the FiniteStateMachineType and basic ObjectType models
presented in IEC 62541-5. Each Program has a Type Definition that is the subtype of the
FiniteStateMachineType. The ProgramType describes the Finite State Machine model
supported by any Program Invocation of that type. The ProgramType also defines the property

– 14 – IEC 62541-10:2015 © IEC 2015
set that characterizes specific aspects of that Program’s behaviour such as lifetime and
recycling as well as specifying the result data that is produced by the Program.
States
StateMachineObjectType
States
HasComponents
HasSubtype
Transitions
ProgramType
Method
Method
HasSubtype
Methods
MyProgramType
MyProgram
IEC
Figure 4 – Program Type
The base ProgramType defines the standard Finite State Machine specified for all Programs.
This includes the states, transitions, and transition causes (Methods) and effects (Events).
Subtypes of the base ProgramType can be defined to extend or more specifically characterize
the behaviour of an individual Program as illustrated with “MyProgramType” in Figure 4.
5.2 ProgramType
5.2.1 Overview
The additional properties and components that compose the ProgramType are listed in Table
5. No ProgramType specific semantics are assigned to the other base ObjectType or
FiniteStateMachineType Attributes or Properties.

IEC 62541-10:2015 © IEC 2015 – 15 –
Table 5 – ProgramType
Attribute Value
Includes all attributes specified for the FiniteStateMachineType
BrowseName ProgramType
IsAbstract False
References NodeClass BrowseName Data TypeDefinition Modelling
Type Rule
HasProperty Variable Creatable Boolean PropertyType --
HasProperty Variable Deletabe Boolean PropertyType Mandatory
HasProperty Variable AutoDelete Boolean PropertyType Mandatory
HasProperty Variable RecycleCount Int32 PropertyType Mandatory
HasProperty Variable InstanceCount UInt32 PropertyType --
HasProperty Variable MaxInstanceCount UInt32 PropertyType --
HasProperty Variable MaxRecycleCount UInt32 PropertyType --

HasComponent Variable ProgramDiagnostic ProgramDiagn ProgramDiagnosticTy Optional
osticDataType pe
HasComponent Object Halted StateType Mandatory
HasComponent Object Ready StateType Mandatory
HasComponent Object Running StateType Mandatory
HasComponent Object Suspended StateType Mandatory

HasComponent Object HaltedToReady TransitionType Mandatory
HasComponent Object ReadyToRunning TransitionType Mandatory
HasComponent Object RunningToHalted TransitionType Mandatory
HasComponent Object RunningToReady TransitionType Mandatory
HasComponent Object RunningToSuspende TransitionType Mandatory
d
HasComponent Object SuspendedToRunnin TransitionType Mandatory
g
HasComponent Object SuspendedToHalted TransitionType Mandatory
HasComponent Object SuspendedToReady TransitionType Mandatory
HasComponent Object ReadyToHalted TransitionType Mandatory

HasComponent Method Start  Optional
HasComponent Method Suspend  Optional
HasComponent Method Reset  Optional
HasComponent Method Halt  Optional
HasComponent Method Resume  Optional

HasComponent Object FinalResultData BaseObjectType Optional

– 16 – IEC 62541-10:2015 © IEC 2015
5.2.2 ProgramType Properties
The Creatable Property is a boolean that specifies if Program Invocations of this
ProgramType can be created by a Client. If False, these Program Invocations are persistent
or may only be created by the Server.
The Deletable Property is a boolean that specifies if a Program Invocation of this
ProgramType can be deleted by a Client. If False, these Program Invocations can only be
deleted by the Server.
The AutoDelete Property is a boolean that specifies if Program Invocations of this
ProgramType are removed by the Server when execution terminates. If False, these Program
Invocations persist on the Server until they are deleted by the Client. When the Program
Invocation is deleted, any result data associated with the instance is also removed.
The RecycleCount Property is an unsigned integer that specifies the number of times a
Program Invocation of this type has been recycled or restarted from its starting point (not
resumed). Note that the Reset Method may be required to prepare a Program to be restarted.
The MaxRecycleCount Property is an integer that specifies the maximum number of times a
Program Invocation of this type can be recycled or restarted from its starting point (not
resumed). If the value is less than 0, then there is no limit to the number of restarts. If the
value is zero, then the Program may not be recycled or restarted.
The InstanceCount Property is an unsigned integer that s
...