Resolving Plant Hierarchy Renaming Anomalies ('Container') After OS Migration from PCS 7 v7.1 SP4 to V8.1

In SIMATIC PCS 7 project upgrades from v7.1 SP4 to V8.1, when the initial OS compilation converts configured Plant Hierarchy area names into generic 'container' labels within the WinCC Picture Tree Manager and runtime navigation bar, the issue is caused by legacy Picture Tree Manager database structures failing to synchronize with the modernized V8.1 Plant Hierarchy schema. Resolving this issue requires resetting and rebuilding the Picture Tree Manager database by enabling 'Completely Rebuild Picture Tree Upon Next OS Compile' in WinCC Explorer, verifying hierarchy delimiter settings in SIMATIC Manager, and executing a complete OS compilation ('Entire OS').

Plant Hierarchy Evolution from PCS 7 v7.1 to V8.1

In SIMATIC PCS 7, the Plant Hierarchy (PH) structures the entire project into plant areas, operational units, and technical equipment modules. In runtime, this hierarchy dictates operator navigation:
- Legacy Architecture (PCS 7 v7.1 SP4):
* Plant Hierarchy folders and their mapping to WinCC process pictures were managed through a dual-database mechanism involving the STEP 7 project database and the WinCC Picture Tree Manager (pftree.exe).
* In v7.1, folder names, hierarchy levels, and container types were stored in localized database tables (wincproj\<OS_Name>\GraCS\pftree.dat).
- Modernized Architecture (PCS 7 V8.1):
* PCS 7 V8.1 unified Plant Hierarchy management, deprecating standalone Picture Tree Manager manipulation in favor of automated hierarchy generation during OS compilation.
* Internal folder classes were introduced, distinguishing area nodes, unit containers, and generic organizational groups.

Root Cause of the 'Container' Substitution Anomaly

When an engineering project is migrated from PCS 7 v7.1 SP4 to V8.1:
1. Schema Mismatch During OS Migration:
- The OS Project Migrator updates the WinCC Microsoft SQL Server database schemas (e.g. from SQL 2005 to SQL 2008 R2).
- However, the binary hierarchy cache file (pftree.dat) retained from v7.1 contains legacy object identifiers.
2. Fallback to Default Class Name:
- When the V8.1 OS compiler parses the Plant Hierarchy folders in SIMATIC Manager and attempts to reconcile them with the existing Picture Tree database, it fails to match the legacy folder node GUIDs.
- By default, the compiler falls back to the generic C++ class type for unlinked hierarchy folders:
text container
- In Graphics Runtime, the top-level area buttons (e.g. Raw Mill, Kiln, Silo) are replaced with identical, useless buttons labeled container, container_1, container_2.

Step-by-Step Picture Tree and Plant Hierarchy Recovery Workflow

To eliminate the generic 'container' labels and restore full hierarchical plant area names:

Verify Plant Hierarchy Settings in SIMATIC Manager:
- In SIMATIC Manager, open the migrated Multiproject.
- Select the Multiproject root folder, right-click, and select Plant Hierarchy > Customize....
- Check the Hierarchy Levels: verify that the configured depth (e.g. 3 to 5 levels) matches the physical structure.
- Check the Delimiter (typically \ or /).
- Check that Derive Picture Hierarchy from Plant Hierarchy has an active checkmark.
Purge Legacy Picture Tree Data in WinCC Explorer:
- Open the OS project in WinCC Explorer.
- In the navigation tree, right-click Picture Tree Manager and select Open.
- In Picture Tree Manager, select Options > Completely Rebuild Picture Tree Upon Next OS Compile.
- Save and close Picture Tree Manager.
- Close WinCC Explorer.
Re-synchronize Plant Hierarchy and Block Icons:
- In SIMATIC Manager Plant View, select the project root.
- Select Options > Plant Hierarchy > Create/Update Block Icons.
- Ensure the correct template picture (@PCS7Typicals_V8.pdl) is selected.
- Click OK to re-link all picture windows to the hierarchy folders.
Execute Complete OS Compilation:
- In SIMATIC Manager, right-click the OS project and select Compile.
- In the wizard, select Entire OS (do NOT select Changes only).
- Check With memory reset to wipe outdated tag and area caches.
- Click Compile.
- Once compilation finishes, open Picture Tree Manager in WinCC Explorer and confirm that all area and unit folder names are restored accurately.

