Resolving Discrepancies Between Block Message Configuration and Process Object View in SIMATIC PCS 7

In SIMATIC PCS 7, discrepancies where the OS Area displayed in a block's internal message configuration (Special Properties -> Messages) differs from the area shown in the Process Object View (POV) occur because the block instance has not inherited the updated Plant Hierarchy path or because the OS message attributes have become desynchronized. When charts are moved between hierarchy folders or renamed without executing a full Plant Hierarchy update, the Process Object View reflects the folder path, but the compiled message headers retain the old area assignment. To resolve this, execute 'Plant Hierarchy -> Update Block Contacts/Messages' in SIMATIC Manager and recompile the OS.

Plant Hierarchy Message Inheritance and Process Object View Architecture

In SIMATIC PCS 7, alarm routing relies on the Plant Hierarchy (PH):
* The OS Area: Defined by the hierarchy folder designated as the 'OS Area' level (e.g. Level 2: Unit_Distillation).
* Message Property Inheritance: When a block (e.g. MonAnL, MotL) is placed in a chart, its embedded ALARM_8P messages inherit the parent folder's technological path and OS Area into their message text parameters ($$Area$$, $$Origin$$).
* The Process Object View (POV): A tabular mass-engineering view in SIMATIC Manager. It queries the active database tables, allowing engineers to audit parameters, signals, and messages globally across all charts.

Root Causes of Area Inconsistencies Between Block Messages and POV

When the block message dialog and Process Object View report conflicting areas:
1. Moved Charts Without Message Update: An engineer moved a CFC chart from Area A to Area B in Plant View. The POV immediately reflects the new folder location, but internal message text fields inside the CFC block retain the old Area A string until explicitly updated.
2. Manual Overrides in Message Configuration: If an engineer manually typed a custom area string into the block's Messages... dialog, the block disables automatic Plant Hierarchy inheritance, locking the manual string.
3. Desynchronized Hierarchy Depth: Modifying the 'Level for OS Area' in Options -> Plant Hierarchy -> Customize without propagating changes across all existing blocks.

Remediation Procedure - Synchronizing Message Areas and Compiling OS

Follow this procedure to eliminate area discrepancies:

[Phase 1: Update Block Messages Across Plant Hierarchy]
   │  • In SIMATIC Manager: Switch to Plant View
   │  • Select the Multiproject root folder
   │  • Navigate to menu: Options -> Plant Hierarchy -> "Update Block Contacts/Messages"
   │  • STEP 7 parses all charts and forces embedded ALARM_8P message parameters
   │    to inherit the active folder's OS Area
   │
[Phase 2: Audit in Process Object View (POV)]
   │  • In SIMATIC Manager: Select the project -> Open "Process Object View"
   │  • Select the "Messages" tab
   │  • Review columns: "Chart", "Block", and "OS Area":
   │      - Verify that the "OS Area" column exactly matches the parent hierarchy folder
   │      - If manual overrides exist, delete them to restore automatic inheritance
   │
[Phase 3: Compile AS and OS Changes]
   │  • In CFC: Chart -> Compile -> Changes Only
   │  • In SIMATIC Manager: Select OS -> Compile -> Scope: "Tags and messages"
   │  • Download changes to the OS Server -> Alarms route to the correct area!

Message Configuration and Area Inheritance Comparison Matrix

Compare message properties across engineering views:

Engineering InterfaceSource of Area DataUpdate MechanismRisk if DesynchronizedProcess Object View (POV)Real-time Plant View folder pathDynamic database viewMisleads engineer if blocks are stale.Block Messages DialogStored block parameter stringsInherited from PH / ManualSends wrong area prefix to WinCC.WinCC Alarm LoggingCompiled OS message databaseGenerated during OS CompileOperators miss alarms due to wrong area filters.

Verification

To confirm that message areas are synchronized:
1. Open the CFC chart; right-click the block -> Object Properties -> Special Properties -> Messages....
2. Confirm that the OS Area field displays the exact technological name of the parent hierarchy folder.
3. Open the Process Object View -> Messages tab; confirm that the table row matches the block dialog.
4. In WinCC Runtime, force a test alarm on the block; confirm that the alarm appears under the correct area button in the top overview bar.
5. Verify that filtering alarms by area displays the message accurately.

Limitations and Operational Precautions

Never hardcode custom area names directly into the message text fields of standard APL blocks. Manual overrides bypass the automated Plant Hierarchy engine and will result in alarm filtering failures when operators navigate using standard area overview buttons. Always manage technological areas through the Plant Hierarchy folders.

Engineer FAQ

Why did moving a CFC chart not update its alarm area immediately?

Moving a chart updates its file location, but embedded message parameters inside compiled S7 blocks require running 'Update Block Contacts/Messages' to re-write parameter strings.

Can I edit message areas for hundreds of blocks at once?

Yes. In the Process Object View -> 'Messages' tab, you can edit or copy-paste area assignments across multiple blocks simultaneously.

What determines which hierarchy level becomes the OS Area?

In SIMATIC Manager, go to Options -> Plant Hierarchy -> Customize...; the setting 'Level for OS Area' (e.g. Level 2) designates the area level.

Do I need to download to the CPU after updating message areas?

Yes. Because message text attributes are stored in data blocks within the CPU, a CFC compilation and delta download to the AS is required.

Technical References

Related Tags

Process Object View
Message Configuration
OS Area
Plant Hierarchy
Alarm Routing

Process Object View

Message Configuration

OS Area

Plant Hierarchy

Alarm Routing

6 respuestas

Resolving Discrepancies Between Block Message Configuration and Process Object View in SIMATIC PCS 7