SIST EN 62541-10:2012

OPC Unified Architecture - Part 10: Programs (IEC 62541-10:2012)

This part of the IEC 62541 series specifies the standard representation of Programs as part of the OPC Unified Architecture and its defined information model. 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.

OPC Unified Architecture - Teil 10: Programme (IEC 62541-10:2012)

Architecture unifiée OPC - Partie 10: Programme (CEI 62541-10:2012)

La CEI 62541-10:2012 spécifie la représentation normalisée des Programmes faisant partie intégrante de l'Architecture Unifiée OPC et son modèle d'information défini. Elle comprend la description des Classes de N uds, et des Propriétés, Méthodes et Évènements normalisés, ainsi que les paramètres associés relatifs au comportement et aux informations applicables aux Programmes.

Enotna arhitektura OPC - 10. del: Programi (IEC 62541-10:2012)

Ta del serije IEC 62541 določa standardni nabor programov kot del enotne arhitekture OPC in njenega definiranega informacijskega modela. To vključuje opis razredov vozlišč, standardnih lastnosti, metod in dogodkov ter povezanega delovanja in informacij za programe. Celoten model naslovnega prostora je z vsemi razredi vozlišč in atributi naveden v standardu IEC 62541-3. Storitve, na primer za priklic metod za upravljanje programov, so opredeljene v standardu IEC 62541-4.

General Information

• Status: Withdrawn
• Publication Date: 09-Oct-2012
• Withdrawal Date: 09-Jan-2018
• ICS: 25.040.40 - Industrial process measurement and control
• ICS: 35.240.50 - IT applications in industry
• Technical Committee: MOV - Measuring equipment for electromagnetic quantities
• Current Stage: 9900 - Withdrawal (Adopted Project)
• Start Date: 10-Jan-2018
• Due Date: 02-Feb-2018
• Completion Date: 10-Jan-2018
• Ref Project: EN 62541-10:2012 - OPC unified architecture - Part 10: Programs

Relations

• Replaced By: SIST EN 62541-10:2015 - OPC Unified Architecture - Part 10:Programs (IEC 62541-10:2015)
• Effective Date: 10-Dec-2013

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN 62541-10:2012
01-november-2012
Enotna arhitektura OPC - 10. del: Programi (IEC 62541-10:2012)
OPC Unified Architecture - Part 10: Programs (IEC 62541-10:2012)
OPC Unified Architecture - Teil 10: Programme (IEC 62541-10:2012)
Architecture unifiée OPC - Partie 10: Programme (CEI 62541-10:2012)
Ta slovenski standard je istoveten z: EN 62541-10:2012
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
SIST EN 62541-10:2012 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST EN 62541-10:2012

---------------------- Page: 2 ----------------------

SIST EN 62541-10:2012

EUROPEAN STANDARD
EN 62541-10

NORME EUROPÉENNE
September 2012
EUROPÄISCHE NORM

ICS 25.040.40; 25.100.01


English version


OPC unified architecture -
Part 10: Programs
(IEC 62541-10:2012)


Architecture unifiée OPC -  OPC Unified Architecture -
Partie 10: Programmes Teil 10: Programme
(CEI 62541-10:2012) (IEC 62541-10:2012)





This European Standard was approved by CENELEC on 2012-08-31. 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.

CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung

Management Centre: Avenue Marnix 17, B - 1000 Brussels


© 2012 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. EN 62541-10:2012 E

---------------------- Page: 3 ----------------------

SIST EN 62541-10:2012
EN 62541-10:2012 - 2 -
Foreword
The text of document 65E/244/FDIS, future edition 1 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:2012.

The following dates are fixed:
(dop) 2013-05-31
• latest date by which the document has
to be implemented at national level by
publication of an identical national
standard or by endorsement
(dow) 2015-08-31
• latest date by which the national
standards conflicting with the
document have to be withdrawn

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.

Endorsement notice
The text of the International Standard IEC 62541-10:2012 was approved by CENELEC as a European
Standard without any modification.

---------------------- Page: 4 ----------------------

SIST EN 62541-10:2012
- 3 - EN 62541-10:2012
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  When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD
applies.

Publication Year Title EN/HD Year

IEC/TR 62541-1 - OPC unified architecture - CLC/TR 62541-1 -
Part 1: Overview and concepts


IEC 62541-3 2010 OPC unified architecture - EN 62541-3 2010
Part 3: Address space model


IEC 62541-4 2011 OPC unified architecture - EN 62541-4 2011
Part 4: Services


IEC 62541-5 - OPC unified architecture - EN 62541-5 -
Part 5: Information model


IEC 62541-7 - OPC unified architecture - EN 62541-7 -
Part 7: Profiles

---------------------- Page: 5 ----------------------

SIST EN 62541-10:2012

