IEC 62541-7-2020 OPC unified architecture – Part 7: Profiles.
3 Terms, definitions, and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC TR 62541 -1 ,
IEC TR 62541 -2, IEC 62541 -3, IEC 62541 -4, IEC 62541 -6, and IEC 62541 -8 and the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following
• IEC Electropedia: available at
• ISO Online browsing platform: available at
NOTE An overview of the terms defined in this document and their interaction can be viewed in Figure 1 .
3.1.1 application
software program 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 OPC UA 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.
3.1.3 ConformanceGroup
group of ConformanceUnits 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 standards.
3.1.4 Facet
Profile dedicated to a specific feature that a Server or Client may require
Note 1 to entry: Facets are typically combined to form higher-level 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 FullFeatured Profile
Profile that defines all features necessary to build a functional OPC UA Application
Note 1 to entry: A FullFeatured Profile in particular adds definitions of the transport and security requirements.
3.1.6 ProfileCategory
category which arranges Profiles into application classes, such as Server or Client
Note 1 to entry: These categories help determine the type of Application that a given Profile would be used for.
For additional details see 4.4.
3.1.7 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. TestCases also provide a detailed summary of the expected result(s) from the execution of the implemented code and any precondition(s) that shall be established before the TestCase can be executed.
3.1.8 TestLab
facility that is designated 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 standard describing OPC UA
TestLabs and the testing they are to provided (see Compliance Part 8 UA Server, Compliance Part 9 UA Client).
3.2 Abbreviated terms
DA data access
HA historical access
HMI human machine interface
NIST National Institute of Standard and Technology
PKI Public Key Infrastructure
RSA Rivest-Shamir-Adleman
UA Unified Architecture.IEC 62541-7 pdf download.