Structure of a plant model (RT Unified) - WinCC Unified

Basic principles

With object oriented configuration, a configured plant object corresponds to a real plant object. Basically, the number of plant objects is determined by the plant hierarchy.

Whether you need to map each plant object with a plant object type is determined by the following factors:

• Relevance of the plant object type for the process visualization

• Depth of the plant hierarchy that is to be mapped

• Degree of reuse

The specific function of a plant object is clear from its position in the plant hierarchy.

For example, the function of a "Drive" plant object is only revealed in the plant hierarchy:

Depth of the plant hierarchy

Define any depth of the plant hierarchy The depth of the plant hierarchy depends essentially on the number of plant objects. A deep plant hierarchy leads to a precise fault localization. You can then, for example, formulate the concise alarm text.

The context of the plant object is also taken into account in runtime, for example, in the localization of faults. The following figure uses the example of the "Temperature exceeded" alarm to show the advantage a deep hierarchy offers in runtime:

Configuration data at the plant object type

The following configuration data are created during the definition of a plant object type:

• Properties through which data is exchanged inside and outside of WinCC Unified PC RT.

• HMI visualization: Alarms, logs

• KPIs