EN 62541-7:2012

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

EUROPEAN STANDARD
EN 62541-7
NORME EUROPÉENNE
September 2012
EUROPÄISCHE NORM
ICS 25.040.40; 25.100.01
English version
OPC unified architecture -
Part 7: Profiles
(IEC 62541-7:2012)
Architecture unifiée OPC -  OPC Unified Architecture -
Partie 7: Profils Teil 7: Profile
(CEI 62541-7:2012) (IEC 62541-7:2012)

This European Standard was approved by CENELEC on 2012-09-04. 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-7:2012 E
Foreword
The text of document 65E/242/FDIS, future edition 1 of IEC 62541-7, 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
The following dates are fixed:
(dop) 2013-06-04
• 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-09-04
• 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-7:2012 was approved by CENELEC as a European
Standard without any modification.

- 3 - EN 62541-7: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/TR 62541-2 - OPC unified architecture - CLC/TR 62541-2 -
Part 2: Security model
IEC 62541-3 - OPC unified architecture - EN 62541-3 -
Part 3: Address space model
IEC 62541-4 - OPC unified architecture - EN 62541-4 -
Part 4: Services
IEC 62541-5 - OPC unified architecture - EN 62541-5 -
Part 5: Information model
IEC 62541-6 - OPC unified architecture - EN 62541-6 -
Part 6: Mappings
IEC 62541-8 - OPC unified architecture - EN 62541-8 -
Part 8: Data access
IEC 62541-9 - OPC unified architecture - EN 62541-9 -
Part 9: Alarms and conditions
IEC 62541-7 ®
Edition 1.0 2012-07
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
OPC unified architecture –
Part 7: Profiles
Architecture unifiée OPC –
Partie 7: Profils
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX XB
ICS 25.040.40; 25.100.01 ISBN 978-2-83220-285-2

– 2 – 62541-7 © IEC:2012
CONTENTS
FOREWORD . 7
INTRODUCTION . 9
1 Scope . 10
2 Normative references . 10
3 Terms, definitions and abbreviations . 11
3.1 Terms and definitions . 11
3.2 Abbreviations . 11
4 Overview . 12
4.1 General . 12
4.2 ConformanceUnit. 13
4.3 Profiles . 13
4.4 Profile categories . 14
5 ConformanceUnits . 14
5.1 Overview . 14
5.2 Services . 15
5.3 Other Features . 23
6 Profiles . 29
6.1 Overview . 29
6.2 Profile List . 30
6.3 Conventions for Profile definitions . 32
6.4 Applications . 32
6.5 Profile Tables . 34
6.5.1 General . 34
6.5.2 A & C Address Space Instance Client Facet . 34
6.5.3 A & C Alarm Client Facet . 35
6.5.4 A & C Dialog Client Facet . 36
6.5.5 A & C Enable Client Facet . 36
6.5.6 A & C Exclusive Alarming Client Facet . 37
6.5.7 A & C Non-Exclusive Alarming Client Facet . 37
6.5.8 A & C Previous Instances Client Facet . 38
6.5.9 A & C Simple Client Facet . 39
6.5.10 A & E Proxy Facet . 39
6.5.11 AddressSpace Lookup Client Facet . 40
6.5.12 Advanced Type Programming Client Facet . 41
6.5.13 Attribute Read Client Facet . 41
6.5.14 Attribute Write Client Facet . 42
6.5.15 Auditing Client Facet . 42
6.5.16 Base Client Behaviour Facet . 43
6.5.17 Core Client Facet . 44
6.5.18 DataAccess Client Facet. 44
6.5.19 DataChange Subscriber Client Facet . 45
6.5.20 Discovery Client Facet . 45
6.5.21 Event Subscriber Client Facet . 46
6.5.22 Method Client Facet . 47
6.5.23 Node Management Client Facet . 47

