Efficient Workflow for Renaming Steps and Transitions in PCS 7 SFC Types

In SIMATIC PCS 7, step and transition names in SFC Types cannot be modified in bulk through the Process Object View (PO View) or Import/Export Assistant (IEA-PO) because step properties are internal chart topology elements rather than external block parameters. The most efficient built-in engineering workflow is to open the Step Properties dialog of the first step in the SFC Editor and use the navigation arrow buttons located at the bottom of the dialog to cycle sequentially through all steps and transitions. Clicking the navigation arrow automatically commits the current name and opens the adjacent step without closing and reopening the dialog.

Executive Summary

Standardization of sequential control logic requires consistent, descriptive naming of steps and transitions across SFC Types. During sequence development or refactoring, engineers frequently need to rename dozens of sequential steps (e.g. from generic Step1, Step2 to functional designations like Dosing_ReactantA, Agitation_HighSpeed). Because practitioners rely heavily on the tabular bulk-editing capabilities of the Process Object View (PO View) for tags and messages, they often search for a corresponding grid view to rename all SFC steps simultaneously. In SIMATIC PCS 7, step names are not exposed to PO View. This article explains the architectural encapsulation of SFC topology metadata and presents the most efficient sequential workflows and external engineering options.

Architecture and Fundamental Mechanics

SFC Internal Data Models, Topology Metadata Storage, and PO View Scope Boundaries:

Architecture of SFC Topology Storage:
In SIMATIC PCS 7, an SFC Type is compiled into a runtime Function Block (FB), but its internal topological layout—including step coordinates, step names, transition conditions, and comment strings—is stored inside proprietary binary graphic containers in the project S7 program database.
The Process Object View (PO View) and Import/Export Assistant (IEA-PO) interact exclusively with the COM interface of the S7 database representing Block Parameters, Interconnections, I/O Signals, and Alarm Messages.
Step and transition names are topological graph nodes, not block I/O attributes; consequently, PO View does not expose them in its tabular columns.
The Rapid Sequential Navigation Mechanism in SFC Editor:
Inside the SFC Editor, the Step Properties and Transition Properties modal dialogs incorporate a sequential cursor control.
At the lower-left corner of the dialog, two directional blue arrows (< and >) navigate to the previous and next sequential topological nodes.
Pressing the arrow key executes three actions atomically:
1. Validates the newly entered step name against character restrictions (maximum 16 alphanumeric characters, no spaces).
2. Commits the name to the internal database.
3. Refreshes the dialog fields with the subsequent step's parameters without GUI destruction or modal redisplay overhead.
Advanced Bulk Options via Plant Automation Accelerator (PAA):
For enterprise plants requiring automated bulk manipulation of SFC sequences, Siemens Plant Automation Accelerator (PAA) or COMOS provides full object-oriented engineering, permitting tabular renaming of steps and seamless bi-directional synchronization with PCS 7 via CAx XML exchange.

Step-by-Step Implementation Procedure

Open the SFC Type in the SFC Editor:
* In SIMATIC Manager, navigate to the Master Data Library or project S7 Program.
* Double-click the SFC Type to open it in the SFC Editor window.
Access the Step Properties Dialog:
* Locate the initial step of the sequence (e.g. RUN_START).
* Double-click the step block (or right-click and select Object Properties).
Execute Rapid Sequential Renaming:
* In the General tab, the cursor defaults to the Name text field.
* Type the new standardized name (e.g. Init_Purge).
* Optional: Press Tab twice to update the Description field.
* Click the Next (>) navigation arrow button at the bottom of the dialog.
* The dialog automatically updates to the next step; type the new name and repeat.
Rename Transitions Sequentially:
* After finishing steps, double-click the first transition icon (T1).
* Update the transition name in the properties dialog.
* Use the navigation arrow buttons at the bottom to cycle through and rename all remaining transitions.
Compile the SFC Type and Update Block Instances:
* Select menu Options > Compile in the SFC Editor.
* In the CFC Editor, select Options > Block Types, select the SFC Type, and click New Version.
* Execute a CFC Changes compilation and download changes to the AS in RUN mode.

Verification

Inspect the SFC sequence canvas; verify that all step boxes and transition flags display the updated names.
Open WinCC Runtime on an operator client; click the SFC block icon.
Confirm that the active step name rendered on the SFC faceplate header reflects the newly assigned technological name.

Limitations and Operational Precautions

Step names in SIMATIC PCS 7 must not exceed 16 characters and must not contain spaces, commas, or special punctuation characters other than underscores. Renaming steps changes the step identifiers logged in WinCC Alarm Logging and SIMATIC BATCH electronic batch records; plan sequence renaming prior to commissioning active production.