Mastering Filter Strings and Process Object View Wildcards in SIMATIC PCS 7
In SIMATIC PCS 7 Process Object View (POV), filter strings operate with an automatic, invisible wildcard (*) permanently appended to the end of every entered search term. Consequently, entering PV matches all strings beginning with PV (starts-with behavior). Engineers can use an explicit prefix wildcard (such as *LIM) to execute an 'ends-with' query, but entering an explicit trailing wildcard (such as *LIM*) is redundant or produces unexpected substring matches. For advanced multi-parameter editing, engineers should utilize multi-level criteria filters via the double-down arrow button or export the POV table to CSV/Excel for bulk batch modification.
Table of Contents
- Executive Summary
- Process Object View Architecture and the Filtering Mechanism
- Wildcard Syntax Rules: The Implicit Trailing Joker
- Multi-Level Filtering via the Double-Down Arrow Interface
- Step-by-Step Procedure for Bulk Alarm and Parameter Configuration
- Process Object View Filter Syntax and Query Behavior Matrix
- Verification
- The CSV Export and Import Workflow for Mass Parameter Engineering
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Executive Summary
The Process Object View (POV) in SIMATIC Manager is the central mass-engineering tabular interface in SIMATIC PCS 7, allowing automation engineers to view and configure thousands of process tags, alarm limits, channel connections, and block parameters across the entire Plant Hierarchy. However, engineers accustomed to standard spreadsheet or SQL wildcard syntax often experience frustration when attempting to filter for specific parameter patterns (such as locating all high alarm limits PV_AH_Lim or filtering specific instrumentation loops). Entering typical wildcard strings like *LIM* frequently yields unexpected matches or empty result sets. This technical article clarifies the internal query syntax of the POV filter engine, explains the implicit trailing wildcard rule, and details efficient mass-engineering workflows.
Process Object View Architecture and the Filtering Mechanism
The Process Object View provides a unified technological perspective over the underlying STEP 7 database:
- Tabular Structure: Data is categorized into dedicated tabs: General, Blocks, Parameters, Signals, Messages, Picture Objects, and Archive Tags.
- Hierarchical Inheritance: When an engineer selects a hierarchy folder in the left pane, the right-hand table displays only the technological objects contained within that folder and its child folders.
- Database Filtering Engine: Filtering in POV does not use standard regex or Excel expression evaluation; instead, it executes optimized internal queries against the local Sybase/Access project database.
Wildcard Syntax Rules: The Implicit Trailing Joker
The primary source of confusion in POV filtering lies in how the query parser treats string boundaries:
- The Automatic Trailing Asterisk: The POV query engine automatically appends an invisible asterisk (
*) to the end of every filter string entered by the user. If an engineer typesPV, the engine internally executesPV*, returningPV,PV_In,PV_AH_Lim, andPV_Unit. - Prefix Wildcard Support (Ends-With): The engine supports an explicit leading asterisk. Typing
*LIMmatches all attributes whose names end withLIM(e.g.,PV_AH_LIM,SP_LL_LIM). - Substring Matching (Contains): If an engineer enters
*C-YY, the query evaluates as*C-YY*. It matchesABC-YY, but also matchesABC-YYXZ. Because the trailing asterisk cannot be turned off, strict exact-match filtering requires specific syntax. - Empty Field Filtering: To filter for records where a specific column is blank or unconfigured, enter a single blank space (
) into the filter cell.
Multi-Level Filtering via the Double-Down Arrow Interface
When single-column filtering is insufficient to isolate target parameters, engineers should utilize multi-level filtering:
- Accessing Advanced Filters: At the right-hand edge of the filter row, click the double-down arrow (
>>) icon. - Secondary Criteria Rows: This reveals secondary and tertiary filter rows, allowing combined boolean
ANDfiltering across multiple distinct columns simultaneously. - Example Application: On the Messages tab, set Column 1 (
Block Type) toPIDConL, Column 2 (Message Identifier) to*AH*, and Column 3 (Priority) to> 8. This instantly isolates all high-priority analog alarm definitions without parsing unrelated motor or valve signals.
Step-by-Step Procedure for Bulk Alarm and Parameter Configuration
To rapidly adjust parameter values (such as alarm limits across all pressure transmitters) using POV:
- In SIMATIC Manager, select the top-level Plant Hierarchy folder to include all plant areas.
- Open Process Object View (
View -> Process Object Viewor pressF8). - Select the Parameters tab.
- In the filter row under the I/O Name column, enter
*AH_Limto display all high-alarm limit parameters. - In the Block Type column, enter
MonAnLto restrict results to analog monitoring blocks. - Sort the table by the Value column to identify out-of-spec or uninitialized limit values.
- Edit values directly in the grid cells; changes are immediately committed to the CFC database.
Process Object View Filter Syntax and Query Behavior Matrix
The following table provides verified query syntax and matching behavior across Process Object View columns:
PVPV*PV, PV_In, PV_AH_Lim*LIM*LIM*PV_AL_LIM, SP_HLIM_VAL*** (Single Space)IS NULL OR = ''> 50> 50<> 0<> 0Verification
To verify that filtered parameter modifications have been applied cleanly:
- Clear Filters: Click the
Clear Filtericon on the POV toolbar. Verify that all hierarchy records reload cleanly without errors. - Open Target CFC: Navigate to a modified block in the Plant View and open its CFC chart. Confirm that the parameter value on the block pin matches the value entered in POV.
- Delta Compilation Test: Perform a
Compile Charts as Program -> Changes only. Confirm that the compiler detects modified parameters and successfully generates delta download code without errors.
The CSV Export and Import Workflow for Mass Parameter Engineering
When plant requirements exceed the filtering capabilities of the POV user interface:
- Exporting Table Data: Filter the desired tab and select
Process Objects -> Export to File...to save the view as a CSV or text file. - Spreadsheet Manipulation: Open the exported CSV in Microsoft Excel or an engineering script. Apply complex regex, mathematical scaling formulas, or cross-reference lookups against the piping and instrumentation diagrams (P&ID).
- Importing Verified Data: Return to SIMATIC Manager POV and select
Process Objects -> Import from File.... - The import engine parses the CSV, validates block existence and data types, and updates the CFC charts in a single transaction.
Limitations and Operational Precautions
Never modify the structural columns (such as Chart Name, Block Name, or Hierarchy Path) via CSV import while multiple engineers are working concurrently in a multi-user engineering project. Structural renames must be executed strictly within SIMATIC Manager.
Process Object View mass changes modify actual offline controller parameters. When modifying safety-related parameters in fail-safe F-Systems, POV cannot bypass fail-safe signature checks; F-parameters must be verified according to safety lifecycle protocols.
Engineer FAQ
Can I use regular expressions in the POV filter row?
No. Process Object View only supports basic wildcard asterisks (*), numerical comparison operators (>, <, <>), and blank space filters.
Why does typing a word in the filter field hide all my rows?
Because of case sensitivity or column mismatch. Check whether the column is text or numerical, and verify that parent hierarchy folders are selected.
Does editing a value in POV immediately change the running controller?
No. POV edits modify the offline project database. The changes must be compiled and downloaded to the automation station to take effect.
Can I edit OS block icon attributes directly from POV?
Yes. The 'Picture Objects' tab in POV allows bulk configuration of block icon names, display formats, and screen assignments.