SIMULATORS

Aspen Plus Toolchain

The Aspen Plus toolkit lets the agent drive a locally installed Aspen Plus directly: connect or create a file, define components and property methods, build unit operations, connect streams, run the case, and read the results — 32 tools in total.

Prerequisites

RequirementDetail
Operating systemWindows (the simulator is driven through its Windows automation interface)
Aspen PlusInstalled locally and able to open normally; V12.1 is the tested reference, other versions are assessed at delivery
Computation componentsLicensed calculation components delivered with the product; when absent the toolkit simply does not register and everything else keeps working

Tool families

FamilyWhat the tools cover
SessionConnect to or create a simulation file, save, close, and summarize the current session
Components and propertiesAdd or remove components and configure the property method
StreamsCreate streams and set feed conditions and composition
Distillation columnsBuild a column, connect feed, overhead, and bottoms, and manage column specifications
Heat exchangersCreate heaters and exchangers and connect their inlet and outlet streams
PumpsCreate pumps and connect their streams
Run and resultsRun the case to convergence, read column and stream results, and remove blocks
32 tools, visible in the console

The complete tool list is shown in the console skills page under the Aspen Plus group, with a description and switch on every tool card. This page describes families only; exact availability depends on the deployment.

Stability safeguards

SafeguardWhat it does
Dialog suppressionModal simulator dialogs are suppressed after connecting, so a run never stalls waiting for someone to click a popup
Crash-dialog watchdogKnown simulator crash popups are detected and dismissed automatically and the session continues, with the event recorded in the tool result
Post-connect settlingA short settle after connecting avoids simulator initialization races
Exclusive session ownershipFirst-come ownership prevents concurrent sessions from corrupting one model
Lazy connectionStarting or restarting the console never touches the simulator; connection happens only when a tool is actually called

Modelling discipline

  • Confirm before changing

    In Build mode the agent asks before changing model structure or overwriting an existing file.

  • Report convergence

    After every run the agent reports convergence status and the key results.

  • Source every parameter

    Every parameter written into the model is labelled with its source: specified by the user, taken from the knowledge base, or a simulator default.

Scope

Workflow description only

This page describes behaviour and boundaries. Internal interfaces, computation-component details, and tool implementations are not published.