Make New SFC Type Control Strategies Available in SIMATIC BATCH

For the reported PCS 7 V9.0 SP3 and SIMATIC BATCH V9.0 SP1 Update 5 project, enabling a strategy in an SFC type is only the configuration change. The type and OS changes must be compiled, then the Batch configuration updated using the release-appropriate Generate, Propagate, Merge, and process-cell download workflow. If the strategy remains absent, first confirm the edited SFC type is the one used by the equipment module and that the full Batch configuration chain completed.

Confirm the source SFC type

Open the SFC type used by the affected equipment phase and verify that the new control strategies are enabled in its properties. Check whether the project uses a master-library copy or a project-library copy and ensure that the instance references the edited type.

Compile AS and OS changes

Compile the affected AS changes and download them according to the project's approved procedure. Compile the corresponding OS changes where required. Keep the project's compile scope and runtime status consistent with the applicable PCS 7 V9.0 SP3 instructions.

Update SIMATIC BATCH configuration

The Siemens SIMATIC BATCH V9.0 Getting Started guide describes the following sequence after AS/OS changes: open the Batch configuration dialog, generate Batch types, propagate the types, merge Batch instances, and download the process cell. Run the operations for the affected process cell and review any reported inconsistencies before continuing.

Verification

Open the affected Batch instance and inspect its selectable control strategies. Confirm the newly configured strategy is available for the intended equipment phase, then validate its behavior in an approved test environment before production use. A successful compile does not by itself prove the Batch instance was regenerated or updated.

Limitations and Operational Precautions

The report's screenshots are unavailable, and it does not identify the SFC type name, library, equipment module, or Batch configuration state. The sequence is tied to the cited SIMATIC BATCH V9.0 guide; verify exact menu labels and download requirements for V9.0 SP1 Update 5. Protect current project and process-cell data before broad Batch updates.

Technical References

Siemens, SIMATIC BATCH V9.0 Getting Started, section 6.6, “Compiling and Downloading AS, OS, and Batch”: https://cache.industry.siemens.com/dl/files/909/109781909/att_1032032/v1/sb_gs1_b_en-US.pdf
Siemens, Learn/Training Document PA Module P03-03, Batch control with recipes for PCS 7 V9: https://www.automation.siemens.com/sce-static/learning-training-documents/pcs7/v9-0/p03-03-batch-control-with-recipes-v9-tud-0719-en.pdf

Related Tags

Engineer FAQ

Where are SFC type control strategies selected? In the ticket's PCS 7 V9.0 SP3 workflow, the SFC type properties contain the control-strategy selections; confirm the edited type and library used by the equipment module.

What follows an SFC type strategy change? Siemens SIMATIC BATCH V9.0 Getting Started describes compiling/loading AS changes, compiling OS changes, and then generating/propagating batch types, merging instances, and downloading the process cell.

Why do strategies remain absent after enabling them? The source reports this symptom but does not identify the specific configuration defect; check that changes are on the instantiated type/library and that the required compile and Batch generation chain completed.

Does AS download alone update Batch instances? No. The V9.0 guide separates AS/OS compilation from Batch type generation, propagation, instance merge, and process-cell download.

What is the purpose of Propagate? The documented getting-started flow uses Propagate for Batch types; apply it after generating types and in the sequence documented for that release.

Should I use a full or delta compile? Use the compile scope appropriate to the project changes and applicable PCS 7/BATCH instructions; the discussion's suggestion is not a universal compile rule.

Can Batch run during the update? The Siemens guide notes the runtime OS must be deactivated for its specific PLCSIM training sequence; production runtime requirements depend on the actual change and project procedure.

How do I confirm the strategy is available? After the batch configuration and download sequence, inspect the relevant Batch instance and its selectable control-strategy list, then validate the intended equipment phase.

Does this article guarantee a fix for every missing strategy? No. The attachment and project details are unavailable, so the cause may depend on SFC type, library, equipment module, and Batch configuration.

What version applies to the report? The reported configuration is PCS 7 V9.0 SP3 with SIMATIC BATCH V9.0 SP1 Update 5; do not infer behavior for other releases.

Make New SFC Type Control Strategies Available in SIMATIC BATCH