Managing Recipe Operation (ROP) Status Changes and Continuous Phase Transitions During SIMATIC BATCH Upgrades

When upgrading SIMATIC BATCH from legacy versions (v6.1 or v7.0) to modern versions (v8.0, v8.1, or higher), the status propagation behavior of Recipe Operations (ROP) containing continuous running Recipe Phases (RF) changed to strictly adhere to ISA-88 hierarchical state models. In older releases, an ROP would transition to 'Completed' (Beendet) while a child continuous phase continued running. In v8.0 and higher, the parent ROP remains in the 'Running / Continuous' state until all embedded phases terminate. Consequently, recipe transitions evaluating 'ROP Status == Completed' will never trigger. To resolve this without rewriting thousands of validated recipes, configure continuous phase status propagation in BATCH project settings or decouple continuous phases to asynchronous parallel branches.

ISA-88 State Model Transition in SIMATIC BATCH v8.0 and Higher

In the ANSI/ISA-88 standard, recipe state machines operate strictly hierarchically: Recipe Procedure -> Recipe Unit Procedure (RUP) -> Recipe Operation (ROP) -> Recipe Phase (RF).

Between SIMATIC BATCH V7.x and V8.0/V8.1, Siemens implemented a major architectural alignment with the international standard:
* Legacy Behavior (BATCH v6.1 / v7.0): When a continuous phase (such as a continuous agitator or background cooling phase) was executed within an ROP, the parent ROP would flag Completed as soon as the sequence traversed past the step, allowing downstream transitions to fire while the phase continued running in the background.
* Modern Behavior (BATCH v8.0 / v8.1 / v9.x): According to strict ISA-88 logic, a parent operational entity cannot be considered 'Completed' if one of its child technological functions is still actively executing. The ROP remains in Continuous / Running status until the continuous phase is explicitly terminated by another recipe step.

Root Causes of Transition Deadlocks in Migrated Recipes

When a facility upgrades its PCS 7 and SIMATIC BATCH installation:
1. Transition Condition Failure: Recipes engineered in v6/v7 frequently utilize step transitions that query the parent ROP status: IF ROP_1.Status == Completed THEN Step_2. Because the ROP never enters the Completed state, the transition condition permanently evaluates to FALSE, deadlocking the batch execution.
2. Mass Recipe Incompatibility: In mature pharmaceutical or specialty chemical plants with hundreds or thousands of validated master recipes, modifying every recipe transition represents an immense regulatory and engineering burden.
3. SFC Type / IEPH Block State Mismatch: Custom logic between the AS controller SFC block and the BATCH interface block (IEPH / IEOP) attempting to force a completion state causes communication handshake timeouts with the BATCH Control Server.

Remediation Strategies - Project Settings and Recipe Decoupling

To resolve transition deadlocks following a BATCH version upgrade:

[Strategy 1: Configure BATCH Project Settings Compatibility (Recommended)]
   │  • Open BATCH Control Center (BCC) -> System -> "Project Settings"
   │  • Navigate to the "Recipe processing" or "State propagation" tab
   │  • Locate setting: "Status propagation of continuous phases"
   │  • Select legacy compatibility mode:
   │      [x] "Allow ROP completion with active continuous phase"
   │  • Update Process Cell data and restart BATCH Control Server
   │
[Strategy 2: Decouple Continuous Phases to Asynchronous Parallel Branches]
   │  • If compatibility mode is unavailable or non-compliant:
   │  • In BATCH Recipe Editor, separate continuous phases into a dedicated parallel branch:
   │      - Branch A: Starts continuous phase (e.g. Agitation)
   │      - Branch B: Executes sequential process operations (Heating, Dosing)
   │      - Converge branches only when the continuous phase is explicitly stopped
   │
[Strategy 3: Adapt SFC Type Interface Properties]
   │  • In SIMATIC Manager: Open the SFC Type in Master Data Library
   │  • In Characteristics -> "Operating Principle":
   │      Verify if phase is declared as "Continuous" or "Non-continuous"
   │  • Compile and transfer Process Cell data to synchronize state words

SIMATIC BATCH Version Behavior and State Propagation Matrix

Compare state propagation behavior across SIMATIC BATCH releases:

Feature / BehaviorSIMATIC BATCH v6.1 / v7.0SIMATIC BATCH v8.0 / v8.1 / v9.xISA-88 CompliancePermissive state propagationStrict ISA-88 hierarchical enforcementROP Status with Active RFTransitions to Completed (Beendet)Remains in Continuous / Running (Weiterlaufen)Transition ROP == CompletedFires immediately upon sequence exitFails to fire (Deadlock)Parallel Branch DecouplingOptionalRecommended design best practiceSFC Interface BlocksClassic EPH / EOP blocksStandardized IEPH / IEOP APL interface

Verification

To confirm that recipe operations transition properly after upgrading:
1. In BATCH Control Center, launch a test batch utilizing the migrated master recipe with continuous phases.
2. Observe the batch execution view in BCC; confirm that the step sequence progresses past the ROP containing the continuous phase.
3. Verify that downstream transitions evaluate to TRUE without operator manual stepping.
4. Verify on the SFC Visualization faceplate in WinCC that the continuous phase remains running in the background.
5. Confirm that the final recipe terminating step commands the continuous phase to stop, allowing the batch to complete cleanly.

Limitations and Operational Precautions

Never implement non-standard 'trick' logic in CFC between the SFC block and the IEPH block to fake a completed state. Faking state words can desynchronize the BATCH Server and AS controller, resulting in unacknowledged batch step hangs or orphaned running equipment in the field. Always validate recipe timing and interlock behavior in an offline SIMIT simulation environment before running on live production vessels.

Engineer FAQ

Why did Siemens change the ROP status behavior in BATCH V8.0?

To enforce strict alignment with ANSI/ISA-88 standards and eliminate ambiguous state conditions where a parent operation was marked completed while its physical process equipment was still running.

What does the 'Continuous' (Weiterlaufend) setting do on an SFC Type?

It designates that the technological phase is designed to run across multiple recipe operations without being reset or terminated when the originating operation finishes.

Can I revert this behavior globally in SIMATIC BATCH V8.1?

Yes, depending on the specific update installed, BATCH project settings provide a compatibility flag for legacy state propagation.

What block links the AS controller SFC sequence to SIMATIC BATCH?

The IEPH (Interface Equipment Phase) or IEOP (Interface Equipment Operation) block from the PCS 7 BATCH Library.

Technical References

Related Tags

SIMATIC BATCH
ROP Status
Continuous Phase
ISA-88
Batch Migration

6 respuestas

Managing Recipe Operation (ROP) Status Changes and Continuous Phase Transitions During SIMATIC BATCH Upgrades