Customizing the PCS 7 Measuring Point Browser - Displaying Custom and APL Blocks via XML Configuration

To display custom technological blocks or additional standard APL blocks (such as Intlk02) in the SIMATIC PCS 7 Measuring Point Browser (Messstellenbrowser), create a custom XML configuration file following the naming convention PCS7_TagStates_XXX.xml and deploy it to the directory C:\Program Files (x86)\SIEMENS\WinCC\Options\SSM\ on BOTH the OS Servers and all OS Clients. In the XML file, define the required status columns under and map the target block types and status word bit masks under . Deploying the file on the client alone will fail because the OS Server evaluates tag status queries; restart WinCC Runtime on all nodes after deployment.

Architecture of the SIMATIC PCS 7 Measuring Point Browser

The SIMATIC PCS 7 Measuring Point Browser (Messstellenbrowser) is an integrated OS toolbar utility that allows operators to query and filter all technological measuring points (motors, valves, controllers, interlocks) across the plant based on operational states (such as Manual mode, Simulation active, Interlocked, Maintenance bypass, or Alarm inhibited).

The parsing rules that determine which block types appear and how their internal status words are evaluated are governed by modular XML files stored in:
C:\Program Files (x86)\SIEMENS\WinCC\Options\SSM\
The default definitions reside in PCS7_TagStates_APL.xml.

XML Schema Organization: Columns, Types, and Bit Masks

The XML configuration structure contains two foundational sections:

<Columns>: Declares the operational states displayed as table columns (e.g. Manual, Simulation, Interlocked). Defines multilingual column headers, tooltip descriptions, and icon bitmap paths.
<Types>: Declares each technological block type (e.g. MotL, VlvL, Intlk02, or custom block MyMotor). Each type specifies which WinCC status tag (.Status1, .Status2, .EventState) and bit mask (e.g. 0x00000001) corresponds to each column defined in <Columns>.

Why Modifying the Client Alone Causes Display Failures

A frequent troubleshooting pitfall is editing the XML file exclusively on an OS Client workstation:

The Measuring Point Browser executes distributed database queries: the OS Client UI reads column formatting, but the underlying tag query engine executes on the OS Server.
If the custom XML file (PCS7_TagStates_Custom.xml) is missing on the OS Server, the server's query provider ignores the unrecognized block types, returning zero records to the client.
Mandatory Rule: The custom XML file must be copied to the Options\SSM directory on all OS Servers, redundant partners, and all OS Clients.

Step-by-Step Configuration Workflow for Custom Blocks and Intlk02

Follow this procedure to integrate new blocks safely:

Create Custom XML File:
- Navigate to C:\Program Files (x86)\SIEMENS\WinCC\Options\SSM\.
- Copy PCS7_TagStates_APL.xml and rename it to PCS7_TagStates_Custom.xml (never overwrite the original).
Add Custom Block and Intlk02 Definitions:
- Open PCS7_TagStates_Custom.xml in an XML editor.
- Under <Types>, insert a <Type Name="Intlk02"> entry:
Map status tag .Status1 bit 0 to the 'Tripped/Interlocked' column.
- Insert your custom block entry <Type Name="MyCustomBlock"> mapping relevant status bits.
Distribute to All Nodes:
- Copy PCS7_TagStates_Custom.xml to the identical directory on Server 1, Server 2, and all OS Clients.
Restart WinCC Services:
- Deactivate and reactivate WinCC OS Runtime (or reboot the stations) to force the SSM subsystem to re-index XML files.

Comparison of Measuring Point Browser vs Custom Status Views

The table below contrasts the Measuring Point Browser with alternative status monitoring approaches:

Monitoring ToolConfiguration BaseEngineering EffortMulti-Station DeploymentOperating ScopeMeasuring Point BrowserXML (Options\SSM\*.xml)Low (Schema mapping)Requires file sync to all nodesPlant-wide filtering by operating modeCustom WinCC Table ControlSQL / VBScript in PDLHigh (Script programming)Embedded in graphic pictureLocal screen-specific asset viewsProcess Object ViewSIMATIC Manager (ES)Zero (Built-in)Engineering Station onlyOffline engineering & parameter tuningSMMC Asset InventorySMMC Management AgentZero (Console based)Centralized consoleHardware & firmware lifecycle audits

Verification

Verify custom block visibility in runtime:

Open WinCC OS Runtime on an OS Client.
In the OS title bar, click the Measuring Point Browser button.
In the Filter dialog, expand the block type dropdown; confirm that Intlk02 and your custom block type are selectable.
Select Simulation or Manual filter; confirm that instances in those modes appear in the results list.
Double-click an entry; verify that the standard faceplate opens immediately.

Limitations and Operational Precautions

Review the following technical precautions regarding SSM XML customization:

Do Not Modify Original XML: Editing PCS7_TagStates_APL.xml directly risks having all customizations wiped out during the next PCS 7 update or service pack installation. Always use the PCS7_TagStates_<Custom>.xml convention.
Syntax Validation: Ensure the XML file contains valid XML syntax without unclosed tags or illegal characters, as an XML parser error causes the entire Measuring Point Browser to fail to load.
Case Sensitivity: Block type names inside <Type Name="..."> are case-sensitive and must match the block type family name in SIMATIC Manager.

Engineer FAQ

Why must the custom XML file be installed on OS Servers as well as OS Clients?

Because tag evaluation and status queries are executed on the OS Server database engine. If the server does not recognize the block type in its SSM configuration, it will not return data to the client.

What naming format is mandatory for custom Measuring Point Browser XML files?

The file must be named PCS7_TagStates_XXX.xml (where XXX is a unique custom identifier) and placed in C:\Program Files (x86)\SIEMENS\WinCC\Options\SSM.

Can I display non-APL standard library blocks in the Measuring Point Browser?

Yes, by defining the block name and its corresponding status word and bit masks in your custom XML file, any block type can be evaluated by the browser.