MaximaLabs
Power & steam

Power & steam cycles, built in

Rigorous IAPWS steam, a full steam-utility unit-op library, organic Rankine cycles and fuel-cell CHP — the power-cycle thermodynamics on one flowsheet you wire and solve.

Rigorous IAPWS-97 steam properties

Every steam number — superheat enthalpy, the isentropic-expansion endpoint, exhaust steam quality — is the real IAPWS-97 steam-table value, not a correlation, so a Rankine cycle's turbine work and wet-exhaust quality come out right.

A full steam-utility unit-op library

Boiler, steam turbine (including extraction / back-pressure), condenser, deaerator, desuperheater and a cooling-tower screen are real, wireable nodes on the canvas — the balance-of-plant a power or utilities flowsheet is actually built from, not a single black box.

Organic Rankine Cycle on a real fluid

Run a closed working-fluid loop (e.g. R245fa) for low-grade waste-heat recovery: a two-stream boiler vaporizes the fluid against a hot source, a real isentropic-efficiency turbine makes shaft power, and a condenser and pump close the loop — the whole cycle converges as one flowsheet.

Fuel cells & combined heat and power

A PEM fuel-cell CHP block couples the electrochemical conversion with cathode water management, so a combined-heat-and-power unit is modelled as part of the process, not bolted on — the modern-energy workflows a 2003-era simulator was never built for.

Back-work, efficiency & duties, solved

The pump back-work ratio, cycle thermal efficiency, condenser heat rejection and boiler fired duty are all solved quantities off the converged flowsheet — the numbers a heat-balance study reports, produced by the deterministic solver, never estimated.

One data model, cycle to report

A steam stream is the same object through the boiler, the turbine, the condenser and the report — so a whole power or cogeneration cycle is an ordinary flowsheet that conserves every kilogram of water and every joule, not three disconnected tools you reconcile by hand.

Worked power cycles, one click away

Three solved flowsheets you can open, run and edit — a classic pump → boiler → turbine → condenser steam Rankine cycle, an organic Rankine loop recovering marine-engine exhaust heat, and a PEM fuel-cell combined-heat-and-power unit.

Why this is different

A legacy stack treats the power island, the utilities and the process as separate models you stitch together by hand. Here the IAPWS steam, the steam-utility ops, the ORC loop and the fuel-cell block share one data model with the simulator, so a power or cogeneration cycle is an ordinary flowsheet — pressurize the feedwater, fire the boiler, expand the steam, reject to the condenser — that converges and closes every mass and energy balance, not a heat-balance spreadsheet you maintain alongside the model.

Honest by design

  • Steam properties are the rigorous IAPWS-97 formulation and the machines carry real isentropic/polytropic efficiencies, so turbine work, discharge state and wet-steam quality are genuine thermodynamic results.
  • The headline steam cycle is an open (once-through) representation with a single expansion — no reheat or feedwater regeneration — so its efficiency is the simple ideal-cycle figure, not a supercritical/reheat station's; the description states this.
  • The ORC boiler's cold-outlet is a fixed spec, so that showcase demonstrates cycle convergence and net power, not a pinch/approach-temperature heat-recovery-area design.
  • The cooling tower is a screening heat/water balance (evaporation + blowdown makeup), not a Merkel/psychrometric NTU model, and the steam turbine is dry/superheated-vapor (no wet-steam quality tracking through the machine).
  • The deterministic solver produces every duty, flow, temperature and efficiency; this layer supplies the steam/power thermodynamics — it never invents a process number.

From feedwater to net power in one model

Pick the IAPWS steam package, drop a boiler, turbine and condenser on the canvas, and solve the whole cycle — turbine work, back-work ratio and thermal efficiency read off the converged result.

Try it free

Stop fighting legacy software. Build your first flowsheet in 60 seconds.