Configuring Multi-Level Overview Screens and Block Icon Inheritance in SIMATIC PCS 7

Configuring Multi-Level Overview Screens and Block Icon Inheritance in SIMATIC PCS 7

To display overview graphics containing block icons from child folders (Level 2) on a parent overview screen (Level 1) in SIMATIC PCS 7 without breaking automated icon synchronization, configure the 'Lower hierarchy levels included' parameter or manually place icons without the '@' type prefix. When copying an automatically generated block icon to a higher-level overview picture, removing the leading '@' from its 'type' property converts it into a manually placed icon (equivalent to @TemplateAPL.pdl). This prevents the OS compiler from deleting or moving the icon while still allowing the Block Icon Wizard to update its tags, interconnections, and faceplate links.

Table of Contents

Plant Hierarchy Organization and OS Area Designation

In SIMATIC PCS 7, the Plant Hierarchy (Pflanzensicht) models the physical and technological structure of the facility. In SIMATIC Manager > Options > Customize > Plant Hierarchy, the engineer configures which hierarchy level represents the OS Area (typically Level 1 or Level 2).

The selected OS Area level populates the primary area navigation buttons in the @Overview1.pdl banner during OS compilation. However, complex facilities often require an overarching Level 1 overview picture (e.g., displaying key summary valves and pumps) while detailed subordinate equipment resides in Level 2 sub-folders.

Automatic Block Icon Generation and 'Lower Hierarchy Levels Included'

When executing Plant Hierarchy > Create/Update Block Icons (or compiling the OS):

  • The compiler scans CFC charts within hierarchy folders and generates graphical block icons in the folder's process picture.
  • The parameter 'Lower hierarchy levels included' (Untere Hierarchiestufen eingeschlossen) controls search depth:
  • Value 0: Block icons are generated strictly in the picture residing in the identical hierarchy folder where the CFC is located.
  • Value 1: The wizard searches one level below the current folder, generating block icons for both local and immediate child CFCs.
  • Value 2+: Searches deeper child hierarchy levels.

Significance of the '@' Prefix in Block Icon Type Property

Every block icon in PCS 7 possesses a user-defined property named type (e.g. @MotL/1 or MotL/1):

  1. Icons with Leading @ (e.g. @MotL/1): Informs the Block Icon Wizard that the icon was automatically generated. During each OS compilation, the wizard recalculates icon coordinates, repositions icons, and deletes any icon whose underlying CFC block no longer matches the hierarchy folder rules.
  2. Icons without Leading @ (e.g. MotL/1): Designates a manually placed block icon (identical to dragging an icon from @TemplateAPL.pdl). The wizard will NEVER delete or reposition this icon during OS compilation, but WILL successfully update its tag interconnections, alarm flags, and faceplate call scripts.

Siemens Best Practice for Multi-Level Overview Displays

To construct clean, maintainable overview screens across hierarchy levels:

  1. Set OS Area to Level 1 in Plant Hierarchy properties.
  2. Keep Lower hierarchy levels included = 0 so that full detailed icons are generated automatically inside Level 2 pictures.
  3. In the Level 1 overview picture, copy the critical summary block icons from Level 2 pictures.
  4. In the Level 1 picture, open the Object Properties of each copied icon, locate property type, and delete the leading @ (e.g., change @MotL/1 to MotL/1, or @VlvL/2 to VlvL/2).
  5. Uncheck the option Derive the block icons from the plant hierarchy in the Level 1 picture properties if purely manual layout control is desired.

Comparison of Block Icon Management Strategies

The table below contrasts automatic versus manual block icon deployment:

Icon StrategyProperty 'type' ValueAutomatic PositioningDeleted upon Missing CFCWizard Updates TagsBest Suited ContextFully Automatic Generation@<BlockType>/<Variant>Yes (Grid layout)Yes (Purged on compile)Yes (Fully automated)Standard Level 2/3 unit graphicsManually Placed Icon<BlockType>/<Variant>No (Fixed coordinate)No (Preserved on compile)Yes (Updated via Wizard)Level 1 plant overview screensStatic Custom SymbolCustom string / NoneNoNoNo (Requires manual script)Simple status indicators

Verification

Verify block icon behavior across hierarchy levels:

  1. Copy an icon from a Level 2 picture to the Level 1 overview picture; remove the leading @ from property type.
  2. Position the icon at a specific X/Y coordinate on the Level 1 picture canvas.
  3. Execute a full OS Compilation (Entire OS) from SIMATIC Manager.
  4. Confirm that the icon remains at its exact X/Y coordinate on the Level 1 picture and was not deleted or rearranged.
  5. Open WinCC OS Runtime; click the icon on the Level 1 picture and confirm it opens the correct Level 2 equipment faceplate.

Limitations and Operational Precautions

Review the following engineering precautions regarding block icons:

  • Unique Tag Name Binding: Ensure the copied icon's tagname property matches the full AS chart path (e.g. Area/SubArea/Motor101).
  • Overcrowding Overview Screens: Placing hundreds of manually placed icons on a single overview picture degrades screen load times; limit overview screens to high-level summary indicators.
  • Wizard Re-run: Always run Plant Hierarchy > Create/Update Block Icons after renaming CFC charts to ensure manually placed icons reconnect to new tag paths.

Engineer FAQ

Does removing the '@' from the block icon type break faceplate opening?

No. The '@' symbol is solely an instruction flag for the automated Block Icon Wizard. Removing '@' does not affect faceplate opening, alarm signaling, or runtime status scripts.

What happens to an icon with an '@' prefix during OS compile if its CFC is in a different folder?

If the icon has an '@' prefix and the folder setting 'Lower hierarchy levels included' does not reach that CFC, the Block Icon Wizard assumes the icon is orphaned and automatically deletes it from the picture.

Can manually placed icons without '@' be updated automatically when block interfaces change?

Yes. Running 'Create/Update Block Icons' updates the tag interconnections and structure types of manually placed icons without altering their screen coordinates.

Technical References

Related Articles

Related Tags

  • Plant Hierarchy
  • Block Icons
  • Create/Update Block Icons
  • OS Area
  • Type Property
  • Overview Screen
6 respuestas