62541-7 © IEC:2012 – 3 –
6.5.24 Redundancy Switch Client Facet . 47
6.5.25 Redundant Client Facet . 48
6.5.26 SecurityPolicy – Basic128Rsa15 . 48
6.5.27 SecurityPolicy – Basic256 . 48
6.5.28 SecurityPolicy – None. 49
6.5.29 A & C Acknowledgeable Alarm Server Facet. 49
6.5.30 A & C Address Space Instance Server Facet . 49
6.5.31 A & C Alarm Server Facet . 49
6.5.32 A & C Dialog Server Facet . 50
6.5.33 A & C Enable Server Facet . 50
6.5.34 A & C Exclusive Alarming Server Facet . 50
6.5.35 A & C Non-Exclusive Alarming Server Facet . 51
6.5.36 A & C Previous Instances Server Facet . 51
6.5.37 A & C Simple Server Facet . 51
6.5.38 A & E Wrapper Facet . 52
6.5.39 Address Space Notifier Server Facet . 52
6.5.40 Auditing Server Facet . 53
6.5.41 Base Server Behaviour Facet . 53
6.5.42 Client Redundancy Facet . 53
6.5.43 ComplexType Server Facet . 54
6.5.44 Core Server Facet . 54
6.5.45 Data Access Server Facet . 55
6.5.46 Embedded DataChange Subscription Server Facet . 55
6.5.47 Embedded UA Server Profile . 55
6.5.48 Enhanced DataChange Subscription Server Facet . 56
6.5.49 Method Server Facet . 56
6.5.50 Micro Embedded Device Server . 56
6.5.51 Nano Embedded Device Server . 57
6.5.52 Node Management Server Facet . 57
6.5.53 Redundancy Transparent Server Facet . 57
6.5.54 Redundancy Visible Server Facet . 58
6.5.55 Standard DataChange Subscription Server Facet . 58
6.5.56 Standard Event Subscription Server Facet . 58
6.5.57 Standard UA Server . 59
6.5.58 SOAP-HTTP WS-SC UA Binary . 59
6.5.59 SOAP-HTTP WS-SC UA XML . 60
6.5.60 SOAP-HTTP WS-SC UA XML-UA Binary . 60
6.5.61 UA-TCP UA-SC UA Binary . 60
Bibliography . 61

Figure 1 – Profile – ConformanceUnit – TestCases . 13
Figure 2 – HMI Client Sample . 33
Figure 3 – Embedded Server Sample . 33
Figure 4 – Standard UA Server Sample . 34

Table 1 – Profile Categories . 14
Table 2 – Conformance Groups . 15

– 4 – 62541-7 © IEC:2012
Table 3 – Discovery Services . 16
Table 4 – Session Services . 17
Table 5 – Node Management Services . 18
Table 6 – View Services . 18
Table 7 – Query Services . 19
Table 8 – Attribute Services . 19
Table 9 – Method Services . 20
Table 10 – Monitored Item Services . 20
Table 11 – Subscription Services . 22
Table 12 – Base Information . 23
Table 13 – Security . 24
Table 14 – Protocol and Encoding . 26
Table 15 – Address Space Model . 26
Table 16 – Data Access . 26
Table 17 – Alarms and Conditions . 27
Table 18 – Auditing . 29
Table 19 – Redundancy . 29
Table 20 – Profile List . 30
Table 21 – A & C Address Space Instance Client Facet . 35
Table 22 – A & C Address Space Instance Client Facet Related Server Profiles . 35
Table 23 – A & C Alarm Client Facet . 35
Table 24 – A & C Alarm Client Facet Related Server Profiles . 35
Table 25 – A & C Dialog Client Facet . 36
Table 26 – A & C Dialog Client Facet Related Server Profiles . 36
Table 27 – A & C Enable Client Facet . 36
Table 28 – A & C Enable Client Facet Related Server Profiles . 37
Table 29 – A & C Exclusive Alarming Client Facet . 37
Table 30 – A & C Exclusive Alarming Client Facet Related Server Profiles . 37
Table 31 – A & C Non-Exclusive Alarming Client Facet . 38
Table 32 – A & C Non-Exclusive Alarming Client Facet Related Server Profiles . 38
Table 33 – A & C Previous Instances Client Facet . 38
Table 34 – A & C Previous Instances Client Facet Related Server Profiles . 38
Table 35 – A & C Simple Client Facet . 39
Table 36 – A & C Simple Client Facet Related Server Profiles . 39
Table 37 – A & E Proxy Facet . 39
Table 38 – AddressSpace Lookup Client Facet . 40
Table 39 – AddressSpace Lookup Client Facet Related Server Profiles . 41
Table 40 – Advanced Type Programming Client Facet . 41
Table 41 – Advanced Type Programming Client Facet Related Server Profiles . 41
Table 42 – Attribute Read Client Facet . 42
Table 43 – Attribute Read Client Facet Related Server Profiles. 42
Table 44 – Attribute Write Client Facet . 42
Table 45 – Attribute Write Client Facet Related Server Profiles . 42

