C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

How Renaming Plant Hierarchy Folders Impacts HIDs, Picture Tree, and WinCC Tags in PCS 7

How Renaming Plant Hierarchy Folders Impacts HIDs, Picture Tree, and WinCC Tags in PCS 7

Renaming a folder in the SIMATIC PCS 7 Plant Hierarchy (PH) alters the Higher-Level Designation (HID) across all subordinate CFC charts, blocks, process pictures, and WinCC tags. Because PCS 7 enforces object-oriented naming based on plant layout, the name of each hierarchy folder serves as a structural prefix in the generated tag name (e.g., Plant1/UnitA/Valve101). Renaming a folder triggers automated cascading updates across the project, but requires recompiling the OS and updating block icons. While modern PCS 7 versions automatically rename WinCC tags and adjust Picture Tree navigation without breaking internal links, any external systems relying on absolute tag names (such as OPC clients, Process Historian logging, or custom WinCC C-scripts) must be updated manually.

Table of Contents

Architecture of the Plant Hierarchy and Higher-Level Designation (HID)

In SIMATIC PCS 7, the Plant Hierarchy organizes engineering data according to physical and technological equipment structures:
- Hierarchical Levels: Typically configured according to ISA-88 / ISA-106: Enterprise -> Plant -> Unit -> Equipment Module.
- Higher-Level Designation (HID): The complete technological path string assembled by concatenating folder names with delimiters (e.g., Brewery/Fermentation/Tank_01/Agitator).
- AS-OS Propagation: When "Derive structure from plant hierarchy" is enabled, every block instance DB automatically inherits the HID as its symbolic tag name in both controller memory and WinCC Tag Management.

Cascading Impact on WinCC Tags, Messages, and Picture Tree

When you rename a folder in the Plant Hierarchy (for example, renaming AreaA to Milling):

Project ComponentImpact of Renaming the FolderRequired Engineering ActionCFC Charts and BlocksBlock instance comments and technological names update automatically; internal signal interconnections remain 100% intact.None; CFC manages connections by internal object pointers, not folder strings.WinCC Tag ManagementTag names update during OS compilation: AreaA/Motor1.PV becomes Milling/Motor1.PV.Execute OS Compile. WinCC updates internal tag tables automatically.Alarm LoggingAlarm text strings update to reflect the new HID origin; historical alarm queries shift to the new path.Recompile OS. Old historical archives retain the original path string.Picture Tree NavigatorNavigation hierarchy buttons on the WinCC runtime top bar update automatically to reflect the new name.Run OS Project Editor or ensure Picture Tree update is checked during OS compile.Block Icons in PDLsBlock icons link to the new tag names automatically when block icons are updated.Execute Plant Hierarchy -> Create/Update Block Icons.

External Interface Risks: OPC DA/UA, Historians, and Hardcoded Scripts

