How to Fix Incorrect Entry Point Pictures During Loop-in-Alarm Navigation in WinCC

When the same block icon is placed manually on multiple pictures in SIMATIC PCS 7 WinCC, the 'Loop in Alarm' (Point function) navigates to the secondary manual screen instead of the primary process picture because the alarm system resolves entry points based on picture tree registration. To ensure navigation always targets the primary hierarchy picture, open the secondary manual block icon properties in Graphics Designer and set the attribute 'Relevant' (or 'Group Relevant') to 'No'. Alternatively, update the 'Entry point picture' attribute directly within the WinCC Component List Editor.

Architecture of Loop-in-Alarm and Entry Point Resolution

In SIMATIC PCS 7 Operator Stations (OS), the Loop in Alarm feature (invoked via the "Point to picture" button in the WinCC Alarm Control) provides rapid operator navigation:
* When an alarm is selected in the alarm banner, clicking Loop in Alarm instantly loads the exact process picture containing the faulted equipment and centers the viewport on the faulted block icon.
* This navigation path is governed by the Entry Point Picture registered in the WinCC Alarm Logging database and the Component List Editor.
* During standard OS compilation, the system creates a 1:1 binding between the technological hierarchy folder of the CFC chart and the automatically generated block icon on that area's primary .pdl picture.

Why Duplicate Block Icons Hijack Alarm Navigation

In large industrial facilities, operators frequently request the same equipment status icon (e.g., a critical feed pump 123PT1234/MonAnL) to appear on multiple screens:
* Picture A: The primary unit overview screen matching the CFC hierarchy (where the icon is generated automatically with @ prefix in the Type field).
* Picture B: A summary overview or utility screen (where the engineer manually pastes a duplicate block icon with the @ removed from the Type field to prevent deletion during OS compiles).

When a duplicate icon is inserted:
1. Picture Tree Association Conflict: By default, copied block icons inherit the property Relevant = Yes (or Group Relevant = Yes).
2. Alarm Routing Disruption: The WinCC Alarm Logging system detects two valid targets for the same tag. Depending on alphabetical PDL sorting or internal database insertion order, the alarm engine binds the "Entry point picture" to Picture B.
3. Erratic Operator Experience: When an alarm trips, clicking Loop in Alarm jumps to Picture B (the secondary summary screen) rather than Picture A (the dedicated operational graphic containing local interlocks and manual controls).

Corrective Methods to Enforce Primary Picture Routing

To restore deterministic navigation targeting the primary operational picture, choose one of the following methods:

Method 1: Set 'Relevant = No' on Secondary Block Icons (Recommended)

Open the secondary picture (Picture B) in WinCC Graphics Designer.
Select the manually inserted block icon.
In the Properties window, expand Configurations (or Object Properties).
Locate the attribute Relevant (or Group Relevant).
Change the setting from Yes to No.
Save the picture. This tells the alarm tree and Loop-in-Alarm engine to completely ignore this duplicate icon for alarm navigation, while preserving its real-time process value display.

Method 2: Manually Reassign in Component List Editor

In WinCC Explorer, open the Component List Editor.
Locate the technological tag in the component list.
In the column Entry point picture, select the primary PDL corresponding to the CFC hierarchy folder from the drop-down menu.
Save the component list. (Note: Modifying components manually takes precedence, but requires tracking to prevent accidental overwrites during full OS compilations).

Verification

In WinCC Runtime, open the alarm view or trip an alarm on the affected measurement tag.
Highlight the alarm line in the WinCC AlarmControl.
Click the Loop in Alarm button in the alarm toolbar.
Verify that:
WinCC immediately opens Picture A (the primary unit picture).
The primary block icon is highlighted with the red selection frame.
Navigating to Picture B confirms that the secondary icon displays live values without interfering with alarm links.

Limitations and Operational Precautions

Setting Relevant = No on a secondary block icon means that alarms for that specific tag will not contribute to the hierarchical group display (alarm tally) of Picture B's navigation button in the overview area.
Never remove the @ prefix from block icons on the primary picture; the @ prefix is required for the OS compiler to manage automatic updates.
If duplicate icons are deployed extensively across multiple screens, consider using Control Module Types (CMT) or custom display-only symbols to minimize manual property maintenance.

Engineer FAQ

Can a block icon display live values without generating alarms?
Yes. Setting Relevant = No disconnects the icon from the alarm system and group display hierarchy while maintaining full dynamic tag linking for process measurements and status colors.
Why does the Component List Editor lose object names when edited?
If a tag's block icon is manually renamed or altered outside standard APL naming conventions, the Component List Editor resets internal cross-references to default descriptors.
Can I export the Component List Editor to Excel to fix entry points in bulk?
Yes. In WinCC Explorer, you can export the component list to CSV, adjust the entry point picture columns in bulk, and re-import it into WinCC.

Technical References

SIMATIC PCS 7 OS Process Control System; Graphic Objects and Faceplates Manual.
SIMATIC WinCC V7/V8 Alarm Logging and Screen Navigation Manual.
Siemens Industry Online Support Entry ID 109801081: Configuring Loop-in-Alarm and Block Icons in PCS 7.