AseptSoft Core Documentation
AseptSoft Core Documentation
Breadcrumbs

Build Condition Field

The Condition Builder is a guided, click-based interface that helps you construct formal condition expressions without manually typing formulas. It is used to populate the Condition field in Algorithm Design.

:gear: Overview

A condition expression defines what must be true before the process can advance to the next step. In pharmaceutical manufacturing, conditions are the safety and quality gates that ensure critical process parameters are met before proceeding.

A condition expression typically follows the pattern:

Instrument(s) Operator Parameter/Variable

For example: PIT_01 >= MaxPressure or TIT_01, TIT_02 >= MinTemp

The Condition Builder lets you construct these expressions by clicking items rather than typing.

:desktop_computer: Window Layout

The Condition Builder window is divided into five areas:

Area

Purpose

Selection Area

Click to select Instruments, an Operator, and a Parameter or Variable

Edit Area

Three text boxes showing current selections — editable for custom values

Logical Operators

AND, OR, XOR buttons to combine multiple atomic formulas

Final Formula

Live preview of the complete expression being built

Commit Area

"Insert Condition" to apply, or "Cancel" to abort

:footprints: How to Use

Building a Simple Condition

Step

Action

Result

1

Click one or more Instruments in the Selection Area

Instruments appear in the first Edit box (e.g., PIT_01)

2

Click an Operator (=, >, <, >=, <=, etc.)

Operator appears in the second Edit box

3

Click a Parameter or Variable

Value appears in the third Edit box

4

Review the Final Formula at the bottom

Shows the complete expression (e.g., PIT_01 >= MaxPressure)

5

Click "Insert Condition"

The expression is inserted into the condition field

Note: You can select multiple Instruments at once, but only one Parameter or Variable at a time.

Using Custom Values

Instead of clicking items in the Selection Area, you can type directly in the Edit Area text boxes. This is useful when you want to use a static value instead of a module data reference.

Example: Instead of selecting a variable, type 25l directly in the third text box to create PIT_01 >= 25l.

Building Complex Formulas

To combine multiple conditions with logical operators:

Step

Action

1

Build your first atomic formula (e.g., PIT_01 >= MaxPressure)

2

Click AND, OR, or XOR in the Logical Operators area

3

The first formula is saved, and the Selection/Edit Areas reset

4

Build your second atomic formula (e.g., TIT_01 >= MinTemp)

5

The Final Formula shows the combined result: (PIT_01 >= MaxPressure) AND (TIT_01 >= MinTemp)

Tip: Parentheses are added automatically when using logical operators. Uncheck the parentheses checkbox next to the operators if you want to disable automatic parentheses.

:test_tube: Pharma Example Walkthrough

Scenario: You are configuring a SIP (Steam-in-Place) sterilization step. Before steam can be introduced, the system must verify that the CIP rinse temperature has reached a safe threshold and that the hold timer has elapsed.

  1. Select instrument TIT_CIP_RINSE (the CIP rinse temperature transmitter)

  2. Select operator >=

  3. Select parameter MinRinseTemp (e.g., 85 °C)

  4. Click AND

  5. Select instrument TIMER_HOLD_01 (the CIP hold timer)

  6. Select operator >=

  7. Select parameter MinHoldTime (e.g., 300 seconds)

  8. Final formula reads: (TIT_CIP_RINSE >= MinRinseTemp) AND (TIMER_HOLD_01 >= MinHoldTime)

  9. Click "Insert Condition"

This condition ensures both the temperature and the timer thresholds are satisfied before the process transitions from CIP rinsing to the SIP sterilization phase — a critical safety gate in pharmaceutical production.

:bulb: Tips

  • The Final Formula area is also directly editable — you can make manual adjustments at any time

  • You can always return to the Selection Area to modify your picks

  • Multiple instruments in one formula create a comma-separated list (e.g., TIT_01, TIT_02 >= MinTemp)

  • Conditions are part of the Algorithm Design workflow — they control the transitions between steps in the SFC Editor