Creating and Relocating APL Block Icons Across Different Plant Hierarchy Pictures in PCS 7

In SIMATIC PCS 7, placing an APL block icon into an overview or supervisory graphic picture located in a different plant hierarchy folder than the underlying CFC chart can be accomplished through two manufacturer-supported methods. Method 1: In Plant View, configure the 'Lower hierarchy levels included' parameter on the destination folder's 'Create/Update block icons' dialog (e.g., setting it to 1 or 2 to automatically aggregate icons from subordinate units into the overview picture). Method 2: Manual relocation: generate the icon once, open the generated picture in WinCC Graphics Designer, change the block icon's 'type' attribute from '@MotL/1' to 'MotL/1' (removing the leading '@' symbol to decouple it from automated deletion), copy the icon into the desired picture, and uncheck 'Create block icon' on the CFC block properties to prevent duplicate generation.

Executive Summary

The SIMATIC PCS 7 Plant Hierarchy (PH) enforces strict structural alignment between the AS software organization (CFC charts) and the OS visualization screens (.pdl). By default, the automated block icon generation tool places an equipment icon (e.g., motor or valve faceplate icon) directly into the picture assigned to the specific hierarchy folder where the chart resides. However, plant operational philosophies frequently demand overview screens, central header graphics, or utility dashboards that display selected equipment icons originating from multiple disparate units. Understanding how the hierarchy level aggregation rules operate—and how to convert automated typical icons into static customized icons—allows flexible, multi-hierarchy visualization design.

Architecture and Fundamental Mechanics

The automated block icon generation subsystem in SIMATIC PCS 7 links CFC block instances to WinCC graphic screens through defined hierarchy rules:

The Automated Generation Workflow (Create/Update Block Icons):
* In CFC, each operator control block (MotL, VlvL) has an attribute Create block icon (checked by default).
* When an engineer executes Plant Hierarchy > Create/Update block icons, the compiler scans the selected plant hierarchy folder.
* It instantiates template icons from @PCS7Typicals_APL_V9.pdl into the graphic picture assigned to that folder.
The 'Lower Hierarchy Levels Included' Rule:
* In the block icon generation wizard, the setting Lower hierarchy levels included determines vertical aggregation:
- Setting = 0: The compiler only searches the immediate hierarchy folder. Only charts residing directly in that folder have icons placed in that folder's picture.
- Setting = 1: The compiler searches the current folder plus all immediate child folders one level below. Any charts in the subfolders have their icons placed into the parent picture.
- Setting = 2+: Extends the search downward through multiple hierarchy tiers.
Decoupling from Automated Compilation via Type Renaming:
* Standard generated icons carry a internal property: Type = @<BlockType>/<IconNumber> (e.g., @MotL/1).
* The leading @ symbol indicates to the OS compiler that this icon is managed automatically. During every subsequent OS compile, the compiler updates its position or deletes it if the underlying block is missing.
* By removing the @ prefix (changing Type to MotL/1), the icon transitions to a user-managed icon. The compiler will continuously update its dynamic tag connections while refraining from repositioning or deleting it, allowing it to reside permanently in any picture across the OS.

Step-by-Step Implementation Procedure

Follow these procedures to locate block icons in different hierarchy pictures:

Method 1: Using 'Lower Hierarchy Levels Included' (Automated Aggregation):
* In SIMATIC Manager, switch to Plant View (View > Plant View).
* Select the parent hierarchy folder where you want the consolidated overview picture (e.g., Area1).
* Ensure a WinCC picture is assigned to this parent folder (e.g., Area1_Overview.pdl).
* Right-click the folder and select Plant Hierarchy > Create/Update Block Icons....
* In the dialog, set Lower hierarchy levels included to 1 (or 2).
* Click OK. The compiler generates icons for all equipment residing in child folders directly onto Area1_Overview.pdl.
Method 2: Manual Relocation and Decoupling (Arbitrary Placement):
* Generate the block icon normally in its default hierarchy folder picture.
* Open the generated picture in WinCC Graphics Designer.
* Select the generated block icon (e.g., @MotL/1).
* Open Object Properties.
* Under Properties > General, locate the property type.
* Change the value from @MotL/1 to MotL/1 (delete the @ character).
* Cut (Ctrl + X) or Copy the block icon.
* Open the destination picture located in the alternate hierarchy folder (e.g., Central_Dashboard.pdl).
* Paste (Ctrl + V) the block icon and position it on the canvas.
* Save both pictures.
Prevent Duplicate Regeneration in CFC:
* Open the CFC chart where the block resides.
* Double-click the block header to open block properties.
* Uncheck the checkbox Create block icon.
* Click OK.
* This prevents future OS compilations from re-creating an unwanted copy in the origin picture.
Compile and Download OS:
* Perform an OS compile with scope 'Entire OS' or 'Changes only'.
* Verify that the relocated icon retains live tag connections and updates smoothly in runtime.

Verification

Activate WinCC Runtime. Open the destination overview picture; verify that the relocated block icon renders in its configured location. Check motor states, alarms, and setpoints; confirm that dynamic values update in real time from the AS controller. Click the block icon; confirm that the standard APL faceplate opens cleanly and commands execute correctly. Re-run Plant Hierarchy > Create/Update Block Icons; confirm that the decoupled icon is neither deleted nor duplicated.

Limitations and Operational Precautions

Relocating icons across different Operator Stations (OS Servers) is not supported. An icon can only reside in pictures belonging to the specific OS project assigned to that plant hierarchy branch. Always maintain a documented record of manually relocated icons to ensure future maintenance personnel can trace block typicals.

Engineer FAQ

What does the '@' symbol mean in block icon types?

The '@' prefix signifies an automated, system-managed object. The OS compiler uses this flag to identify icons it has permission to generate, modify, or delete.

Can I create hierarchy folders that have no pictures?

Yes. Hierarchy folders can be created purely for organizing CFC charts without assigning pictures; if a folder has no picture, no icons are generated in that folder.