Difference between revisions of "OLI Engine in Aspen HYSYS"
m (PMCKENZIE moved page Aspen HYSYS to OLI Engine in Aspen HYSYS: names standardization) |
|||
| Line 1: | Line 1: | ||
==OLI Engine in Aspen HYSYS== | ==OLI Engine in Aspen HYSYS== | ||
| + | |||
| + | |||
| + | HYSYS Electrolytes OLI, also known as HEO, is a joint product between AspenTech and OLI. | ||
| + | |||
| + | |||
| + | The OLI Engine in Aspen HYSYS is the OLI component that enables HEO. With HEO, clients can use OLI AQ or OLI MSE as a property method inside Aspen HYSYS. Through the Aspen HYSYS mechanism of sub flowsheets, HEO clients can define the electrolyte portion of a flowsheet using OLI, while keeping other parts of the flowsheet in other property methods. | ||
| + | |||
| + | |||
| + | OLI Engine in Aspen HYSYS is sold through OLI. | ||
| + | |||
| + | |||
* [[ Using OLI in Aspen HYSYS]] | * [[ Using OLI in Aspen HYSYS]] | ||
Revision as of 17:20, 4 September 2014
OLI Engine in Aspen HYSYS
HYSYS Electrolytes OLI, also known as HEO, is a joint product between AspenTech and OLI.
The OLI Engine in Aspen HYSYS is the OLI component that enables HEO. With HEO, clients can use OLI AQ or OLI MSE as a property method inside Aspen HYSYS. Through the Aspen HYSYS mechanism of sub flowsheets, HEO clients can define the electrolyte portion of a flowsheet using OLI, while keeping other parts of the flowsheet in other property methods.
OLI Engine in Aspen HYSYS is sold through OLI.
