SIMULATORS

Optimization Design Modules

Optimization design modules are ChemAgent's value-added engineering capability. For a supported column type, a purpose-built calculation module returns an optimized design option in seconds; the engineer reviews and approves it, and the approved conditions carry straight into Aspen flowsheet creation in the same conversation.

Available modules

ModuleStatus
DepropanizerReference workflow, documented on this page
DeethanizerDelivered and enabled as an independent module
DebutanizerDelivered and enabled as an independent module
Delivered per module

Each column type is an independent module with its own switch in the console skills page: a deployment enables exactly the modules it has licensed, and the module list grows with the product. Using one module in a session does not block another session from using a different module.

The depropanizer workflow

  1. 1
    State the design basis

    Give the feed composition, operating pressure, product specifications, and constraints in plain language in the chat.

  2. 2
    Run the module

    The agent fills in the module's input template, validates it, and runs the calculation. A full optimization round typically completes in seconds, so alternatives are cheap to explore.

  3. 3
    Review the engineering summary

    The module returns a compact engineering summary of the recommended design; the complete result set is saved to the workspace for inspection.

  4. 4
    Approve the handoff

    Only after the engineer approves the option do its conditions flow into Aspen flowsheet creation, where the standard modelling discipline applies.

Boundaries

  • Input protection

    Unknown fields and malformed values are rejected before the calculation runs.

  • The module proposes, the engineer decides

    A module result is a design option, not a decision; assumptions, applicability, and the selected operating point remain the engineer's call.

  • Traceable results

    Calculation inputs and outputs are kept in the workspace, so a design decision can be traced back to the exact run behind it.

Scope

Workflow description only

Calculation methods, model internals, and interface details are not published. Module availability and the supported column list follow the commercial delivery scope.