Duplicating Block Icons Across Multiple WinCC Process Pictures: Managing Alarms and Group Displays

When duplicating a block icon across multiple WinCC pictures, both icons monitor the identical AS instance; locking alarms from either faceplate disables alarms globally in the controller. To prevent the copied block icon from causing duplicate alarm flashing on higher-level area buttons in the overview bar, open the icon's Object Properties, navigate to the 'System' group, and set the 'Relevant' (Group Display Relevant) property to 'No'.

Operational Use Case for Multi-Picture Block Icons

In complex process plants running SIMATIC PCS 7 OS (WinCC), operators frequently need to monitor critical equipment from multiple graphic perspectives:
* Detailed Equipment Overview: A feed pump (PMP_101) is primarily visualized inside the detailed unit picture RTM1 (Feed Preparation).
* Summary Process Overview: The same pump must also be visible on an overview screen RTM2 (Plant Utility Overview) alongside transfer valves and storage tanks.

Engineers implement this by copying the block icon of PMP_101 from picture RTM1.pdl and pasting it into picture RTM2.pdl.

However, duplicating block icons introduces two major operational challenges:
1. Alarm Interaction and Faceplate Locking: When an alarm occurs, both icons flash simultaneously. If an operator clicks the padlock icon on the faceplate in RTM2 to lock alarms, how does this affect RTM1?
2. False Group Display Flashing on Area Buttons: When PMP_101 trips, the area overview bar at the top of the monitor displays flashing red alarm indicators for both Area 1 and Area 2, even though the physical pump belongs exclusively to Area 1. This false alarm indication confuses control room personnel.

Block Icon vs Controller Instance Architecture

To understand why alarms behave identically across both screens, examine the relationship between graphics and automation code:

Passive Visualization of AS Blocks:
* Block icons in WinCC do not generate alarms or calculate process states. They are graphical proxies pointing to tag instances inside the AS controller (e.g., PMP_101.EventState, PMP_101.Status1).
* When the AS block triggers an alarm, it updates the central message archive. Because both block icons read the same controller instance, the yellow/red flashing alarm banner (A) illuminates on both block icons.
Global Effect of the Faceplate Lock (Padlock):
* When an operator opens the faceplate from either icon and clicks the Lock Messages button (padlock), the faceplate does not change a local graphic setting.
* It sends a control command to the AS block input MsgLock = 1.
* Consequently, message generation is disabled at the controller source, suppressing alarms across all WinCC clients, redundant servers, and both process pictures.

Group Display Hierarchy and the 'Relevant' Property

The critical mechanism governing area overview button flashing is the Group Display (Sammelanzeige):

Group Display Roll-Up:
Every standard PCS 7 block icon embeds a WinCC Group Display object (@GroupDisplay).
The group display scans the picture, aggregates active alarms, and passes the highest priority alarm state upward through the Plant Hierarchy to the Area button in the WinCC overview area bar.
The 'Relevant' (Group Display Relevant) Property:
In the object properties of every block icon, under property group System, exists an attribute named Relevant (or Group Display Relevant / Sammelrelevanz).
By default, Relevant = Yes (TRUE). This instructs the picture hierarchy engine to include this block icon in the area's aggregated alarm status.
If the icon is copied into a secondary picture belonging to another area (RTM2), Relevant = Yes causes Area 2 to report a phantom alarm!
Solution: Setting Relevant = No (FALSE) on the copied icon in RTM2 decouples it from Area 2's group display hierarchy. The icon will still show live process values, display flashing alarm letters locally, and open faceplates, but it will not trigger alarm indicators on Area 2's top-level button.

Step-by-Step Duplication and Configuration Procedure

1. Copy the Block Icon to the Secondary Picture

In WinCC Explorer, open Graphics Designer.
Open primary picture RTM1.pdl (where the icon was auto-generated by OS compilation).
Select the block icon (e.g. pump icon), press Ctrl + C.
Open secondary picture RTM2.pdl, press Ctrl + V, and position the icon as desired.

2. Configure the 'Relevant' Property to Prevent Phantom Area Alarms

In RTM2.pdl, right-click the pasted block icon and select Properties.
In the Object Properties window, select the System property group in the left pane.
In the right pane, locate the attribute Relevant (or Group Display Relevant).
Double-click the static value column and change it from Yes to No.
Save RTM2.pdl.

3. Verify Tag Interconnection Binding

In the Object Properties window, inspect property group General > attribute Tag.
Confirm the tag name points to the identical AS instance (e.g. Plant_1/SubArea_A/PMP_101).
Ensure no local script overwrites the tag binding upon picture opening.

Block Icon Configuration and Group Display Property Matrix

Property SettingLocal Block Icon DisplayFaceplate OperationPropagates to Area Button?Recommended ApplicationRelevant = Yes (Default)Live values + AlarmsFull control & faceplate jumpYES (Triggers Area Alarm)Primary auto-generated icon in home plant areaRelevant = NoLive values + AlarmsFull control & faceplate jumpNO (Suppressed from Area)Manually copied auxiliary icon in secondary pictureMsgLock = 1 (Locked)Live values only (Lock icon shown)Alarms disabled in CPUNO (No alarms generated)Equipment under maintenance / testing

Verification

In WinCC Graphics Designer, confirm Relevant = No on the copied icon in RTM2.pdl.
Activate WinCC Runtime.
Open RTM2.pdl; verify the copied icon displays valid running states (green/grey).
Simulate an alarm on the pump (e.g. overload trip).
Verify the block icon in RTM1 and RTM2 both flash with red alarm letter A.
Inspect the top overview area bar: verify the Area 1 button flashes red, but the Area 2 button remains dark/normal.

Limitations and Operational Precautions

OS Compile Overwrite Risk: Automatic OS compilation will not delete manually placed block icons in user pictures, but running 'Create/update block icons' with aggressive cleanup options may detach custom properties. Always verify manually placed icons after full OS compilation.
Avoid Renaming Block Icon Structure: Do not ungroup or rename internal child elements of the block icon; doing so breaks the internal dynamic C-scripts that open faceplates.
Faceplate Control Conflict: If two operators on different client stations open the faceplate for the same motor simultaneously, standard PCS 7 operator authorization limits control to the operator possessing active controlling privileges.

Engineer FAQ

Will clicking 'Acknowledge' on the copied icon acknowledge the alarm everywhere?

Yes. Acknowledging the alarm from either faceplate or picture sends an acknowledge telegram to the WinCC alarm server, silencing the alarm across all operator stations.

Why did the icon disappear after running OS compilation?

If you manually placed the icon in a picture where 'Derive block icons from plant hierarchy' is enabled and the icon type mismatches the hierarchy tree, OS compile may clean up unmapped objects. Ensure manual icons are positioned on user-defined overview screens.

Can I hide the flashing alarm letter on the copied icon while keeping it on the primary icon?

To hide local alarm indication entirely on the copied icon, disconnect the @GroupDisplay sub-element inside the icon or set its visibility to No.

Technical References

Related Tags

Block Icons
Group Display
Relevant
WinCC Graphics Designer
PCS 7 OS
Alarm Management

Block Icons

Group Display

Relevant

WinCC Graphics Designer

PCS 7 OS

Alarm Management

6 respuestas

Duplicating Block Icons Across Multiple WinCC Process Pictures: Managing Alarms and Group Displays