62541-7 © IEC:2012 – 5 –
Table 46 – Auditing Client Facet . 43
Table 47 – Auditing Client Facet Related Server Profiles . 43
Table 48 – Base Client Behaviour Facet . 43
Table 49 – Base Client Behaviour Facet Related Server Profiles . 43
Table 50 – Core Client Facet . 44
Table 51 – Core Client Facet Related Server Profiles . 44
Table 52 – DataAccess Client Facet . 44
Table 53 – DataAccess Client Facet Related Server Profiles . 45
Table 54 – DataChange Subscriber Client Facet . 45
Table 55 – DataChange Subscriber Client Facet Related Server Profiles . 45
Table 56 – Discovery Client Facet. 45
Table 57 – Discovery Client Facet Related Server Profiles . 46
Table 58 – Event Subscriber Client Facet . 46
Table 59 – Event Subscriber Client Facet Related Server Profiles . 46
Table 60 – Method Client Facet . 47
Table 61 – Method Client Facet Related Server Profiles . 47
Table 62 – Node Management Client Facet. 47
Table 63 – Node Management Client Facet Related Server Profiles . 47
Table 64 – Redundancy Switch Client Facet . 48
Table 65 – Redundancy Switch Client Facet Related Server Profiles . 48
Table 66 – Redundant Client Facet . 48
Table 67 – Redundant Client Facet Related Server Profiles . 48
Table 68 – SecurityPolicy – Basic128Rsa15 . 48
Table 69 – SecurityPolicy – Basic256 . 49
Table 70 – SecurityPolicy – None . 49
Table 71 – A & C Acknowledgeable Alarm Server Facet . 49
Table 72 – A & C Address Space Instance Server Facet . 49
Table 73 – A & C Alarm Server Facet . 50
Table 74 – A & C Dialog Server Facet . 50
Table 75 – A & C Enable Server Facet . 50
Table 76 – A & C Exclusive Alarming Server Facet . 51
Table 77 – A & C Non-Exclusive Alarming Server Facet . 51
Table 78 – A & C Previous Instances Server Facet . 51
Table 79 – A & C Simple Server Facet . 52
Table 80 – A & E Wrapper Facet . 52
Table 81 – Address Space Notifier Server Facet . 53
Table 82 – Auditing Server Facet . 53
Table 83 – Base Server Behaviour Facet . 53
Table 84 – Client Redundancy Facet . 53
Table 85 – ComplexType Server Facet . 54
Table 86 – Core Server Facet . 54
Table 87 – Data Access Server Facet . 55
Table 88 – Embedded DataChange Subscription Server Facet . 55

– 6 – 62541-7 © IEC:2012
Table 89 – Embedded UA Server Profile . 56
Table 90 – Enhanced DataChange Subscription Server Facet. 56
Table 91 – Method Server Facet . 56
Table 92 – Micro Embedded Device Server . 57
Table 93 – Nano Embedded Device Server . 57
Table 94 – Node Management Server Facet . 57
Table 95 – Redundancy Transparent Server Facet. 57
Table 96 – Redundancy Visible Server Facet . 58
Table 97 – Standard DataChange Subscription Server Facet . 58
Table 98 – Standard Event Subscription Server Facet . 59
Table 99 – Standard UA Server . 59
Table 100 – SOAP-HTTP WS-SC UA Binary . 60
Table 101 – SOAP-HTTP WS-SC UA XML . 60
Table 102 – SOAP-HTTP WS-SC UA XML-UA Binary . 60
Table 103 – UA-TCP UA-SC UA Binary. 60

62541-7 © IEC:2012 – 7 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
OPC UNIFIED ARCHITECTURE –
Part 7: Profiles
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-7 has been prepared by subcommittee 65E: Devices and
integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.
The text of this standard is based on the following documents:
FDIS Report on voting
65E/242/FDIS 65E/267/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.

