A ConformanceUnitrepresents an individually testable entity. For improved clarity, the large list of ConformanceUnitsis arranged into named ConformanceGroups. These groups reflect the Service Setsin OPC 10000-4and the OPC UA information models. Table 2lists the ConformanceGroups. These groups and the ConformanceUnitsthat they describe are detailed in the Subclauses of chapter 5starting with clause 5.2. ConformanceGroupshave no impact on testing; they are used only for organizational reasons, i.e. to simplify the readability of this document.
Group |
Description |
Address Space Model |
Defines ConformanceUnitsfor various features of the OPC UA AddressSpace. |
Aggregates |
All ConformanceUnitsthat are related to Aggregates, including individual ConformanceUnitsfor each supported Aggregate as described in Part 13. |
Alarmsand Conditions |
All ConformanceUnitsthat are associated with the OPC UA Information Model for Conditions, acknowledgeable Conditions, confirmations and Alarmsas specified in Part 9. |
Includes ConformanceUnitsto read or write current or historical Attributevalues. |
|
Auditing |
User level security includes support for security audit trails, with traceability between Clientand Serveraudit logs. |
Base Information |
All information elements as defined in Part 5. |
Data Access |
ConformanceUnitsspecific to Clientsand Serversthat deal with the representation and use of automation data as specified in Part 8. |
ConformanceUnitswhich focus on ServerEndpoint Discovery. |
|
GDS |
Conformance Units for a GDS. Includes units for global discovery and global certificate management. |
Historical Access |
|
Methods represent the function calls of Objects. Methods are invoked and return only after completion (successful or unsuccessful). |
|
Miscellaneous |
This group contains ConformanceUnitsthat cover miscellaneous subjects, such as recommended behaviours, documentation etc. These ConformanceUnitstypically do not fit into any of the other groups. |
Monitored Item Services |
Clientsdefine MonitoredItemsto subscribe to data and Events. Each MonitoredItemidentifies the item to be monitored and the Subscriptionto use to send Notifications. |
Bundles ConformanceUnitsfor all Servicesto add and delete OPC UA AddressSpace Nodesand References. |
|
Protocol and Encoding |
Covers all transport and encoding combinations that are specified in Part 6. |
Redundancy |
The design of OPC UA ensures that vendors can create redundant Clientsand redundant Serversin a consistent manner. Redundancy may be used for high availability, fault tolerance and load balancing. |
Security |
Security related ConformanceUnitsthat can be profiled this includes all aspects of security. |
An (OPC UA) Sessionis an application layer connection. |
|
Subscriptions are used to report Notificationsto the Client. |
|
View Services |
Clientsuse the View ServiceSet to navigate through the OPC UA AddressSpaceor through a View (a subset) of the OPC UA AddressSpace. |