IEC 62541 -7:2020 pdf download – 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 addresses: • IEC Electropedia: available at http://www.electropedia.org/ • ISO Online browsing platform: available at http://www.iso.org/obp 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.
4 Overview 4.1 General The IEC 62541 series, which is the OPC Unified architecture standard, 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 and wish to have certified. This document 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 (CTT), 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 document. This relationship is also displayed by the OPC UA Compliance Test Tool.
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 OPC UA. Additional Information regarding testing of a ConformanceUnit are provided in the Compliance Part 8 UA Server or Compliance Part 9 UA Client test standards. The same features do not appear in more than one ConformanceUnit. 4.3 Profiles A Profile is a named aggregation of ConformanceUnits and other Profiles. To support a Profile, an application has to support the ConformanceUnits and all aggregated Profiles. The definition of Profiles is an ongoing activity, in that it is expected that new Profiles will be added in the future. 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.