– 8 – 62541-7 © IEC:2012
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.
62541-7 © IEC:2012 – 9 –
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.
– 10 – 62541-7 © IEC:2012
OPC UNIFIED ARCHITECTURE –
Part 7: Profiles
1 Scope
This part of the IEC 62541 series describes the OPC Unified Architecture Profiles. The
Profiles are used to describe the functionality that an OPC UA Server exposes or that an OPC
UA Client consumes. The details of the functionality are specified in other parts of IEC 62541.
Profiles are used by vendors to advertise the OPC UA capabilities of their products. The
Profiles a product supports will typically appear on product data sheets. Buyers will use this
Profile information to specify and purchase products that work together and meet specific
application requirements. Most OPC UA applications will conform to several, but not all of the
Profiles.
Profiles are used to segregate features with regard to testing of OPC UA Products and the
nature of the testing. This includes the testing performed by the OPC Foundation provided
OPC UA Compliance Test Tool and by the OPC Foundation provided Independent
Certification Test Labs. This could equally as well refer to test tools provided by another
organization or a test lab provided by another organization, what is important is the concept of
automated tool based testing verse lab based testing. The scope of this specification includes
defining functionality that can only be tested in an a lab and defining the grouping of
functionality that is to be used when testing OPC UA products either in a lab or using
automated tools. The definition of actual TestCases is not within the scope of this document,
but the general categories of TestCases are within the scope of this document.
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/TR 62541-2, OPC Unified Architecture – Part 2: Security Model
IEC 62541-3, OPC unified architecture – Part 3: Address Space Model
IEC 62541-4, OPC unified architecture – Part 4: Services
IEC 62541-5, OPC unified architecure – Part 5: Information Model
IEC 62541-6, OPC unified architecure – Part 6: Mappings
IEC 62541-8, OPC unified architecture – Part 8: Data Access
IEC 62541-9, OPC Unified architecure – Part 9: Alarms and conditions

62541-7 © IEC:2012 – 11 –
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62541-1,
IEC 62541-2, IEC 62541-3, IEC 62541-4, IEC 62541-6, IEC 62541-8 and the following apply.
3.1.1
Application
a body of code or piece of hardware that executes or implements some aspect of OPC UA
Note 1 to entry: The application could run on any machine and perform any function. The application could be
software or it could be a hardware application, the only requirement is that it implements OPC UA
3.1.2
ConformanceUnit
specific set of features that can be tested as a single entity
Note 1 to entry: A ConformanceUnit can cover a group of services, portions of services or information models. For
additional detail see section 4.2
3.1.3
ConformanceGroup
group of conformance units that is given a name
Note 1 to entry: This grouping is only to assist in organizing ConformanceUnits. Typical ConformanceGroups
include groups for each of the service sets in OPC UA and each of the Information Model specifications.
3.1.4
Facet
profile that is a subset of the ConformanceUnits a Server or Client may require
Note 1 to entry: Facet are typically combined to form full function Profiles. The use of the term Facet in the title of
a Profile indicates that the given Profile is not a standalone profile.
3.1.5
ProfileCategory
a grouping of Profiles into major functionality groups, such as Server or Clients
Note 1 to entry: These categories help developers and users determine the type of type of Application that a
given Profile would be used for. For additional details see section 4.4
3.1.6
TestCase
technical description of a set of steps required to test a particular function or information
model
Note 1 to entry: TestCases provide sufficient details to allow a developer to implement them in code. A TestCases
also provide a detailed summary of the expected result(s) from the execution of the implemented code and any
precondition(s) that must be established before the TestCase can be executed.
3.1.7
TestLab
location that is designed to provide testing services
Note 1 to entry: These services include but are not limited to personal that directly perform testing, automated
testing and a formal repeatable process. The OPC Foundation has provided detailed specification describing OPC
UA TestLabs and the testing they are to provided (see Compliance Part 8 UA Server, Compliance Part 9 UA
Client).
3.2 Abbreviations
A&C Alarms and Conditions
– 12 – 62541-7 © IEC:2012
A&E Alarms and Events
API Application Programming Interface
DA Data Access
HA Historical Access
HMI Human Machine Interface
UA Unified Architecture
4 Overview
4.1 General
The OPC Unified Architecture multipart specification describes a number of Services and a
variety of information models. These Services and information models can be referred to as
features of a Server or Client. Servers and Clients need to be able to describe which features
they support. This part provides a grouping of these features. The individual features are
grouped into ConformanceUnits which are further grouped into Profiles. Figure 1 provides an
overview of the interactions between Profiles, ConformanceUnits and TestCases. The large
arrows indicate the components that are used to construct the parent. For example a Profile is
constructed from Profiles and ConformanceUnits. The figure also illustrates a feature of the
OPC UA compliance test tool, in that it will test if a requested Profile passes all
ConformanceUnits. It will also test all other ConformanceUnits and report any other Profiles
that pass conformance testing. The individual TestCases are defined in separate documents
see Compliance Part 8 UA Server and Compliance Part 9 UA Client. The TestCases are
related back to the appropriate ConformanceUnits defined in this specification. This
relationship is also displayed by the OPC UA Compliance Test Tool.

