Configuring and Synchronizing the Picture Tree on WinCC OS Clients in SIMATIC PCS 7

In SIMATIC PCS 7, custom modifications made to the Picture Tree or area buttons on an Engineering Station (ES) fail to transfer or get overwritten on OS Clients because the Plant Hierarchy automatically regenerates the server Picture Tree during OS compilation, and OS Clients derive their navigation structure strictly from the loaded OS Server Data package (.pdk). To preserve custom button layouts, uncheck 'Picture Tree' when compiling the OS, regenerate server data on the OS Server, download server data to the clients, and run the OS Project Editor on the client stations to rebuild runtime navigation paths.

Plant Hierarchy (PH) vs Picture Tree Manager: Synchronization Lifecycle

In SIMATIC PCS 7, operator station navigation is governed by the Picture Tree Manager. In standard workflows, the Picture Tree is completely derived from the Plant Hierarchy (PH) configured in SIMATIC Manager. Each hierarchy folder designated with the property 'Area' generates an area overview button in the WinCC runtime overview area (@overview1.pdl), and subordinate pictures appear in the picture tree drop-down menus.

However, complex facilities frequently require custom-designed area buttons, custom picture groupings, or multi-project views where the raw Plant Hierarchy structure does not match operational control room ergonomics.

Why OS Compilation Overwrites Manual Picture Tree Adjustments

When an engineer manually rearranges containers or renames nodes inside WinCC Picture Tree Manager on the ES, those changes are stored in local project configuration files (*.ptd).

If the engineer subsequently performs an OS Compilation with the default option 'Picture Tree' checked in the compilation wizard, the AS-OS compiler parses the Plant Hierarchy and completely overwrites the manual changes.
To protect custom picture trees, engineers must uncheck 'Picture Tree' in the OS Compilation dialog once the initial hierarchy is established.

How OS Clients Derive Picture Tree Navigation from Server Data (.pdk)

In distributed PCS 7 systems, OS Clients do not possess independent plant hierarchies; they are multi-clients that display pictures belonging to one or more OS Servers:

When the OS Server project is compiled, generating Server Data creates the <ServerName>.pdk package file.
This package file encodes the server's active Picture Tree structure, picture names, and tag prefixes.
When the OS Client loads this package, the client's Picture Tree Manager incorporates the server's picture hierarchy.
If multiple server packages are loaded (e.g. across multiprojects), the client merges these nodes into its overall picture tree.

The Role of the OS Project Editor in Client Navigation Layouts

On the OS Client station:

Loading server data updates the available picture catalog, but the visual arrangement of screen containers and monitor layouts is controlled by the OS Project Editor.
Running the OS Project Editor on the client initializes the runtime screen resolution (e.g. 1920x1080), assigns overview areas, and rebuilds internal navigation scripts (@screen.pdl). Without running OS Project Editor, clients often exhibit blank or misaligned area buttons.

Comparative Picture Tree Configuration Matrix: ES vs OS Server vs OS Client

The following table compares picture tree roles and update rules across station types:

Station RolePicture Tree SourceCompilation Overwrite RuleNavigation Update MechanismEngineering Station (ES)STEP 7 Plant HierarchyOverwritten if 'Picture Tree' checked during OS CompileFull OS Compile & Local OS Project EditorOS ServerInherited from ES via DownloadReplaced during full OS DownloadServer Data Generation (<OS>.pdk)OS ClientImported from OS Server PackagesClient Picture Tree can rearrange imported packagesOS Project Editor + Server Data ReloadMultiClient (Cross-Project)Merged from multiple .pdk filesRetains independent client-side container orderOS Project Editor execution

Step-by-Step Procedure to Deploy Custom Picture Tree Layouts to Clients

Follow this sequence to ensure custom picture tree changes propagate cleanly to all OS Clients:

Configure Custom Hierarchy in ES: Open Picture Tree Manager in WinCC Explorer. Organize containers and assign customized picture nodes.
Protect Picture Tree During OS Compile: When compiling the OS Server in SIMATIC Manager, uncheck the checkbox 'Picture Tree' in the compilation wizard.
Generate Server Data: In WinCC Explorer on the OS Server, right-click Server Data and select Create.
Download OS Server: Perform an OS Download to target OS Server stations.
Update OS Client Project: In SIMATIC Manager, right-click the OS Client object -> Assign OS Server. Verify the updated server package is selected.
Run OS Project Editor on Client: Open the OS Client project in WinCC Explorer. Open OS Project Editor, verify screen resolution, and click OK to rebuild client scripts.
Download OS Client: Download the client project to the target physical client PC and start runtime.

Verification

Verify client navigation integrity through these checks:

Overview Area Button Inspection: In WinCC Runtime on the OS Client, verify that all custom Area buttons appear on the top overview banner.
Picture Tree Dropdown Navigation: Click an area button; verify that the drop-down menu lists the correct subordinate process pictures.
Picture Opening Test: Click each menu item; confirm the corresponding plant mimic opens with live data and without script errors.
Multi-Language Verification: If translated area names are configured (e.g. Russian/English), toggle language in runtime and verify buttons translate properly.

Limitations and Operational Precautions

Observe the following engineering constraints:

Unchecked Compile Hazards: If 'Picture Tree' is left unchecked permanently, any newly added CFC charts or plant folders in SIMATIC Manager will not appear in WinCC automatically; you must manually add new pictures into Picture Tree Manager.
Maximum Hierarchy Depth: WinCC Picture Tree Manager supports a maximum hierarchy depth of 4 levels. Do not nest containers deeper than 4 tiers.
Commercial Accuracy Disclaimer: Software order numbers (MLFBs), package structures, and hardware capacity prerequisites vary across PCS 7 versions and hardware platforms. System integrators must confirm exact software entitlements and licensing requirements against the official Siemens Catalog CA 01 and obtain an authorized Siemens distributor quotation prior to purchasing.

Engineer FAQ

Can I translate Area button names into Russian or other languages?

Yes, by exporting the WinCC Text Library, translating the Area string keys in the Text Distributor, and re-importing them into the project.

What happens if an OS Client loads packages from two different multiprojects?

The client merges the Picture Trees of both server packages; the engineer can use the client's Picture Tree Manager to arrange the visual display order.