Understanding the Propagate Types Function in SIMATIC BATCH Multiprojects

In SIMATIC BATCH Multiproject engineering, the "Propagate types" function acts as the cross-project synchronization mechanism that distributes central batch type definitions (phase types, operation types, equipment phases, and unit classes) from the master Multiproject catalog to every individual S7 subproject. While "Generate types" scans CFC charts to extract phase interfaces (IEPH, IEOP, EPH, EOP) and "Compile" builds the runtime batch database (SBX), "Propagate types" ensures that all distributed AS projects share uniform type descriptions, parameter structures, and unit data types. If block interfaces diverge between charts, the propagation routine automatically triggers a cross-chart comparison to resolve inconsistencies.

SIMATIC BATCH Multiproject Engineering Workflow

In modern batch process facilities, automation programs are rarely confined to a single PLC. A typical SIMATIC PCS 7 facility utilizes a Multiproject containing multiple independent S7 projects corresponding to discrete plant areas (e.g., Raw Materials AS, Reactor Train AS, Filtration AS, Tank Farm AS).

To execute recipes that coordinate equipment across multiple controllers, SIMATIC BATCH requires a unified, plant-wide type catalog. An Equipment Phase (EPH) or Unit Class defined in the master recipe must possess identical data structures, control strategies, setpoint types, and unit identifiers across every controller where it appears.

The Propagate types function is the architectural bridge that enforces this cross-project consistency.

Generate vs Propagate vs Compile Functions

To prevent engineering errors, engineers must understand the distinct roles of the three primary BATCH configuration commands:

Engineering ActionCommand Execution LocationPrimary Operational FunctionOutput ArtifactGenerate TypesSIMATIC Manager -> Target Project -> BATCHScans local CFC charts and block libraries; creates phase types from IEPH/IEOPProject Batch Type CatalogPropagate TypesMultiproject Level -> BATCH -> TypesDistributes unified batch types across all subprojects in the MultiprojectSynchronized Subproject CatalogsCompile BATCHBatch Control Center / SIMATIC ManagerCompiles validated types and instance data into the active recipe execution modelMaster Recipe Database (SBX / SQL)Update Block TypesSIMATIC Manager -> S7 Program -> ChartsPropagates updated function block definitions from library to chartsUpdated Block Instances

If an engineer creates a new equipment phase in Project A and compiles BATCH without running 'Propagate types', Project B will reject recipes referencing that phase type due to type definition absence.

What Occurs During the Propagate Types Execution

When an engineer clicks Propagate types in SIMATIC Manager:
1. Catalog Aggregation: The engineering system opens the batch type definitions across all projects participating in the Multiproject.
2. Master Type Merging: Type definitions, control strategy enumerations, setpoints, and phase parameter descriptors are merged into a master Multiproject type description.
3. Distribution to Subprojects: The updated master type catalog is written into each individual project database under <ProjectDir>\Batch\.
4. CFC Chart Synchronization Check: If the system detects that an existing block instance in a CFC chart possesses an outdated parameter interface compared to the propagated type, it automatically invokes a CFC chart comparison dialog, prompting the engineer to reconcile the parameter differences.

Resolving Type Conflicts and Chart Comparison Triggers

If 'Propagate types' halts with an error or triggers an unexpected chart comparison:
* Interface Signature Mismatch: An equipment phase block (e.g., EPH FB) in Project 1 has different input/output parameters than the same block in Project 2. Resolve this by copying the approved block from the Master Data Library into both projects and running Options -> Update Block Types....
* Enumeration Conflict: A control strategy enumeration value was modified in one project but retains the legacy name in another.
* Orphaned Phase Types: A phase type was deleted from CFC charts but remains referenced in the BATCH type catalog. Open the BATCH Type Editor, delete the orphaned phase type, and re-run propagation.

Verification

To verify successful type propagation across the Multiproject:
1. In SIMATIC Manager, select the top-level Multiproject folder.
2. Navigate to Options -> SIMATIC BATCH -> Propagate Types.
3. Verify that the propagation log concludes with: Type propagation completed successfully without errors.
4. Open the Batch Type Editor in each subproject; confirm that newly created phase types and parameters appear identically across all project trees.
5. Execute Compile BATCH; confirm that compilation succeeds without missing type references.

Limitations and Operational Precautions

Never execute 'Propagate types' while another engineer has an open CFC chart or BATCH dialog in one of the subprojects over a shared network. Concurrent multi-user file access can lock the type database, resulting in partial propagation and inconsistent project states. Always back up the Multiproject via File -> Archive before performing mass type propagation or library block updates.

Engineer FAQ

When must I run 'Propagate types'?

You must run 'Propagate types' whenever you add, modify, or delete a phase type, control strategy, unit class, or setpoint parameter in any subproject before compiling SIMATIC BATCH.

What happens if I compile BATCH without propagating types?

The BATCH compiler will report missing type descriptions or interface mismatches for any instances that reside in subprojects where types were not synchronized.

Does 'Propagate types' modify the running PLC program?

No. 'Propagate types' operates purely within the offline engineering database on the Engineering Station. It does not alter the online controller program until changes are downloaded.