Plant Hierarchy and Picture Tree Migration Troubleshooting Table

The following table details symptoms and resolutions for Plant Hierarchy migration anomalies:

Observed SymptomUnderlying Failure PointDatabase ImpactApproved Corrective ActionArea buttons labeled 'container'Legacy pftree.dat cache mismatchOS compiler falls back to default class nameEnable 'Completely Rebuild Picture Tree' and compile Entire OSMissing Area Overview buttonsFolder property 'Picture' unassignedHierarchy folder omitted from navigation barAssign process picture (.pdl) to folder in Plant ViewDuplicate area buttons in runtimeMultiple hierarchy folders sharing namesWinCC appends incremental indexes (_1, _2)Ensure unique naming for all folders across the plantOS Compile error 1739:10Obsolete OCM type handles in delta indexIncremental compilation failsExecute 'Save As with Reorganization' and Entire OS compileBlock icons not generatingPicture property 'Derive tags' disabledBlock icon generator skips pictureCheck 'Picture receive tag from Hierarchy Folder'

Verification

To confirm that Plant Hierarchy names are restored and runtime navigation is functional:
1. Open WinCC Explorer on the Engineering Station and double-click Picture Tree Manager.
2. Verify that the navigation tree displays the actual plant area names (e.g. Boiler_Area, Turbine_Hall, Water_Treatment) rather than 'container'.
3. Open WinCC Graphics Designer and inspect the overview screen (@Overview1.pdl).
4. Activate WinCC Runtime:
- Verify that the upper overview navigation area displays buttons with correct plant area names.
- Click each area button: confirm that the main process working area switches immediately to the designated area overview picture.
- Confirm that alarm group displays in the header reflect alarms originating from the correct hierarchical sub-units.

Limitations and Operational Precautions

When migrating plant hierarchies across major PCS 7 versions:
1. Never Manually Edit Hierarchy Names in Picture Tree Manager: In PCS 7, the Plant Hierarchy in SIMATIC Manager is the master authority. Renaming nodes inside WinCC Picture Tree Manager directly creates immediate database discrepancies that will be wiped during the next OS compile.
2. Maximum Hierarchy Depth: PCS 7 supports a maximum of 8 hierarchy levels. Exceeding 8 levels causes compilation truncation and unresolvable tag names.
3. Delimiter Character Restrictions: Avoid using spaces, periods, or special characters (@, #, $, %) in hierarchy folder names. Standard alphanumeric characters with underscores (_) guarantee seamless SQL Server indexing.

Engineer FAQ

Why did the compiler name the folders 'container' specifically?

In the C++ object model of the PCS 7 OS compiler, 'container' is the internal base class name for an unassigned hierarchy folder node. When node metadata cannot be parsed, the compiler substitutes the class name.

Does rebuilding the Picture Tree delete my process pictures?

No. Rebuilding the Picture Tree only restructures the navigation hierarchy XML/database tables. Physical .pdl picture files in the GraCS directory are completely unaffected.

Why did 'Compile OS Changes' fail to fix the container names?

Changes compilation only transfers modified data. Because the hierarchy structure was considered 'unchanged' by the delta engine, it did not rebuild the navigation tree. An 'Entire OS' compilation is required.

Can I restore my old v7.1 Picture Tree manually?

No. PCS 7 V8.1 utilizes a modernized database schema. Rebuilding the tree directly from the SIMATIC Manager Plant Hierarchy is the only supported and stable method.