Table 15 includes a list of FunctionalGroups with name and purpose. If Servers expose a FunctionalGroup that corresponds to the described purpose, they should use the recommended BrowseName with the Namespace of this specification.

Table 15 – Recommended FunctionalGroup BrowseNames




Parameters representing the configuration items of the TopologyElement. If the CurrentWrite bit is set in the AccessLevel Attribute they can be modified by Clients.


Parameters and Methods to optimize the behavior of the TopologyElement.


Parameters and Methods useful for maintenance operations.


Parameters and Methods for diagnostics.


Parameters and Methods for statistics.


Parameters which describe the general health of the TopologyElement. This can include diagnostic Parameters.


Parameters and Methods useful for during normal operation, like process data.


Parameters representing numbers of interest when managing a TopologyElement while it is operated.

Examples are the hours of operation, hours in standby, etc. Those are often the base to calculate KPIs (key performance indicators) like the OEE (overall equipment efficiency).

Parameters are often domain specific. Some common ones are defined in the OperationCounter Interface (see 4.5.5).This FunctionalGroup might be organized into other FunctionalGroups, so Clients shall expect that they need to browse several hops to get to all OperationCounters.


The Properties of the VendorNameplate Interface, like Manufacturer, SerialNumber or Properties of the TagNameplate will usually be sufficient as identification. If other Parameters or even Methods are required, all elements needed shall be organized in a FunctionalGroup called Identification. See Annex B.1 for an example.