Show DB-Derived PCS 7 Alarms in the WinCC Group Display

To show alarms based on DB values in a PCS 7 group display, make sure they are generated and configured as PCS 7 process messages and included in the OS group-display hierarchy. The APL Event block is one supported way to generate messages from digital alarm conditions; analog values first need an engineered Boolean condition. Compile the relevant AS and OS configuration, update the hierarchy, and verify the alarm path under a controlled test condition. Exact block and OS steps depend on the installed PCS 7/APL release.

Why ordinary DB alarms may not appear in the group display

A WinCC alarm associated with a DB value and a PCS 7 group-display state are related but distinct configuration items. PCS 7 group displays summarize message state through the configured group-display hierarchy and message-state information such as the measuring point's EventState. A raw DB tag alarm does not, by itself, establish the PCS 7 process-message and hierarchy links required for the top-level area display.

Siemens' APL Event block is intended to generate acknowledgeable process messages from changing digital signals. The ticket's reply proposes using that block for the DB-derived signals. This is a supported direction when the installed APL and PCS 7 release support the block and its messages are compiled and included in the OS hierarchy.

Configure DB-derived events through the AS

Confirm whether the existing DB alarm is an AS-generated PCS 7 message or only a WinCC tag alarm. Record the trigger signal, active state, expected message class and target process area.
In a CFC chart assigned to the intended plant area, use the Event message block from the APL release installed in the project, if supported. Siemens' APL V71 manual places Event in the Report family and describes up to eight monitored digital inputs, with a separate message text for each input.
Interconnect each suitable Boolean alarm condition to an Event input. For an analog DB value, create and review the threshold/condition logic in the AS first; the Event input is digital. Do not substitute a guessed threshold or inversion. Verify which signal polarity means alarm active.
Configure the message texts and any required associated values using the exact APL and PCS 7 version manuals. Event messages are generated on signal edges; check alarm activation, clearing, acknowledgement and startup behavior for the installed version.
Compile the AS program and verify that its messages are included in the OS configuration. Use the installed version's OS compile procedure with tags and messages included, then review compiler results.
Update the group-display hierarchy through the supported Picture Tree Manager or OS Project Editor workflow. The PCS 7 V7.1 Operator Station manual documents recalculation/update of group displays when saving the picture hierarchy or when the OS Project Editor's create/update option is enabled.
Download the approved AS and OS changes under site change control, then verify the message list and header/area group display using an authorized test condition.

Check the OS hierarchy and message class

The PCS 7 Operator Station manual describes two relevant display relationships: connecting a group display to a process tag, and propagating messages from lower-level pictures through a picture hierarchy. Its V7.1 procedure says the group display hierarchy is updated when the project is downloaded, when the Picture Tree Manager recalculates and saves it, or when the OS Project Editor runs with “Create/update group displays” enabled.

Check that the DB-derived event is assigned to the intended area and that the relevant process picture is part of the expected hierarchy. Confirm the message class maps to a visible group-display type. A message visible in an alarm list is not by itself proof that the top header has the needed EventState or picture-tree relationship.

Verification

Use a controlled test condition that does not actuate hazardous equipment. Confirm that the AS condition changes state, the intended PCS 7 message appears with the right text and class, and the header or area group display reflects the alarm state. Then confirm that the message clears or remains pending according to the intended acknowledgement and return-to-normal behavior.

If the message list shows the event but the group display does not, inspect the message's process-area assignment, group-display EventState linkage and Picture Tree Manager hierarchy. Review OS compile output and confirm that the latest project configuration was downloaded to the relevant OS stations.

Limitations and Operational Precautions

The ticket specifies WinCC V7.5 but not the PCS 7 or APL release, actual alarm-generation method, signal polarity, message class, screenshot content or process-picture hierarchy. The cited APL Event manual is V71; its exact block details must not be assumed identical to another library release. Confirm the matching installed APL manual before selecting a block, configuring message attributes or compiling.

The Event block handles digital signal transitions; analog alarms need properly engineered AS condition logic. Changes to alarm messages, AS logic, OS compilation and downloads can affect annunciation and operator response. Review alarm philosophy, test without unsafe process actuation, and use approved change control.

Engineer FAQ

Can a WinCC tag alarm on a DB automatically drive a PCS 7 group display? Not necessarily. The group display depends on PCS 7 message-state and hierarchy configuration; confirm that the signal is integrated as the required PCS 7 process message.

What does the APL Event block do? In the cited APL V71 manual, Event creates acknowledgeable messages from changes on up to eight digital inputs, with separate message text per input.

Can I connect an analog DB value directly to Event? Event inputs are digital. Create and validate an appropriate Boolean alarm condition in the AS and connect that condition using the installed release's documented design.

Why might the alarm appear in a message list but not in the header? Check the message class mapping, process-area assignment, EventState link and Picture Tree Manager hierarchy, then review OS compilation and download status.

Does checking “Create/update group displays” alone guarantee the custom DB alarm will appear? No. That option updates the hierarchy; it does not by itself establish the event-generation and message-state links for an arbitrary tag.

Technical References

Siemens, PCS 7 Advanced Process Library V71, Function Manual, 03/2009, A5E02102723-01. See Section 8.1 “Event – Creating messages,” pp. 965–975, for digital inputs, edge-triggered messages and block behavior.
Siemens, Process Control System PCS 7 Operator Station V7.1, Configuration Manual, 03/2009, A5E02122464-01. See Section 8.14 (pp. 149–160) for group-display hierarchy, EventState mapping and connection to a process tag or picture.
Siemens, Process Control System PCS 7 Operator Station V9.1 SP1, Configuration Manual, 11/2021, A5E50302515-AB. See Section 6.5, “Compiling OS data,” for transferring SIMATIC Manager tags, messages and texts into the OS.

Search IndustrialAutomation.net for PCS 7 group-display configuration

Show DB-Derived PCS 7 Alarms in the WinCC Group Display