While internal PCS 7 mechanisms adapt seamlessly, external and customized software layers represent critical risk vectors:
1. Third-Party OPC DA / UA Clients: External MES, ERP, or SCADA supervisory systems querying tags via Openness or OPC servers will experience broken connections because the OPC Item ID (e.g., AreaA/Motor1.PV_Out#Value) no longer exists.
2. SIMATIC Process Historian (PH) / Tag Logging Archives: Historical trend curves for existing tags may bifurcate. In WinCC Tag Logging, renaming a tag creates a new archive tag under the new name; historical data recorded under the old name will not display continuously on the new trend curve without manual archive redirection.
3. Hardcoded Graphic Scripts: If an engineer wrote custom C-scripts or VBScripts in Graphics Designer containing hardcoded string literals (e.g., GetTagDouble("AreaA/Motor1.PV")), the script will fail at runtime.

Method: Step-by-Step Procedure to Rename a Hierarchy Folder Safely

Follow this procedure to rename a Plant Hierarchy folder while preserving full project integrity:

Step 1: Execute Project Backup and Dependency Audit

  1. In SIMATIC Manager, select File -> Archive... to capture a full baseline backup.
  2. Search WinCC graphics for hardcoded scripts: open WinCC Explorer, select Cross-Reference, and search for the old folder name string. Update any hardcoded script references.

Step 2: Rename the Folder in SIMATIC Manager

  1. Switch to the Plant View in SIMATIC Manager.
  2. Right-click the target hierarchy folder and select Rename (or select Object Properties).
  3. Enter the new folder name (e.g., Milling_Area).
  4. Click OK. A brief processing bar runs as STEP 7 updates the internal hierarchy catalog.

Step 3: Update Block Icons Across Process Pictures

  1. In the Plant View, select the project root.
  2. Select menu Options -> Plant Hierarchy -> Create/Update Block Icons....
  3. Select all picture levels and click OK.
  4. The generator scans all .pdl files, updating the tag bindings of all block icons to match the new HID path.

Step 4: Compile the OS Project

  1. In SIMATIC Manager, right-click the OS Server project and select Compile.
  2. In the compile wizard:
    - Select Tags and messages.
    - Ensure Picture Tree is enabled.
    - Select Changes Only (or Entire Scope if multiple hierarchy levels were altered).
  3. Allow compilation to finish with 0 errors.

Step 5: Download to Target Stations

  1. If only folder renaming was performed without logic changes, download the OS Server and OS Clients via Changes Only.
  2. Verify runtime navigation.

Verification

To verify that the hierarchy rename completed without residual errors:
- Open WinCC Runtime on an operator station: confirm that the top navigation strip displays the new folder name on the area overview button.
- Click the area button: verify that the assigned process picture opens smoothly.
- Test faceplate operation: click multiple motor and valve block icons: confirm that faceplates open, live values update, and operator commands execute.
- Check the WinCC Cross-Reference editor: verify that zero unresolved tag connections exist across all process pictures.

Limitations and Operational Precautions

  • Character Restrictions in Hierarchy Names: Plant hierarchy folder names must not contain special characters, quotation marks, slashes (/, \), or spaces if tags are accessed via OPC. Stick to standard alphanumeric characters and underscores (_).
  • Maximum Path Length (HID Limits): Concatenated HID strings must not exceed 128 characters. If nesting folders deeply, ensure that the total length of Folder1/Folder2/Folder3/ChartName/BlockName remains well within limits to avoid tag truncation.
  • Never Rename Folders While Runtime Compilation is in Progress: Ensure no background OS compilation, archive generation, or client downloads are active before initiating a hierarchy rename.

Engineer FAQ

Does renaming a folder require placing the AS controller in STOP mode?

No. Modifying folder names alters only technological metadata and HMI symbolic tags. The internal machine code executing in the AS controller uses memory addresses and instance DBs, which are unaffected by folder renaming.

Will changing a folder name break inter-chart CFC connections?

No. CFC interconnections between blocks use internal database pointers. The visual margin labels in CFC update automatically to show the new folder path without interrupting signal flow.

How do I maintain continuous historical trend curves after renaming?

In WinCC Tag Logging, before compiling the OS, you can export archive tag mappings and alias the old archive tag name to the new technological HID to preserve unbroken trend history in WinCC OnlineTrendControl.

What happens if I rename a folder that contains an OS Picture?

The Picture Tree Manager updates the picture's node location in the hierarchy navigation structure. The physical .pdl file name on disk remains unchanged unless explicitly renamed in Graphics Designer.

Technical References

  • Siemens Industry Online Support: SIMATIC PCS 7 Plant Hierarchy Engineering Manual.
  • SIOS Entry 109742323: PCS 7 Compendium Part A - Configuration Guidelines (Section: Plant Hierarchy).
  • SIOS Entry 109809264: SIMATIC Process Control System PCS 7 Advanced Process Library Manual.
  • Siemens Support Guide: Managing Plant Hierarchies and HIDs in SIMATIC PCS 7.

Related Articles

Related Tags

  • Plant Hierarchy
  • HID
  • Picture Tree
  • WinCC Tags
  • Block Icons
  • Engineering
  • Industrial Automation
20 respuestas