Structuring WinCC Picture Tree Manager Hierarchies: Aligning Order and Empty Containers with Plant Hierarchy

In SIMATIC PCS 7, when graphic pictures in WinCC Picture Tree Manager appear in an unexpected sequence or fail to reflect the desired operator screen navigation order after OS compilation, the cause is automated Plant Hierarchy (PH) derivation. By default, PCS 7 derives the picture tree directly from the Plant Hierarchy in SIMATIC Manager, sorting folders and pictures alphabetically. To customize picture order and insert empty navigation containers without having them overwritten by subsequent compilations, engineers must configure the Plant Hierarchy directly in SIMATIC Manager by inserting empty hierarchy folders or numerical prefixes, or disable 'Derive picture hierarchy from the plant hierarchy' in Plant Hierarchy properties.

Executive Summary

During the design of operator screen navigation in SIMATIC PCS 7, commissioning engineers frequently spend hours manually organizing container nodes, re-arranging picture buttons, and structuring overview levels in WinCC Picture Tree Manager. However, after the next OS compilation from SIMATIC Manager, all manual changes in Picture Tree Manager are erased, and the navigation tree reverts to the default alphabetical structure derived from the Plant Hierarchy. This guide clarifies the automated derivation rules between SIMATIC Manager and WinCC, explains container node inheritance, and provides standard methods to achieve customized navigation layouts.

Architecture and Fundamental Mechanics

The PCS 7 picture navigation architecture coordinates the engineering database with WinCC runtime navigation:
1. Plant Hierarchy Derivation Mechanism:
When 'Derive picture hierarchy from the plant hierarchy' is selected in SIMATIC Manager (Options -> Plant Hierarchy -> Customize), the OS compiler reads the Plant View hierarchy folders (Area, Unit, Equipment Module). For every hierarchy folder flagged with 'OS area' or containing an assigned graphic picture (.pdl), the compiler generates corresponding container and picture nodes inside the WinCC Picture Tree Manager database (@PT_...).
2. Sorting Logic and Container Creation:
- Alphabetical Sorting: By default, the OS compiler orders child folders alphabetically. A picture named Feed_Water will always precede Steam_Header.
- Empty Container Insertion: If an operator screen requires a parent menu button with no associated direct background picture (a container solely holding sub-pictures), inserting a hierarchy folder in SIMATIC Manager without assigning a .pdl picture generates an empty container node in Picture Tree Manager.
3. Manual vs. Automated Management:
- Automated Mode (Recommended): All sorting, container nesting, and picture assignments are managed in SIMATIC Manager. Compilations overwrite Picture Tree Manager cleanly.
- Independent Mode: Unchecking 'Derive picture hierarchy' detaches Picture Tree Manager. Engineers can freely drag, re-order, and insert containers directly in WinCC without risk of compiler overwrite.

Step-by-Step Implementation Procedure

Option A - Managing Structure within Plant Hierarchy (Recommended Standard):
a. Open the multiproject in SIMATIC Manager and switch to Plant View (View -> Plant View).
b. To control button sorting order in the WinCC overview area, use numerical prefixes on hierarchy folder names (e.g., 10_Water_Treatment, 20_Boiler_Island, 30_Turbine).
c. To create an empty container node in the WinCC navigation bar, insert a hierarchy folder under the desired plant level and leave its 'Assigned OS Picture' property unassigned.
d. Assign target graphic pictures (.pdl) to sub-folders beneath the container folder.
e. In SIMATIC Manager, select Options -> Plant Hierarchy -> Customize: ensure 'Derive picture hierarchy from the plant hierarchy' is checked.
f. Execute an OS compilation (Compile -> Entire OS): verify that Picture Tree Manager builds the exact container structure.
Option B - Decoupling Picture Tree Manager for Manual Organization:
a. In SIMATIC Manager, select Options -> Plant Hierarchy -> Customize.
b. Uncheck 'Derive picture hierarchy from the plant hierarchy'.
c. Open WinCC Explorer on the OS project and open 'Picture Tree Manager'.
d. In Picture Tree Manager, insert new containers (Container -> Insert), drag pictures freely between branches, and re-order nodes using drag-and-drop.
e. Select Options -> Settings: ensure 'Recalculate group display hierarchy completely while saving' is checked.
f. Save Picture Tree Manager.
g. Note that future OS compilations will not modify the manually configured picture tree.
Refreshing Group Displays and Picture Navigation:
a. In Picture Tree Manager, select File -> Save.
b. Open WinCC Graphics Designer and run Tools -> Update Picture Hierarchy if custom group displays are utilized.

Verification

Launch WinCC Runtime on the OS station.
Observe the top screen overview area (area overview buttons):
- Confirm that buttons appear in the desired sequence.
Click a container button: confirm that the sub-menu or sub-picture selection palette expands correctly.
Perform a test delta OS compilation on the ES: confirm that the navigation structure remains completely intact without reverting.

Limitations and Operational Precautions

Decoupling Picture Tree Manager from the Plant Hierarchy (Option B) requires engineers to manually insert every newly created graphic picture into the tree; new charts and pictures will not appear in runtime navigation automatically.

Engineer FAQ

Why did OS compilation overwrite my manual changes in Picture Tree Manager?

Because the Plant Hierarchy setting 'Derive picture hierarchy from the plant hierarchy' was enabled, instructing the compiler to overwrite the WinCC tree with the Step 7 folder structure.

How do I force a specific button order in the overview bar?

Add numerical prefixes to your Plant Hierarchy folder names in SIMATIC Manager (e.g., 01_Boiler, 02_Turbine).

How do I create a navigation button that only opens a sub-menu without a picture?

In SIMATIC Manager Plant View, create a hierarchy folder and do not assign an OS picture to it. The compiler will generate it as an empty container.

Does changing folder names in Plant Hierarchy require an AS STOP?

No. Modifying Plant Hierarchy folder names affects only OS tag prefixes and picture navigation; it requires an OS compilation and delta download without AS interruption.