---------------------- Page: 6 ----------------------

SIST EN 62541-10:2012




IEC 62541-10

®


Edition 1.0 2012-07




INTERNATIONAL



STANDARD




NORME



INTERNATIONALE
colour

inside










OPC unified architecture –

Part 10: Programs




Architecture unifiée OPC –

Partie 10: Programmes

















INTERNATIONAL

ELECTROTECHNICAL

COMMISSION


COMMISSION

ELECTROTECHNIQUE

PRICE CODE
INTERNATIONALE

CODE PRIX X


ICS 25.040.40; 25.100.01 ISBN 978-2-83220-284-5



Warning! Make sure that you obtained this publication from an authorized distributor.

Attention! Veuillez vous assurer que vous avez obtenu cette publication via un distributeur agréé.

® Registered trademark of the International Electrotechnical Commission
Marque déposée de la Commission Electrotechnique Internationale

---------------------- Page: 7 ----------------------

SIST EN 62541-10:2012
– 2 – 62541-10 © IEC:2012
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
2 Normative references . 7
3 Terms, definitions and abbreviations . 7
3.1 Terms and definitions . 7
3.2 Abbreviations . 8
4 Concepts . 8
4.1 General . 8
4.2 Programs . 9
4.2.1 Overview . 9
4.2.2 Program Finite State Machine . 10
4.2.3 Program States . 11
4.2.4 State Transitions . 11
4.2.5 Program State Transition Stimuli . 12
4.2.6 Program Control Methods . 12
4.2.7 Program State Transition Effects . 13
4.2.8 Program Result Data . 13
4.2.9 Program Lifetime . 13
5 Model . 14
5.1 General . 14
5.2 ProgramType. 15
5.2.1 Overview . 15
5.2.2 ProgramType Properties . 17
5.2.3 ProgramType Components . 17
5.2.4 ProgramType Causes (Methods) . 23
5.2.5 ProgramType Effects (Events) . 24
5.2.6 AuditProgramTransitionEventType . 27
5.2.7 FinalResultData . 28
5.2.8 ProgramDiagnosticType . 28
Annex A (informative) Program Example . 30

Figure 1 – Automation facility control . 9
Figure 2 – Program illustration . 10
Figure 3 – Program States and Transitions . 11
Figure 4 – Program Type . 15
Figure 5 – Program FSM References . 18
Figure 6 – ProgramType Causes and Effects . 23
Figure A.1 – Program Example . 30
Figure A.2 – DomainDownload State Diagram . 31
Figure A.3 – DomainDownloadType Partial State Model . 38
Figure A.4 – ReadyToRunning Model . 41
Figure A.5 – OpeningToSending ToClosing Model . 43
Figure A.6 – RunningToSuspended Model . 44

---------------------- Page: 8 ----------------------

SIST EN 62541-10:2012
62541-10 © IEC:2012 – 3 –
Figure A.7 – SuspendedToRunning Model . 45
Figure A.8 – RunningToHalted – Aborted Model . 46
Figure A.9 – SuspendedToAborted Model . 47
Figure A.10 – RunningToCompleted Model . 48
Figure A.11 – Sequence of Operations . 49

Table 1 – Program Finite State Machine . 10
Table 2 – Program States . 11
Table 3 – Program State Transitions . 12
Table 4 – Program Control Methods . 12
Table 5 – ProgramType . 16
Table 6 – Program States . 19
Table 7 – Program Transitions . 20
Table 8 – ProgramType Causes . 23
Table 9 – ProgramTransitionEventType . 25
Table 10 – ProgramTransitionEvents . 26
Table 11 – AuditProgramTransitionEventType . 27
Table 12 – ProgramDiagnosticType . 28
Table A.1 – DomainDownload States . 32
Table A.2 – DomainDownload Type . 34
Table A.3 – Transfer State Machine Type . 35
Table A.4 – Transfer State Machine – States . 36
Table A.5 – Finish State Machine Type . 36
Table A.6 – Finish State Machine – States . 37
Table A.7 – DomainDownload Type Property Attributes Variable Values . 37
Table A.8 – Additonal DomainDownload Transition Types . 39
Table A.9 – Start Method Additions . 41
Table A.10 – StartArguments . 42
Table A.11 – Intermediate Results Object . 43
Table A.12 – Intermediate Result Data Variables . 44
Table A.13 – Final Result Data . 47
Table A.14 – Final Result Variables . 48

---------------------- Page: 9 ----------------------

