Table 15includes a list of FunctionalGroupswith name and purpose. If Serversexpose a FunctionalGroupthat corresponds to the described purpose, they should use the recommended BrowseNamewith the Namespace of this specification.
Table 15– Recommended FunctionalGroup BrowseNames
|
BrowseName |
Purpose |
|
Configuration |
Parametersrepresenting the configuration items of the TopologyElement. If the CurrentWritebit is set in the AccessLevel Attributethey can be modified by Clients. |
|
Tuning |
Parametersand Methodsto optimize the behavior of the TopologyElement. |
|
Maintenance |
Parametersand Methodsuseful for maintenance operations. |
|
Diagnostics |
Parametersand Methodsfor diagnostics. |
|
Statistics |
Parametersand Methodsfor statistics. |
|
Status |
Parameterswhich describe the general health of the TopologyElement. This can include diagnostic Parameters. |
|
Operational |
Parametersand Methodsuseful for during normal operation, like process data. |
|
OperationCounters |
Parametersrepresenting numbers of interest when managing a TopologyElementwhile 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). Parametersare often domain specific. Some common ones are defined in the OperationCounter Interface (see 4.5.5).This FunctionalGroupmight be organized into other FunctionalGroups, so Clientsshall expect that they need to browse several hops to get to allOperationCounters. |
|
Identification |
ThePropertiesof the VendorNameplate Interface, like Manufacturer, SerialNumber or Propertiesof the TagNameplate will usually be sufficient as identification. If other Parametersor even Methodsare required, all elements needed shall be organized in a FunctionalGroupcalled Identification. See Annex B.1for an example. |