Getting Actually Useful With This Thing
I still use Engineering Equation Solver every week for thermodynamics assignments and heat exchanger calculations. It is not complicated. It is also not particularly polished. The interface looks like it was frozen around 2003 and nobody bothered to thaw it. That does not mean it is bad. The numerical solver underneath is genuinely solid, and for anyone who has spent more time than they would like manually iterating energy balances, this saves hours. The basic workflow is straightforward enough that you can get a simple system running in about ten minutes. You open the program, type equations into the main editor window just the way you would write them on paper, assign units to each variable if you want, and hit Solve. It handles simultaneous nonlinear equations without you having to set up a Jacobian or worry about initial guesses for every single variable. Most other tools require you to reformat equations before the solver will touch them. EES does not. Here is a realistic example that came up recently for me. I was calculating the efficiency of a Rankine cycle with reheat and an open feedwater heater. That is six to eight simultaneous equations involving steam table lookups, enthalpy balances, and mass fractions. I set up the equations in about twelve minutes, defined the pressure and temperature boundaries, and hit solve. The program returned all the state properties and the cycle efficiency in roughly three seconds. Doing this by hand or even in a spreadsheet with iterative guess cells would take me at least forty minutes, and I would probably make a rounding error somewhere along the way.
Engineering Equation Solver Ees Software
When people ask where to get it, the official source is EES Software LLC. They offer a full version and an educational version with a couple of restrictions. The full license runs around a few hundred dollars for academic use, though prices shift. There is no free full version, and anyone selling cracked copies is handing you malware or a broken install. Buy the license from the official site and install it on one machine. The educational version is perfectly adequate for coursework and will run everything except some of the advanced parametric and optimization features. The thing most beginners miss is how aggressively EES enforces unit consistency. If you define temperature in Kelvin and then accidentally reference it in Celsius somewhere else in the same equation, EES will flag it. This is not a suggestion. It is a hard stop. I used to ignore this until I was debugging a psychrometrics problem where my humidity ratio was returning garbage values because I had mixed absolute and relative references without realizing it. The unit manager caught it immediately. Once you stop fighting the unit system and just let it work, it becomes one of the best features in the program. Another thing that is not obvious: the built-in property routines are actually very good. Steam, air, refrigerants, combustion products — they are all there. You call them by name. For water you type P=1e6[T=450] and EES interpolates from the IAPWS-IF97 formulation. You do not need an external table or a lookup function. This cuts out an entire category of errors that I used to introduce by manually copying values from steam tables into spreadsheets.
Here is where people run into real trouble. Parametric tables. I spent an afternoon once trying to generate a parametric study where I swept condenser pressure from 5 kPa to 15 kPa and watched the cycle efficiency change. The table generated, but the results were wrong because I had not set the iteration tolerance properly for the lower pressure range. At 5 kPa, water properties become very sensitive to small changes, and the default tolerances were letting the solver accept solutions that were off by several percent in enthalpy. I fixed it by going into the Solver Options dialog, tightening the convergence tolerance to 0.0001, and increasing the maximum number of iterations to 200. After that the parametric table came out clean. This took me two hours to diagnose. Do not make the same mistake. Optimization is another area where EES will surprise you if you do not know what you are doing. The built-in optimizer uses sequential quadratic programming, which is fine for small problems. I tried running it on a heat exchanger network with twelve decision variables and six nonlinear constraints and it either converged to a local minimum or failed to converge within the iteration limit. Half the time. For anything beyond roughly five variables and three constraints, I export the equations to a Python script using SciPy's minimize function and run the optimization there. EES still generates the equations and property calls, but I let Python handle the actual optimization loop. It is faster and more reliable for anything nontrivial. The plotting is functional but crude. You can generate XY plots from parametric tables and save them as images, but the formatting options are minimal. If you need publication-quality graphs, export the data and use matplotlib or OriginLab. The plot builder inside EES is fine for quick visual checks during development but it is not going to replace a proper visualization tool.
Get the Full Details
Documentation is sparse. The help files are decent for individual functions and routines, but there is no comprehensive tutorial that walks you through multi-disciplinary problems. The manual is more of a reference than a guide. I learned most of what I know by reading the example files that ship with the installation. There are about thirty or forty of them covering thermodynamics, fluid mechanics, heat transfer, and a few control problems. They are not exhaustive but they cover the patterns you will actually use. Copy one that is close to your problem, strip it down, and rebuild from there. It is faster than starting from a blank file every time. There are genuine limitations worth being upfront about. EES will not handle CFD or finite element analysis. It is an equation-level solver, not a field solver. If you need temperature distributions in a complex geometry, you are looking at ANSYS or COMSOL, not this. It also does not have native scripting beyond its own built-in programming language, which is functional but obscure. If you want to build automation pipelines or integrate with other tools, you are working against the grain. The export capabilities are limited to text and CSV, which is fine for most cases but frustrating if you need to push data into a MATLAB pipeline or a database. Another edge case that caught me recently: the liquid water property routine uses different formulations depending on the pressure range. Below about 1 MPa it uses one set of correlations and above that it switches. If you are running a parametric study that crosses that boundary, you might see a tiny discontinuity in derived quantities like specific heat or speed of sound. It is not a bug. It is just how the underlying tables are structured. The effect is negligible for most engineering calculations but it will show up if you are differentiating properties numerically or running sensitivity studies at high precision. I worked around it by clamping the pressure range in my parametric table so it never straddled the transition point, and I verified the results against NIST Webbook data at the boundary.
If you are evaluating whether to invest time learning this, the honest answer depends on what you do. For undergraduate thermodynamics, fluid mechanics, and basic heat transfer coursework, it is probably the fastest path from problem statement to numerical answer available. For professional work involving large-scale optimization, coupled multiphysics problems, or production-level automation, it becomes a bottleneck quickly. In those cases I use EES for the quick calculations and property lookups, then migrate the heavy lifting to Python or a dedicated optimization framework. The download and installation process is uneventful. You get an executable installer, run it, enter your license key, and you are in. The educational version has a watermark on exports and limits parametric table size to a few hundred rows, which is plenty for homework but cramped for a thesis project. Full version unlocks everything. I recommend starting with the educational license if you are a student, upgrading when the coursework moves toward research-level work. The property library is the same in both versions, so you are not losing core functionality by waiting. One final practical note: save your files as .ees format, not as plain text. EES stores unit definitions, property fluid selections, and solver options inside the file itself. If you export to text and reimport later, you will lose all of that metadata and spend time redefining everything. I learned this the hard way after a disk failure corrupted my working directory and I had to reconstruct a week's worth of problems from exported text files. Every single one was missing its unit assignments and fluid definitions. Do not make that mistake.
