Module Data

Module Data is the collection of all data definitions within a Module. These definitions are shared across all Processes and Steps within the module, and form the foundation for your process data model.

💡 Think of Module Data as the vocabulary of your process. Before you can design a CIP sequence or define an SFC algorithm, you need to tell AseptSoft what states your valves can be in, what fluids flow through your pipes, what parameters to monitor, and what alarms to watch. Module Data is where all of that is defined.

🗂️ Data Types at a Glance

Module Data is organized into categories. Each data type serves a specific role in your process design:

🔄 States and Fluids

📊 Parameters and Variables

⚙️ Process Automation

🏭 Equipment

🧩 Process and Algorithm Design

🏭 Pharma Industry Context

In a typical biotech or pharmaceutical facility, your Module Data might include:

📖 How To: Set Up Module Data for a New Process

Follow these steps to build out the data model for a new module (for example, a CIP skid):

1. Define your Fluids — Start by creating entries for every fluid that will flow through the system (WFI, CIP Acid, CIP Caustic, Steam, etc.). Assign each a distinct color and priority. See Fluid.

2. Define your States — Create the valve states your process needs (Open, Closed, Partial, etc.) and set the fluid response for each. See State.

3. Create Parameters and Variables — Add the numeric thresholds your conditions will check (MaxTemp, MinPressure) and the storage variables your actions will write to (RecordedTemp, BatchVolume). See Parameter and Variable.

4. Set up Equipment Modules — Group related valves and instruments into functional units with configuration templates. See Equipment Module.

5. Create Dialogs — Define operator prompts for confirmations, data entry, and decision points. See Dialog.

6. Define Alarms and Interlocks — Add monitoring conditions and safety protection logic. See Alarm and Interlock.

7. Set up Control Loops — Define PID strategies for continuous process variable regulation. See Control Loop.

8. Design Processes and Algorithms — Finally, create your processes with steps and define the transition logic. See Process Design and Algorithm Design.

🔧 How to Access

Open the Module Data window from the Data panel in the Module Ribbon. The window organizes all data types into tabs for easy navigation.

🔄 States and Fluids — Overview

States define what condition an Engineering Item (valve, pump, instrument, etc.) can be in. Each state has a name, color, and fluid response that determines how it affects fluid flow.

Fluids define the types of fluids that flow through the piping system. Each fluid has a name, color, aggregation (Liquid or Gas), priority, and flow direction.

💡 States and Fluids work together: when a valve is set to an "Open" state with a fluid response of "Allow fluid to pass", the fluid flows through. When set to "Closed" with "Block fluid", flow is stopped.

📊 Parameters and Variables — Overview

Parameters are named values used in condition expressions — they represent thresholds, targets, and limits that the control logic checks against.

Variables are named storage values used in action expressions — they represent calculated values, counters, and recorded measurements.

⚙️ Process Automation — Overview

💬 Dialogs

Dialogs are reusable operator interaction templates. They prompt the operator with a message and collect a response — such as a whole number, a decimal value, a yes/no answer, free text, a button selection, a confirmation, a continue-or-abort decision, or a continue-or-restart decision. Dialogs can contain buttons and input controls (checkboxes, radio buttons, text fields, numeric inputs, and decimal inputs).

🚨 Alarms

Alarms define monitoring conditions with limit types (High-High, High, Low, Low-Low, or Discrete on/off), setpoints, priority (Critical to Diagnostic), severity (Emergency to Log Only), classification, acknowledgement rules, shelving rules, routing flags, and return-to-normal behavior.

🛡️ Interlocks

Interlocks define safety protection logic following ISA-88 standards. They include scope, type (Command permissive, Runtime hold, Trip/Abort, Transition permissive, Mode exclusivity, Lineup proof, Instrument health check, Quality gate, or Bypass rule), effect (Inhibit command, Force hold, Force abort, Block transition, Inhibit mode change, or Force stop), cause conditions, safe actions, latching/reset policies, bypass policies, and notification flags.

🔁 Control Loops

Control Loops define PID control strategies with pattern (Basic PID, Cascade, Ratio, Split Range, Override, or On/Off), criticality, process variable configuration, setpoint sources, controller tuning, output limits, final control elements, mode handling, failure behavior, and phase interaction.

🔧 Equipment Modules — Overview

Equipment Modules group related Engineering Items into reusable functional units using a template-based system:

1. Configuration Template — defines item slots (which valves/instruments belong to the group)

2. Configurations — named instances of the template (e.g., "Path A", "Path B", "Path C")

3. Configuration Items — the actual valve/instrument assignments within each configuration

🏭 Equipment Modules are typically used for transfer paths, CIP manifolds, and other groups of equipment that operate together.

🛠️ Common Operations

🔗 Related Pages

• Module Ribbon — Access Module Data from the Data panel

• AseptSoft Project Structure — How modules relate to projects and P&IDs

• Algorithm Design — How Module Data is used in condition logic

• Process Design — How to create processes and steps

• Export / Import — Excel and other export options