Configuring Manual Mode Operating Messages (Bedienmeldungen) in PCS 7 V9 APL Blocks

In SIMATIC PCS 7 V9.0 (with Advanced Process Library V9.0 SP2), switching an aggregate or controller into Manual mode (Hand Modus) does not automatically generate an operator message ('O' on a purple background in the WinCC group display) because modern APL standards intentionally decouple mode changes from automatic alarm generation to comply with alarm management standards (ISA-18.2 / EEMUA 191). In legacy PCS 7 V6.x, operating messages were hardcoded into standard library blocks. To implement this functionality in PCS 7 V9, interconnect the block's 'ManAct' (Manual Mode Active) output to an external message input pin (such as ExtMsg1) on the block, and configure ExtMsg1 with Message Class 'Operating Message' (Bedienmeldung - Class 10). To configure this across hundreds of blocks efficiently, use the Process Object View (POV) in SIMATIC Manager.

Executive Summary

Facility migrations from legacy PCS 7 V6.0 systems to PCS 7 V9.0 SP2 frequently reveal differences in operational alarm philosophies. Operators accustomed to legacy systems expect an immediate, high-visibility visual indicator—the classic white 'O' on a purple background in the WinCC overview area and group display (Sammelanzeige)—whenever any field motor, valve, or PID loop is switched from Automatic to Manual mode. In modern APL architecture, automatic mode-switching alarms were removed to prevent alarm flooding during routine plant operations. Restoring this critical operator feedback across plant sections is achieved by wiring ManAct to external message parameters and utilizing the Process Object View for rapid, bulk parameterization.

Architecture and Fundamental Mechanics

The alarm generation and group display architecture in SIMATIC PCS 7 bridges AS block state changes with WinCC overview banners:

The Legacy vs. Modern Alarm Philosophy:
* Legacy PCS 7 V6.x (Standard Library): Blocks like MOTOR and VALVE had built-in message triggers bound directly to manual mode switches. While useful in small systems, large plants experienced severe alarm flooding whenever operators switched banks of equipment to manual.
* Modern PCS 7 V9.x (Advanced Process Library): Aligns with ISA-18.2 / IEC 62682 / EEMUA 191 alarm management standards. Mode changes are treated as operator events recorded in the WinCC Operation Log (OperationLog), rather than generating persistent alarms in the alarm list, unless explicitly engineered.
The Group Display (Sammelanzeige) Mechanics:
* In the WinCC overview screen, the Group Display evaluates hierarchical alarm states aggregated by the @...#EventState tag.
* When a message of Class Operating Message (Bedienmeldung) triggers, WinCC lights up the dedicated 5th button in the group display: rendering a white letter 'O' on a violet/purple background.
* This informs control room supervisors at a glance that equipment in that plant area is currently under manual operator intervention.
APL Message Interfacing (ManAct to ExtMsg1):
* Every APL control block (MotL, VlvL, PidConL) outputs a boolean signal ManAct (Manual mode active: 1 when in Manual, 0 when in Auto).
* APL blocks also provide external message trigger inputs: ExtMsg1, ExtMsg2, ExtMsg3.
* By connecting ManAct to ExtMsg1, every transition into manual mode triggers the internal ALARM_8P call associated with that block.
Mass Configuration via Process Object View (POV):
* Manually opening hundreds of CFC charts to wire ManAct to ExtMsg1 is error-prone and time-consuming.
* SIMATIC Manager provides the Process Object View (POV), allowing table-based bulk interconnection and message class assignment across entire plant hierarchy folders.

Step-by-Step Implementation Procedure

Follow these procedures to configure Manual mode operating messages across APL blocks in PCS 7 V9:

Configure the External Message in CFC (Single Block Method):
* Open a CFC chart containing an APL block (e.g., MotL / FB 1850).
* Locate output pin ManAct and input pin ExtMsg1.
* Wire ManAct directly to ExtMsg1.
* Right-click the block and select Special Object Properties > Message....
* In the Message Configuration window, locate the row corresponding to ExtMsg1 (typically Message 5 or 6):
- Set Message Class to Operating Message (Bedienmeldung - Class 10).
- Set Message Text to: $$BlockComment$$ - Manual Mode Active.
- Click Save.
Mass Bulk Configuration via Process Object View (POV):
* In SIMATIC Manager, switch to Plant View (View > Plant View).
* Select the root plant hierarchy folder.
* Open the Process Object View (View > Process Object View or press F8).
* Navigate to the Messages tab:
- Filter by block type (e.g., MotL, VlvL, PidConL).
- Locate the column for ExtMsg1.
- In the Message Class column, select Operating Message for the entire column using copy/paste.
- In the Message Text column, enter @1%s@ Manual Mode Active.
- Navigate to the Signals or Interconnections tab:
- Locate the ExtMsg1 input column.
- Bulk-assign the connection to the block's own ManAct output (e.g., ChartName\BlockName.ManAct).
Compile the S7 Program and OS:
* In SIMATIC Manager, execute PLC > Compile and Download Objects.
* Select all AS programs and perform Compile: Changes only with 'Generate module drivers'.
* Select the WinCC OS and perform OS Compile: Entire OS (to ensure text and message class mappings update completely).
Download and Activate in Runtime:
* Download AS program changes in RUN.
* Download OS changes or activate WinCC Runtime.

Verification

In WinCC Runtime, open an operator graphic. With a pump in Auto mode, observe that the group display shows no purple indicator. Click the block icon to open the APL faceplate and switch the pump to Manual mode. Confirm that: (1) An operating message appears in the WinCC message list stating 'Manual Mode Active', and (2) The WinCC Group Display in the top overview area immediately illuminates the white 'O' on a purple background. Switch back to Auto; confirm that the message clears and the purple indicator extinguishes.

Limitations and Operational Precautions

Deploying operating messages for manual mode on hundreds of non-critical devices can clutter the alarm banner. Ensure plant operational guidelines align with this philosophy and reserve operating messages for critical control loops and major process drives.

Engineer FAQ

Why is the 'O' symbol purple in WinCC?

In the standard Siemens WinCC message system, Class 10 ('Bedienmeldung' / Operating Message) is assigned purple as its standardized background color to distinguish it from red (alarms) and yellow (warnings).

Does ExtMsg1 consume an AS Process Object?

No. The block is already instantiated; utilizing its existing message pins (ExtMsg1-ExtMsg3) incurs zero additional Process Object licensing cost.

Can I log manual mode without triggering the group display?

Yes. If you want mode changes recorded in the historical log without lighting up the group display, configure the Message Class as 'Operational Notification' without group display mapping.