neqsim-process-modeling

NeqSim Process Modeling Skill

Build executable NeqSim process simulations from engineering descriptions. This skill is the process-flowsheet layer between thermodynamic fluid setup and downstream specialists such as mechanical design, safety, plant data, and reporting.

Use When

• Building a ProcessSystem or ProcessModel flowsheet from a process description.
• Connecting equipment such as streams, separators, compressors, coolers, heaters, heat exchangers, pumps, valves, pipes, mixers, splitters, recycles, adjusters, and distillation columns.
• Extracting process results with units, compositions, duties, powers, phase splits, mass balances, energy balances, or equipment profiles.
• Preparing a steady-state process base case for mechanical design, relief sizing, flow assurance, dynamic simulation, plant-data comparison, or optimization.

Core Workflow

1. Agree the model basis: engineering question, battery limits, feed/assay, units, product specifications, data provenance and required fidelity. Follow model-build-contract for every new or revised flowsheet; use its handoff checklist when another agent consumes it.
2. Select the task pattern from oil-and-gas-task-patterns. Load only the relevant specialist skills. Discover additional capabilities rather than treating an equipment class name as proof of a validated application.
3. Define fluids and feeds with the EOS/component sequence in neqsim-api-patterns. Verify the EOS and phase options for the composition, pressure/temperature range and property being calculated.
4. Assemble a reusable builder with named streams/equipment, live outlet connections, explicit terminal products and one ProcessSystem per area. Return the process/plant and stream/equipment registries, not just numbers.
5. Solve progressively: establish the feed and once-through base case, close physical recycles, then add adjusters and operating constraints. Use makeRecycles() or setAutoRecycles(true) for supported mixer/manifold loops. For coupled models, check the boolean from runUntilConverged(n) and retain residual/iteration evidence. A returned run() call is not convergence proof.
6. Validate each accepted case: external total/component balances, energy closure where heat/work matters, phase identity, feasible equipment limits, independent benchmark and repeat/nearby-point behavior. Missing evidence stays incomplete; never insert zero as a closure result.
7. Deliver reusable outputs with explicit units, inputs, version, assumptions, data gaps, failed cases and validation evidence. Store notebooks/scripts in the task folder; publish sanitized examples only when requested.