Resolving Greyed Out SIMATIC BATCH Recipe Unit Procedures (RUP) in PCS 7 BatchCC (Permission Management & Equipment Allocation)

In SIMATIC BATCH (PCS 7 V8.1, V8.2, and V9.0), a Recipe Unit Procedure (RUP) appearing greyed out or inaccessible within the Batch Control Center (BatchCC) recipe editor is typically caused by insufficient user role permissions in BatchCC Permission Management or unallocated/unassigned equipment units in the Batch Plant Model. When a user account lacks the explicit functional permission 'Edit Recipes' or 'Release Recipes' for the specific plant unit assigned to that RUP, or if the underlying SFC type has not been properly allocated to the physical Unit in SIMATIC Manager and compiled into the Batch database, BatchCC renders the unit procedure inactive to prevent unauthorized process recipe modifications.

Architecture of Recipe Unit Procedures (RUP) in SIMATIC BATCH

SIMATIC BATCH conforms strictly to the ISA-88 (IEC 61512) batch control standard, structuring recipes into a hierarchical model comprising Hierarchical Recipes (Master Recipe > Recipe Unit Procedure [RUP] > Recipe Operation [ROP] > Recipe Phase [RPH]). A Recipe Unit Procedure represents the contiguous sequence of operational tasks performed within a single process unit (such as a Reactor, Dissolver, or Fermenter).

In Batch Control Center (BatchCC) and the BATCH Recipe Editor, each RUP is bound to an Equipment Unit defined in the PCS 7 Plant Hierarchy. The editor enforces rigorous operational constraints: an engineer can only insert, modify, or link operations within a RUP if both the physical unit allocation is valid and the operating user holds the requisite security privileges.

Root Cause Analysis: Why RUP Blocks Appear Greyed Out

When an automation engineer opens a master recipe and finds a newly configured RUP greyed out, shaded, or unresponsive to mouse clicks, the underlying root causes fall into two primary categories:

Permission Management Restrictions (User Rights): BatchCC features granular role-based security. Permissions can be assigned globally or restricted on a per-unit basis. If the logged-in SIMATIC Logon user belongs to a role that has not been granted 'Edit Recipe' or 'Unit Allocation' rights for that specific Unit, BatchCC greys out the RUP while allowing other parts of the recipe to be viewed.
Missing Unit Equipment Allocation: A RUP cannot exist in isolation; it must be assigned to an equipment unit class or a specific unit instance. If the underlying SFC Type or SFC instance is not assigned to the unit folder in the Plant Hierarchy, or if the unit allocation in the RUP header properties is unassigned, the recipe compiler disables the procedure.
Recipe Release Status: If the recipe is in state 'Released' or 'Validation in Progress', all RUP elements are locked against editing until the recipe is revoked to 'Draft' status.

Configuring BatchCC User Permissions and Role Assignments

To resolve permission-related greyed out RUPs, follow these configuration steps in BatchCC:

Open Batch Control Center (BatchCC) on the Engineering Station or BATCH Server.
Navigate to menu Options > Permission Management (requires administrative logon).
In the Permission Management dialog, select the User Roles tab (e.g., Recipe_Author, Plant_Engineer, Batch_Operator).
Select the target user role, expand the Units permission subtree, and ensure that the specific unit hosting the RUP (e.g., Reactor_01) is checked.
Under Single Permissions, verify that the following rights are explicitly granted:
- Edit recipe
- Release recipe for testing / production
- Allocate units
Click Apply and OK. Have the operator log out and log back into BatchCC via SIMATIC Logon to refresh security tokens.

Equipment Hierarchy and Unit Allocation in the Batch Plant Model

If permissions are verified but the RUP remains inactive, verify the equipment model synchronization between SIMATIC Manager and SIMATIC BATCH:

In SIMATIC Manager Plant Hierarchy, verify that the unit folder containing the target SFC types has the Unit attribute checked in folder properties.
Confirm that each Phase / SFC Type possesses the system attribute S7_m_c := true and is assigned to the corresponding unit.
In SIMATIC Manager, highlight the BATCH application and select PLC > Compile and Download Objects > SIMATIC BATCH.
Open BatchCC, select menu System > Update Plant Model, and confirm that the synchronization finishes without discrepancy warnings.
In the Recipe Editor, open the RUP properties; verify that the 'Unit Selection' dropdown correctly displays and selects the newly synchronized unit.

Comparison of Batch Recipe Hierarchy Elements

The following table compares the hierarchical elements defined in SIMATIC BATCH and their association with PCS 7 physical equipment:

ISA-88 Recipe ElementSIMATIC BATCH ContainerAssociated Physical EquipmentTypical Engineering EntityMaster RecipeTop-Level Recipe FileEntire Plant / Process AreaGlobal multi-unit sequenceRecipe Unit Procedure (RUP)Unit Block in RecipeSpecific Unit (Reactor, Tank)Dedicated Unit ContainerRecipe Operation (ROP)Operation ContainerUnit SubsystemDosing, Agitating, HeatingRecipe Phase (RPH)Discrete Action StepEquipment Phase / Control ModuleSFC Type / EPH InstanceTransitionStep Transition ConditionProcess Sensor FeedbackLogic comparisons (Temp > 80°C)

Verification

Verify that the Recipe Unit Procedure has returned to active, editable status:
1. In BatchCC, open the Master Recipe containing the previously greyed out RUP.
2. Confirm that the RUP graphic block displays full color saturation and that the procedure label is readable.
3. Double-click the RUP block; verify that the RUP editor opens, allowing insertion of Recipe Operations (ROP) and Recipe Phases (RPH).
4. Add a test phase, save the recipe, and execute Recipe > Validate; confirm that the recipe passes validation with 0 errors.

Limitations and Operational Precautions

Never modify BatchCC permissions or role assignments while an active production batch is executing inside the affected unit, as security token updates can momentarily block operator intervention commands. Always establish a clear distinction between recipe authors and recipe approvers in accordance with FDA 21 CFR Part 11 guidelines: an engineer who creates or edits a RUP should not possess solitary rights to release the master recipe to production.

Engineer FAQ

Why does the SFC run fine manually outside of BATCH, but the RUP is disabled in BATCH?

Manual SFC execution in CFC only tests the controller logic and Step 7 communication. SIMATIC BATCH introduces an additional security and allocation layer: if the unit is not assigned to the user role in BatchCC Permission Management, BATCH disables the RUP even though the PLC logic is healthy.

Where do I find Permission Management in BatchCC?

In Batch Control Center, select menu 'Options > Permission Management'. You must be logged in as a member of the local Windows SIMATIC BATCH Administrator group to view and modify these settings.

What should I do if the unit dropdown in the RUP properties is empty?

An empty unit dropdown means the Batch Plant Model has not been synchronized with SIMATIC Manager. In SIMATIC Manager, compile the SIMATIC BATCH application, open BatchCC, and select 'System > Update Plant Model'.