Managing and Bulk-Deleting Plant Hierarchy Folders Across Multiprojects in PCS 7 Process Object View

In SIMATIC PCS 7, deleting an unwanted plant hierarchy folder that exists across multiple projects (such as 24 projects within a large multiproject) can be executed efficiently in a single bulk operation using the Process Object View (POV). In SIMATIC Manager, select the root Multiproject node, open 'View > Process Object View', navigate to the 'Hierarchy' tab, filter or sort by the folder name, select the unwanted folder rows across all projects, and press Delete. The engineering system verifies folder dependencies and removes the hierarchy folders across all sub-projects simultaneously.

Executive Summary

Large industrial automation plants engineered with SIMATIC PCS 7 frequently divide the automation architecture into extensive multiprojects containing dozens of individual S7 projects and OS stations (e.g., 24 distinct projects representing different plant areas, skids, and utilities). When standardizing plant models, an engineer may inadvertently execute a template propagation or batch script that creates an obsolete or duplicated Plant Hierarchy folder across every project in the multiproject.

Navigating through 24 separate project trees in SIMATIC Manager to locate and delete each folder individually is tedious, error-prone, and time-consuming. Fortunately, SIMATIC PCS 7 provides a centralized engineering workspace: the Process Object View (POV). This article details how the Process Object View aggregates hierarchy metadata across multiprojects and outlines the exact step-by-step procedure to perform cross-project bulk hierarchy deletions safely.

Architecture and Fundamental Mechanics

The plant modeling architecture in SIMATIC PCS 7 is governed by the Plant Hierarchy (PH):

Role of the Plant Hierarchy: The Plant Hierarchy structures engineering data according to ISA-88 / ISA-106 physical models (Enterprise > Site > Area > Unit > Equipment Module). Hierarchy folders organize CFC charts, SFCs, WinCC process pictures (.pdl), and reports. The hierarchy path also defines the plant designation string (e.g., Plant/Area1/Unit2) assigned to WinCC block icons and alarms.
The Multiproject Database Structure: In SIMATIC Manager, a Multiproject is a distributed database that indexes multiple independent Step 7 project directories (*.s7p). While the Component View displays projects in isolated file silos, the Plant View and Process Object View provide a unified, transparent abstraction across the entire multiproject.
Process Object View (POV) Hierarchy Management: The Process Object View features a dedicated 'Hierarchy' tab. When the top-level Multiproject node is selected, the POV scans all 24 sub-projects and compiles a unified tabular ledger of every configured hierarchy folder. Each record displays: Project Name, Folder Name, Hierarchy Level, Linked Picture, Linked Report, and CFC Chart Count. This tabular structure supports multi-row selection, sorting, filtering, and bulk deletion commands that execute across project boundaries.

Step-by-Step Implementation Procedure

Follow these steps to bulk-delete unwanted plant hierarchy folders across a multiproject using Process Object View:

Create a Full Multiproject Archive:
- In SIMATIC Manager, select 'File > Archive...'.
- Save a full compressed backup of the entire multiproject to external storage before deleting hierarchy elements.
Open Process Object View at the Multiproject Level:
- In SIMATIC Manager, ensure the left navigation pane highlights the top-level Multiproject root node (not an individual S7 project).
- In the main menu, select 'View > Process Object View' (or click the Process Object View icon on the toolbar).
Switch to the Hierarchy Tab:
- In the right-hand Process Object View pane, locate the tab strip at the top.
- Click the 'Hierarchy' tab.
- The view populates with a consolidated table showing every hierarchy folder across all 24 projects.
Filter and Identify the Target Folders:
- In the 'Name' or 'Hierarchy Folder' column, click the column header to sort alphabetically, or use the filter function to isolate the unwanted folder name (e.g., Obsolete_Skid_01).
- Inspect the 'Charts' and 'Pictures' columns for these rows: confirm that the count is 0 (indicating the folders contain no active charts, SFCs, or WinCC pictures).
- If any folder contains active charts, move those charts to valid hierarchy folders before proceeding.
Execute Bulk Deletion Across All Projects:
- Click to select the first unwanted folder row.
- Hold Ctrl and click each matching folder row across the 24 projects (or hold Shift to select a contiguous block of matching rows).
- Press the Delete key on your keyboard (or right-click the selection and choose 'Delete').
- A confirmation dialog appears: 'Do you really want to delete the selected hierarchy folders?'
- Confirm by clicking 'Yes'.
- The Process Object View iterates through all project databases and cleanly removes the hierarchy folders in a single automated sweep.
Verify Plant View Synchronization:
- Switch back to 'View > Plant View'.
- Expand the projects in the tree: confirm that the unwanted hierarchy folders have vanished across all 24 project structures.

Verification

In SIMATIC Manager Plant View, expand multiple sub-projects: confirm that the deleted folder does not appear in any hierarchy path.
In Process Object View, refresh the 'Hierarchy' tab: verify that a search for the deleted folder name returns zero rows.
Open an S7 project within the multiproject, open a CFC chart, and perform a test compile ('Changes only'): confirm that compilation completes cleanly without broken hierarchy reference warnings.
Execute an OS compile ('Changes only'): verify that WinCC Picture Tree Manager updates without reporting missing hierarchy nodes.

Limitations and Operational Precautions

Deleting a hierarchy folder that contains active CFC charts, SFCs, or WinCC pictures will prompt a warning; if confirmed, all enclosed charts and graphics will be permanently deleted! Always verify that the 'Charts' and 'Pictures' columns show zero enclosed objects before executing bulk deletion. Multiproject operations require all sub-project files to be reachable across local or network paths. Validate all software engineering tools through an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

Can I delete hierarchy folders across projects without Process Object View?

Without Process Object View, you would have to manually open each of the 24 projects in SIMATIC Manager Plant View, locate the folder, and delete it 24 separate times.

What happens if a deleted hierarchy folder had an OS picture assigned to it?

Deleting the folder removes the picture assignment from the WinCC Picture Tree. If the .pdl file exists on disk, the file remains in GraCS but is unlinked from the navigation hierarchy.

Why is Process Object View empty when I open it?

Ensure that the root Multiproject node is selected in the left pane and that the filter criteria in POV are set to show all objects without restrictive search masks.

Does deleting a hierarchy folder change controller executable memory?

Deleting an empty hierarchy folder modifies only the Step 7 engineering database and plant view metadata; it does not alter controller code in AS work memory.