Replacing and Synchronizing Equipment Phase Types (EPHT) in the PCS 7 Master Data Library

In SIMATIC PCS 7 (V9.0 SP2 / V9.1), replacing an Equipment Phase Type (EPHT) in the Master Data Library with a type from another project must not be performed by simple deletion and pasting, as deleting an EPHT forces the deletion of all existing instances and destroys plant interconnections. To safely replace an EPHT, import the new version with a temporary name, verify that underlying SFC Type FB/FC numbers do not collide with local project blocks, reassign existing technological instances to the new type using the Technological List Editor or Process Object View, synchronize instances across the multiproject, and retire the obsolete type definition.

Executive Summary

In SIMATIC PCS 7 technological engineering, Equipment Phase Types (EPHT) and Equipment Module Types (EMT) provide reusable object-oriented structures that unite technological interfaces (TIO), CFC charts, and Sequential Function Chart (SFC) Types into coordinated procedural control entities. During plant lifecycle maintenance or project merges, automation engineers frequently need to replace an existing EPHT in the active multiproject's Master Data Library (MDL) with an updated or corrected version from another project archive.

Engineers attempting to delete the old EPHT in the library and paste the replacement face a catastrophic outcome: deleting an EPHT forces the deletion of all instantiated phases across the plant hierarchy, wiping out intricate signal interconnections. Conversely, simply overwriting the type can trigger severe internal compiler discrepancies where function block (FB) and function (FC) numbers collision occurs between the SFC Type and local project blocks. Because Siemens documentation does not outline a single automated 'Update EPHT' button, engineers require a validated, non-destructive migration workflow. This guide outlines the safe procedure to replace EPHTs while preserving all instance interconnections.

Architecture and Fundamental Mechanics

The architectural duality of Equipment Phase Types governs their lifecycle behavior across libraries and projects:

Composition of an EPHT / EMT:
- An EPHT is not a simple block; it is a composite technological container consisting of:
- Technological Interface Objects (TIO): Defines control strategy parameters, setpoints, and technological inputs/outputs.
- CFC Chart Logic: Encapsulates underlying drive/valve channel blocks and interlocks.
- SFC Type: Implements the state sequencer logic (e.g., RUN, HOLD, ABORT sequencers) and compiles into a dedicated S7 Function Block (FB).
The Master Data Library Synchronization Mechanism:
- In the Master Data Library, the EPHT resides in the 'Technological Types' folder, while its associated SFC Type and compiled FB reside in the 'SFC Types' and 'Blocks' folders.
- When an EPHT is instantiated in the Plant Hierarchy, Step 7 establishes persistent GUID (Globally Unique Identifier) references linking the instance to the type.
- If the type is deleted from the library, Step 7 marks all instances as orphaned. A subsequent 'Synchronize' or consistency check flags fatal integrity errors.
The FB/FC Number Collision Hazard:
- Each SFC Type is allocated an FB number (e.g., FB 1050).
- If the replacement EPHT from Project B uses an FB number that is already allocated to a different block in Project A, overwriting the type causes severe memory mapping errors in CPU execution.
- Reassigning instances via temporary versioning decouples the GUID transition, ensuring smooth migration.

Step-by-Step Implementation Procedure

Follow these steps to replace an Equipment Phase Type safely without destroying instances:

Archive Existing Multiproject:
- In SIMATIC Manager, select 'File > Archive...'. Create a full zip archive before proceeding.
Inspect and Align FB/FC Block Numbers:
- Open the source project (Project B) and the active target project (Project A).
- Check the FB number of the SFC Type inside the source EPHT (e.g., FB 1205).
- In Project A, open the block folder and ensure FB 1205 is either unassigned or represents the same SFC Type. If conflicting, renumber the SFC Type in Project B before export.
Import Replacement EPHT with a Temporary Name:
- In Project B, rename the EPHT and its associated SFC Type to a temporary versioned name (e.g., EPHT_Dosing_V2).
- Copy EPHT_Dosing_V2 from Project B's Master Data Library.
- Open Project A's Master Data Library and paste the new type into the 'Technological Types' folder.
- Ensure the associated SFC Type and FB are copied into the library's block folders.
Reassign Existing Instances to the New Type:
- In Project A, open the Process Object View ('View > Process Object View' or Ctrl + Alt + P).
- Switch to the 'Control Modules' or 'Technological Objects' tab.
- Select all existing instances currently bound to the obsolete EPHT.
- In the 'Type' column, reassign each instance from EPHT_Dosing to EPHT_Dosing_V2.
- Alternatively, open each instance's Technological List Editor and select 'Reassign Type'.
- Notice that all external signal interconnections to field valves, motors, and transmitters are preserved!
Synchronize Plant Hierarchy:
- In SIMATIC Manager Plant View, select the root plant hierarchy folder.
- Select 'Options > Plant Hierarchy > Synchronize...'.
- In the synchronization wizard, verify that all instances update to reflect the new parameters, setpoints, and sequencers of EPHT_Dosing_V2.
- Execute synchronization.
Retire Obsolete Type and Recompile:
- Once all instances successfully run under the new type, delete the old EPHT_Dosing from the Master Data Library.
- (Optional): Rename EPHT_Dosing_V2 back to EPHT_Dosing and execute a final synchronization.
- Compile CFC charts ('Entire program' with 'Generate module drivers').
- Download changes to the S7 controller in RUN mode.

Verification

In SIMATIC Manager Plant View, open an instantiated phase chart: confirm that the updated sequencer logic and technological parameters are present.
Verify that all external interconnections to field devices remain intact.
Execute 'Options > Plant Hierarchy > Check Consistency': confirm zero technological errors or orphaned type pointers.
Open the SFC Type in online test mode: verify that the sequencer advances through steps and executes batch commands correctly.

Limitations and Operational Precautions

Never delete an EPHT from the library while active instances exist in the project charts; doing so will invalidate all instances. Structural changes to SFC Type interfaces (adding/deleting characteristics or control strategies) require updating SIMATIC BATCH process cells. Verify engineering licenses and software options through an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

Why shouldn't I delete and replace an EPHT directly in the library?

Deleting an EPHT marks all plant instances as orphaned and forces their deletion, destroying all configured field interconnections.

What components make up an Equipment Phase Type (EPHT)?

An EPHT consists of a Technological Interface (TIO), a CFC chart, and an associated SFC Type with its compiled Function Block (FB).

How do I avoid FB/FC number collisions when copying an EPHT?

Check the FB number of the SFC Type in both projects and ensure no conflicting block exists in the target project block folder before copying.

What tool allows bulk reassignment of technological instances?

Process Object View (POV) or the Technological List Editor in SIMATIC Manager.

Does replacing an EPHT require stopping the controller?

If the interface changes allow delta download, changes can be downloaded in RUN mode; significant structural DB changes may require a CPU restart.

Technical References

Related Tags

EPHT
Master Data Library
SFC Type
Type-Instance Sync
Process Object View
PCS 7 V9.0 SP2

20 respuestas

Replacing and Synchronizing Equipment Phase Types (EPHT) in the PCS 7 Master Data Library