62541-7 © IEC:2012 – 13 –
Profiles /
Grouped into
Facets
ProfileCategories
Will determine
Composed Conformant Profile(s)
for Application
of
Other
Profiles /
Facets
Organized by
Conformance Process Test Cases
Conformance
For Conformance Unit
Groups Units
Each
Conformance
UA
Unit is
Application Compliance
Composed of
Tests
Will execute
Test Cases
IEC  1472/12
Figure 1 – Profile – ConformanceUnit – TestCases
4.2 ConformanceUnit
Each ConformanceUnit represents a specific set of features (e.g. a group of services, portions
of services or information models) that can be tested as a single entity. ConformanceUnits are
the building blocks of a Profile. Each ConformanceUnit can also be used as a test category.
For each ConformanceUnit, there would be a number of TestCases that test the functionality
described by the ConformanceUnit. The description of a ConformanceUnit is intended to
provide enough information to illustrate the required functionality, but in many cases to obtain
a complete understanding of the ConformanceUnit the reader may be required to also
examine the appropriate part of the OPC UA specification. Additional information regarding
testing of a ConformanceUnit is provided in the Compliance Part 8 UA Server or
Compliance Part 9 UA Client test specifications.
The same features do not appear in more than one ConformanceUnit.
4.3 Profiles
Profiles are named groupings of ConformanceUnits. The Servers and Clients in an OPC UA
application will provide the names of Profiles that they support. The definition of Profiles is a
dynamic activity, in that it is expected that new Profiles will be added in the future. A Profile
can be defined to inherit from an existing Profile. The new Profile may add additional
ConformanceUnits. These additional ConformanceUnits may add additional features that are
to be tested. The additional ConformanceUnits may also further restrict inherited
ConformanceUnits.
– 14 – 62541-7 © IEC:2012
An OPC UA Application will typically support multiple Profiles.
Multiple Profiles may include the same ConformanceUnit.
Testing of a Profile consists of testing the individual ConformanceUnits that comprise the
Profile.
Profiles are named based on naming conventions (see 6.3 for details)
4.4 Profile categories
Profiles are grouped into categories to help vendors and end users understand the
applicability of a Profile. Categories include: Server and Client, but other example could also
include power generation or chemical plant. A Profile shall be assigned to one or more
categories.
Table 1 contains the list of currently defined ProfileCategories.
Table 1 – Profile Categories
Category Description
Client Profiles of this category specify a complete functional set for an OPC UA Client. The
URI of such profiles has to be part of a Software Certificate passed in the
CreateSession request.
Discovery Server Profiles of this category are for Discovery Servers
External Profiles that are defined outside
Security Profiles of this category specify a security policy. The URI of such profiles has to be
part of an Endpoint Description returned from the GetEndpoint service.
Server Profiles of this category specify a complete functional set for an OPC UA Server. The
URI of such profiles has to be part of a Software Certificate returned with the
CreateSession service response.
Transport Profiles of this category specify a specific protocol mapping. The URI of such profiles
has to be part of an Endpoint Description.

5 ConformanceUnits
5.1 Overview
A ConformanceUnit represents an individuall
...