SIST EN 62541-10:2012
– 4 – 62541-10 © IEC:2012
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 interna-
tional 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, Tech-
nical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publica-
tion(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 Interna-
tional 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 inter-
ested 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 misinter-
pretation 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 be-
tween 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 ex-
penses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC Publica-
tions.
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 meas-
urement, control and automation.
The text of this standard is based on the following documents:
FDIS Report on voting
65E/244/FDIS 65E/269/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 archi-
tecture, can be found on the IEC website.

---------------------- Page: 10 ----------------------

SIST EN 62541-10:2012
62541-10 © IEC:2012 – 5 –
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 re-
lated 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 understand-
ing of its contents. Users should therefore print this document using a colour printer.

---------------------- Page: 11 ----------------------

SIST EN 62541-10:2012
– 6 – 62541-10 © IEC:2012
INTRODUCTION
This International Standard is a specification intended for developers of OPC UA applications.
The specification is a result of an analysis and design process to develop a standard interface
to facilitate the development of applications by multiple vendors that inter-operate seamlessly
together.

---------------------- Page: 12 ----------------------

SIST EN 62541-10:2012
62541-10 © IEC:2012 – 7 –
OPC UNIFIED ARCHITECTURE –

Part 10: Programs



1 Scope
This part of the IEC 62541 series specifies the standard representation of Programs as part of
the OPC Unified Architecture and its defined information model. 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 Pro-
grams 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 amend-
ments) applies.
IEC/TR 62541-1, OPC Unified Architecture – Part 1: Overview and Concepts
IEC 62541-3:2010, OPC unified architecture – Part 3: Address Space Model
IEC 62541-4:2011, OPC unified architecture – Part 4: Services
IEC 62541-5, OPC unified architecure – Part 5: Information Model
IEC 62541-7, OPC unified architecture – Part 7: Profiles
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC/TR 62541-1 and
IEC 62541-3, as well as the following apply.
3.1.1
function
programmatic task performed at 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

---------------------- Page: 13 ----------------------

SIST EN 62541-10:2012
– 8 – 62541-10 © IEC:2012
3.1.3
ProgramType
ObjectType Node that represents the type definition of a Program and is a subtype of the
FiniteStateMachineType
3.1.4
Program Control Method
Method specified by this specification 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: The Program Invocation is distinguished from other Object instances of the same ProgramType
by the object node’s unique browse path.
3.2 Abbreviations
API Application Programming Interface
DA Data Access
FSM Finite State Machine
HMI Human Machine Interfaces
PCM Program Control Method
PGM Program
PI Program Invocation
PLC Programmable Logic Controller
UA Unified Architecture
UML Unified Modelling Language
4 Concepts
4.1 General
Integrated automation facilities manage their operations through the exchange of data and
coordinated invocation of system functions like 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 Pro-
grams as an interoperable way to advertise, discover, and request these functions. They pro-
vide a normalizing mechanism for the semantic description, invocation of, 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.

---------------------- Page: 14 ----------------------

SIST EN 62541-10:2012
62541-10 © IEC:2012 – 9 –
Filling
Cleaning
Labelling
Palletizing
Packaging

IEC  1511/12
Figure 1 – Automation facility control
Methods and Programs model functions typically having different scopes, behaviours, life-
times, 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, 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. Meth-
ods and their invocation mechanism are described in IEC 62541-3 and IEC 62541-4.
This specification describes the extensions to, or specific use of the core capabilities defined
in IEC 62541-5. Support for the feature described in this specification is described by means
of Profiles in IEC 62541-7.
4.2 Programs
4.2.1 Overview
Programs are complex functions in a server or underlying system that can be invoked and
managed by an OPC UA 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.

---------------------- Page: 15 ----------------------

SIST EN 62541-10:2012
– 10 – 62541-10 © IEC:2012

Program

Control Methods
________()
Manage
________()
________()
State Machine
_________
Get Description
_________
_________
Transition Events
_________
Monitor
_________

_________
Result Data
_________
Get Results
_________

_________

IEC  1512/12
Figure 2 – Program illustration
Programs are state full, transitioning through a prescribed sequence of states as they exe-
cute. 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 tran-
sitions.
4.2.2 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
Report Transition 5
5 RunningToSuspended Suspend Method Running Suspended
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

---------------------- Page: 16 ----------------------

SIST EN 62541-10:2012
62541-10 © IEC:2012 – 11 –
HALTED
1

9
3
READY
2
4 7
8
RUNNING
5
6
SUSPENDED
IEC  1513/12

Figure 3 – Program States and Transitions
4.2.3 Program States
A standard set of base states are 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 sup-
port 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 substates can be
defined for the base states to provide more resolution to the process and to describe the
cause and effects of additional stimuli and transitions. Standards bodies and industry groups
may extend the base Program Finite State Model to conform to industry models. For example,
the Halted state can include the sub states “Aborted” and “Completed” to indicate if the func-
tion 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.4 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.

---------------------- Page: 17 ----------------------

SIST EN 62541-10:2012
– 12 – 62541-10 © IEC:2012
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 RunningToSuspend
...