Configuring Equipment Phase Display Names Versus Type Names in SIMATIC BATCH
To resolve discrepancies where SIMATIC BATCH displays Equipment Phase (EPH) Type names (e.g., EPH_Dose) instead of instance names (e.g., Dose_Tank1) in recipe procedures, adjust the representation settings in the BATCH Recipe Editor and Batch Control Center (BCC). In the Recipe Editor, navigate to Options -> Settings -> View / Display, or select the specific recipe phase properties, and configure the display preference to show the instance 'Name' rather than the 'Type'. Furthermore, ensure the Plant Hierarchy and SFC Type compilation for SIMATIC BATCH are aligned: if a phase is defined as a generic recipe phase across a unit class, it initially displays the generic type until bound to a specific unit instance during recipe creation or batch execution.
Table of Contents
- Executive Summary
- Architecture and Fundamental Mechanics
- Step-by-Step Implementation Procedure
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Executive Summary
In automated batch processing facilities operating under ISA-88 standards with SIMATIC BATCH, recipe creators and operators rely on graphical recipe views to track execution sequences. A common source of confusion across different PCS 7 environments occurs when one system displays instantiated equipment names (e.g., Agitate_Vessel_A) while another displays generic type names (e.g., EPH_Agitate) within the Recipe Editor and Batch Control Center (BatchCC). This inconsistency impairs operational clarity and complicates recipe verification. The display behavior is governed by a combination of SIMATIC BATCH user interface display preferences, the category classification of SFC Types (EPH vs. EPH Interface/Derived), and whether unit-independent or unit-specific recipe modeling is employed.
Architecture and Fundamental Mechanics
The representation of equipment phases in SIMATIC BATCH is governed by the relationship between the Plant Hierarchy, SFC Types, and Recipe Editor configuration:
-
SFC Type Category and Recipe Phases (RPH): In PCS 7, equipment phases are created as SFC Types assigned to specific BATCH categories in their object properties:
-EPH: Direct equipment phase tied to a specific technological SFC instance. The recipe phase (RPH) name defaults to the SFC Type name.
-EPH (interface): Generic interface defining setpoints and control strategies without execution logic.
-EPH (derived): Implementation of the interface containing physical logic in an equipment module. -
Recipe Structure: Unit-Independent vs. Unit-Specific: In hierarchical recipes, Unit Procedures (RUP) contain Recipe Operations (ROP) and Recipe Phases (RPH). If a recipe is designed to run across a Unit Class (multiple interchangeable tanks), the Recipe Editor displays the generic Type Name (e.g.,
EPH_Heat) because the actual physical unit has not yet been selected. If the recipe is modeled directly against a specific Unit Instance, the Recipe Editor displays the specific Instance Name (e.g.,Heat_TK101). -
Display Preference Configuration: Within the Batch Control Center (BatchCC) and Recipe Editor, user preferences dictate how technological elements are rendered. The options toggle whether graphic blocks show the technological hierarchy path, the type identifier, or the instance comment. In multi-client architectures, these settings are stored in local workstation user profiles.
Step-by-Step Implementation Procedure
To harmonize and configure the display of EPH names across SIMATIC BATCH systems, execute the following steps:
-
Configure Recipe Editor Display Options:
- Open the SIMATIC BATCH Recipe Editor.
- Navigate toOptions -> Settings(orTools -> Settings).
- In the settings tree, selectDisplay / Representation(orView Options).
- Locate the option forRepresentation of Technological Objects.
- SelectTechnological Name(orInstance Name) instead ofType Name.
- ClickApplyandOK. -
Configure Batch Control Center (BatchCC) General Settings:
- OpenBatch Control Center (BatchCC).
- SelectOptions -> Settings.
- Verify that the display format for batches and unit allocation is set to display equipment tag names. -
Verify SFC Type Definition in SIMATIC Manager:
- In SIMATIC Manager Component View, navigate to the Master Data Library chart container.
- Right-click the SFC Type and selectObject Properties.
- Check theCategoryfield. Ensure it is configured appropriately (EPHvs.EPH interface). -
Recompile and Download BATCH Process Cell Data:
- In SIMATIC Manager Plant View, right-click the root Process Cell folder.
- SelectSIMATIC BATCH -> Compile / Download.
- SelectCompileto regenerate the BATCH types and plant model.
- In BatchCC, selectProcess Cell -> Update Process Cellto read the newly compiled data.
Verification
Confirm consistent naming representation in the BATCH environment:
-
Recipe Editor Inspection: Open a Master Recipe. Confirm that phase blocks display the intended instance name (e.g.,
Dose_Tank1) rather than the generic SFC type name (EPH_Dose). -
Batch Execution Monitoring: Create a control recipe from the master recipe in BatchCC and start a test batch. Confirm that the active batch control view clearly identifies the allocated equipment instance.
-
Multi-Client Consistency: Open the Recipe Editor on secondary engineering clients. Verify that local display options render matching naming formats across all stations.
Limitations and Operational Precautions
When recipes are intentionally constructed for Unit Classes (generic recipes capable of running on any tank in a class), phases must display generic type names during recipe authoring until an active unit is selected during batch scheduling. Forcing instance names on class-based recipes restricts flexibility and breaks recipe transportability.
Engineer FAQ
Why do two different BATCH engineering PCs show different phase names for the same recipe?
Representation settings in the Recipe Editor (Options -> Settings -> Display) are stored locally per Windows user profile on each workstation. If one PC is set to 'Type Name' and the other to 'Instance Name', the rendered labels will differ.
What is the difference between an EPH and an RPH in SIMATIC BATCH?
An EPH (Equipment Phase) is the automation logic implemented in the AS controller (SFC Type). An RPH (Recipe Phase) is the corresponding recipe step in the BATCH Recipe Editor that issues setpoints and commands to the EPH.
Can I rename an EPH instance without invalidating approved recipes?
Renaming an EPH instance requires recompiling the BATCH process cell and updating the process cell in BatchCC. If recipes are unit-specific, they may require re-validation and re-release.
Where is the process cell model updated after changing SFC Type properties?
In SIMATIC Manager Plant View, right-click the Process Cell and select SIMATIC BATCH -> Compile / Download. Then in BatchCC, select Process Cell -> Update Process Cell.
Does changing display settings require an AS CPU stop?
No. Modifying UI display settings in BatchCC or the Recipe Editor is purely client-side and has zero impact on the running controller.
Technical References
- SIMATIC BATCH Operating Manual V9.0 SP1
- SIMATIC BATCH Engineering and Configuration Manual
- SIMATIC PCS 7 SFC for S7 Engineering Manual
Related Articles
- Propagating SFC Type Parameter Changes to SIMATIC BATCH and Updating Process Cell Data
- Managing Unit Allocation Conflicts and Chained Batches in SIMATIC BATCH
- Hardware Homogeneity and Synchronization Rules for Redundant WinCC OS Servers
Related Tags
- SIMATIC BATCH
- EPH
- Recipe Editor
- BatchCC
- SFC Type
- Process Cell