C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Configuring Picture-Specific Hierarchy Scopes for Block Icon Generation in SIMATIC PCS 7

Configuring Picture-Specific Hierarchy Scopes for Block Icon Generation in SIMATIC PCS 7

In SIMATIC PCS 7, the option 'Lower hierarchy levels included' is a global multiproject setting in Plant Hierarchy properties that cannot be toggled on a per-folder basis. However, picture-specific block icon generation scope is achieved architecturally: the block icon compiler automatically stops traversing deeper into subordinate hierarchy levels as soon as it encounters a lower folder that has its own graphic picture assigned. Therefore, to prevent a parent picture from absorbing icons from 1 to 2 levels lower, assign dedicated graphic pictures (or lightweight sub-pictures) to those lower hierarchy folders, or disable 'Derive block icons from the plant hierarchy' in the properties of the specific picture.

Table of Contents

Executive Summary

Designing structured, scalable Human-Machine Interface (HMI) screen navigation in SIMATIC PCS 7 relies on the Plant Hierarchy (PH). When compiling the OS, the Create/Update Block Icons wizard automatically places and animates block icons inside WinCC graphic pictures based on where CFC charts reside in the hierarchy. A common engineering conflict occurs when some process pictures require icons gathered from 1 or 2 subordinate hierarchy levels below (e.g. an equipment overview that combines pumps and valves from sub-units), while other pictures must strictly generate icons only from their immediate folder. When engineers discover the global setting 'Lower hierarchy levels included' under Plant Hierarchy Settings, they find it applies uniformly across the entire multiproject. This technical guide explains the underlying traversal algorithm and provides proven architectural patterns to enforce folder-specific icon derivation.

Plant Hierarchy Traversal Rules for Block Icon Generation

When the block icon generation wizard runs, it evaluates each graphic picture (.pdl) according to strict hierarchy rules:

  1. If a picture has Derive block icons from the plant hierarchy checked, the compiler searches for CFC charts in that picture's immediate hierarchy folder.
  2. If Lower hierarchy levels included is enabled globally, the compiler continues searching downward into child subfolders.
  3. The Picture Boundary Rule: The compiler stops traversing a subordinate hierarchy branch the moment it encounters a child folder that contains its own assigned graphic picture. The child picture absorbs all subsequent lower-level icons, shielding the parent picture from further clutter.

The Global 'Lower Hierarchy Levels Included' Constraint

Under Options > Plant Hierarchy > Settings, the parameter Lower hierarchy levels included specifies the maximum depth (e.g. 1, 2, or all levels) that the compiler will traverse downward. Because this dialog sets an environment variable for the entire multiproject database, it cannot be modified dynamically per folder.

Architectural Solutions: Folder Picture Boundaries and Scope Limiting

Engineers can achieve precise folder-level control through two standard methods:

  • Method A: Inserting Picture Boundaries: By placing a graphic picture in a subfolder, that subfolder becomes a 'firewall' that prevents child CFC block icons from rolling up into the grandparent picture.
  • Method B: Selectively Disabling Derivation: Unchecking 'Derive block icons' on individual picture properties prevents automated generation entirely for that picture, allowing manual icon placement.

Block Icon Hierarchy Scope Configuration Matrix

The following table compares configuration patterns for controlling block icon generation scope:

Engineering ObjectivePicture PropertyLower Subfolder StatusResulting Icon Generation ScopeCurrent Folder OnlyDerive Icons = EnabledChild folders have own picturesStrictly icons from current folder; stops at child boundary.Multi-Level Rollup (1-2 Levels)Derive Icons = EnabledChild folders have NO picturesTraverses downward, generating child icons in parent picture.Zero Automatic Icons (Overview)Derive Icons = DisabledAny stateCompiler completely ignores picture; 0 icons generated.Block Icon Hidden GloballyBlock attribute S7_m_c = trueBlock Icon Type = "" (Empty)Block is accessible in WinCC, but no icon is created anywhere.Cross-Area AggregationDerive Icons = DisabledManual Copy (Strip @)Manually placed icons persist across all compilations.

Step-by-Step Implementation Procedure

Method 1: Establishing Picture Boundaries in Lower Folders

  1. In SIMATIC Manager, navigate to the Plant View.
  2. Locate the parent hierarchy folder where icons from lower levels should NOT appear.
  3. Inspect the child subfolders nested beneath it.
  4. For each child subfolder that contains CFC charts, right-click the folder and choose Insert > New Object > Picture.
  5. Assign a meaningful name (e.g. Unit_Detail.pdl).
  6. Open the parent picture's properties and ensure Derive block icons from the plant hierarchy is enabled.
  7. Execute Options > Plant Hierarchy > Create/Update Block Icons.
  8. Confirm that the parent picture now contains only its own folder's icons, while child icons are placed into Unit_Detail.pdl.

Method 2: Disabling Block Icon Creation for Specific Blocks

  1. If specific technological blocks in lower charts should never generate block icons, open the CFC chart.
  2. Double-click the block (e.g. MonAnL) to open Block Properties.
  3. Under Create block icon, uncheck the option or clear the block icon type number.
  4. Compile OS changes; the block is excluded from all picture generations.

Verification

To verify that block icons generate strictly within intended picture boundaries:

  1. Compilation Log Review: Execute Create/Update Block Icons. Inspect the compilation log; verify that parent pictures list only local block tags.
  2. Graphic Designer Inspection: Open the parent overview picture in Graphic Designer. Confirm that no unexpected subgroup icons populate the screen.
  3. Sub-Picture Verification: Open the child detail picture. Confirm that its local technological block icons are present and correctly positioned.

Limitations and Operational Precautions

  • Picture Deletion Hazard: Deleting a child picture removes the boundary; upon the next execution of Create/Update Block Icons, all child icons will immediately roll up into the parent picture.
  • Hierarchy Level Depth: Maintain consistent hierarchy depth definitions across all multiproject folders to avoid confusing plant navigation paths.
  • Empty Sub-Pictures: If a subfolder picture is created purely as a boundary, it can be hidden from operator picture navigation by not assigning it to the Area Overview menu.

Engineer FAQ

Can 'Lower hierarchy levels included' be parameterized per picture?

No. The setting in Plant Hierarchy Settings is a global multiproject parameter that applies to all pictures where derivation is active.

What happens if two pictures exist in the same hierarchy folder?

The block icon generation wizard will prompt the engineer to select which of the two pictures should serve as the target for automated icon creation.

How do I prevent a single block from creating an icon without deleting its WinCC messages?

In the CFC block properties, uncheck 'Create block icon'. The block maintains S7_m_c communication for alarms and faceplates, but skips icon generation.

Technical References

Related Articles

Related Tags

  • https://industrialautomation.net/search?query=simatic-pcs7
  • https://industrialautomation.net/search?query=plant-hierarchy
  • https://industrialautomation.net/search?query=block-icons
  • https://industrialautomation.net/search?query=os-compilation
6 respuestas