Engineering Computation
Deterministic Tools. Typed Interfaces.
MCP servers wrap peer-reviewed open-source engines and expose them as typed, auditable tools. Every input is validated. Every output is structured. Every call is logged.
How Engineering Computation Works in PuranOS
In most engineering firms, simulation models live in notebooks, Excel spreadsheets, or desktop applications disconnected from project state. An engineer runs a model, copies results into a report, and the model becomes stale the moment project parameters change.
PuranOS treats engineering computation differently. Each engine is API-first (not GUI-first), session-persistent across agent interactions, and produces results with explicit credibility metadata.
Agents don't interact with these tools through a chat interface. They are triggered by OpenProject task assignments, scheduled automation, or inbound emails — and they call engineering tools as part of structured skill execution.
Core Engineering Engines
QSDsan
University of Illinois · Biological and chemical treatment
Mass/energy balance, process simulation, LCA. IWA ADM1, ASM1, ASM2d models. Session-persistent simulations with model credibility metadata on every result.
WaterTAP
NAWI / DOE · Membrane and separation processes
Desalination, advanced treatment, costing. RO, NF, ED, crystallizer, evaporator. Cross-engine handoffs from QSDsan via typed converters with provenance tracking.
PHREEQC
USGS · Chemical equilibrium
Precipitation, dosing optimization, scaling potential analysis. Multi-database support (phreeqc.dat, minteq.dat, llnl.dat, pitzer.dat).
CoolProp + fluids
Open source · Fluid mechanics
120+ fluid properties, pipe sizing, pump TDH, control valve sizing (IEC 60534), blower power calculations.
Cross-Engine Handoffs
A QSDsan effluent composition becomes a WaterTAP influent specification through typed converters — with unit conversion, component mapping, and provenance from the source model.
Multiple component bases are supported (mASM2d for activated sludge, MCAS for WaterTAP solutes, mADM1 for anaerobic models) with typed converters between them. The handoff is not a copy-paste — it carries the full lineage of how the data was produced.
Model Credibility Metadata
An agent-generated sizing is not automatically "engineering grade." Every simulation result carries explicit credibility metadata:
Model status
validated · calibrated · heuristic · preliminary · stub
Decision grade
design · budgetary · screening · order-of-magnitude
Validation basis
bench-tested · plant-data · literature · vendor · assumed
The credibility metadata is what allows a PE reviewer to know what level of trust to place in a result.
These engines are open-source. The MCP server wrappers and architecture are documented on GitHub.