For the purposes of this document, the terms and definitions given in OPC 10000-1, OPC 10000-2, and OPC 10000-3, and OPC 10000-4 as well as the following apply. An overview of the terms defined in this standard and their interaction can be viewed in Figure 1.

a 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.

a Profile that defines all features necessary to build a functional OPC UA application

Note 1 to entry: An Application Profile in particular adds definitions of the transport and security requirements. Application Profiles are organized in the “Application Profiles” ProfileCategory.

a 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.

a 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.

a 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.

arranges Profiles into application classes, such as Server or Client

Note 1 to entry: These categories help determine what a given Profile is used for. For additional details see 0.

a 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 must be established before the TestCase can be executed.

a 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).

DAData Access

CTTCompliance Test Tool

HAHistorical Access

HMIHuman Machine Interface