Filtering Exact Block Names and Managing Substring Matching in PCS 7 Process Object View

In SIMATIC PCS 7 Process Object View, text filters operate via substring matching ('contains') rather than exact string equality, causing queries for 'Meldung' to return both 'Meldung' and 'Meldung8'. The filter syntax does not support regular expression boundary anchors or quotation marks. To isolate exact block types, filter by the substring, click the Block Type column header to sort identical names into contiguous groups, or export the view to Microsoft Excel using Process Objects > Export, where exact equality filters can be applied before re-importing.

Architecture of Filter Mechanisms in Process Object View

In SIMATIC PCS 7, the Process Object View (PO View) serves as the central mass-engineering tabular editor for the plant hierarchy. Across its specialized tabs (General, Blocks, Parameters, Signals, Messages, and Picture Objects), engineers manage thousands of technological instances simultaneously.

To help navigate massive projects, each tab features column-specific filter boxes along the top header. Typing into a filter box instantly restricts the displayed rows. However, the filtering engine implemented in SIMATIC Manager uses a legacy substring comparison algorithm (InStr): any block whose type name contains the entered search string is evaluated as a match.

Why Substring Matching Causes Partial String Overlaps

When an engineering project employs technological blocks with overlapping root names:
* Block Type A: Meldung (custom single-alarm block).
* Block Type B: Meldung8 (custom eight-alarm block).
* Entering Meldung into the Block Type filter box matches both Meldung and Meldung8.
* Entering special characters such as ^Meldung$, "Meldung", or Meldung fails because the filter parser does not interpret regular expressions or escape delimiters; it treats quotation marks and punctuation as literal search characters, returning zero results.

Effective Workarounds: Column Sorting, Grouping, and Excel Export

Engineers can isolate and manipulate specific block types using three validated techniques:

TechniqueProcedureAdvantagesBest ApplicationColumn SortingFilter by Meldung, then click the Block Type column header.Sorts rows alphabetically; groups all Meldung instances into a contiguous block ahead of Meldung8.Quick visual audits; selecting a continuous range for editing.Excel Export / ImportExport table via Process Objects > Export, filter using Excel exact match, edit, and re-import.Full power of Excel formulas, exact string filtering (= "Meldung"), and bulk parameter fill.Mass engineering changes, I/O reassignment, and signal auditing.Hierarchy IsolationSelect a specific technological unit folder in the left tree rather than root project.Limits the search domain to a smaller technological subset.Unit-level commissioning and debugging.

Table 1: Workaround strategies for exact name filtering in Process Object View.

Standardizing Technological Naming Conventions to Prevent Filter Collisions

To avoid substring collisions entirely across large automation projects, Siemens recommends establishing rigid naming rules in the plant coding standard:
1. Use Distinct Delimiters: Instead of appending numbers directly (Meldung and Meldung8), use delimiters: Meld_01 and Meld_08, or Msg_Single and Msg_Octal.
2. Standardize on APL Naming Syntax: APL uses fixed-character length naming conventions: MonDiL (Digital Monitoring Large), MonDiS (Digital Monitoring Small), OpDi01 vs OpDi03.
3. Prefix Custom Blocks: Prefix site-specific blocks with company or technological initials (e.g., CUST_Meld01, CUST_Meld08).

Verification

To confirm proper filtering and isolation:

In SIMATIC Manager, select the plant hierarchy folder and open Process Object View > Blocks.
Type Meldung into the Block Type filter box.
Click the Block Type header to sort: verify that all Meldung instances appear grouped contiguously.
Select all rows of the Meldung group: verify that status bar row count matches the expected instance count.
Perform an export to CSV: open in Excel and confirm that exact string filters isolate the target block type cleanly.

Limitations and Operational Precautions

When re-importing CSV data into Process Object View, ensure column headers and hierarchy paths remain unmodified; corrupted headers cause import rejections.
Never rename block types directly in the Symbol Table while CFC charts are actively using them without performing a complete block type reorganization.
The PO View filter is case-insensitive by default in most PCS 7 versions.

Engineer FAQ

Does Process Object View support wildcard characters like '*' or '?'?

No. The PO View filter performs an implicit wildcard search (*string*). Entering explicit asterisks often results in matching errors.

Can I filter by multiple criteria simultaneously?

Yes. You can enter filter strings across multiple columns concurrently (e.g., Block Type = Meldung AND Chart = Reactor01 AND Hierarchy = AreaA).

Why are some block instances hidden even when no filter is typed?

Check the hierarchy tree selection on the left: if a subfolder is highlighted, PO View displays only objects within that subfolder. Select the project root to view all objects.