Open your HYSYS, DWSIM and COCO cases
Import a case and it arrives drawn, connected and specified, with a report of anything that did not come across exactly. Then one command compares every stream with the answer the other simulator stored.
Aspen HYSYS
HYSYS XML cases, and older binary .hsc files. Newer .hsc files are encrypted: open the case in HYSYS, File > Save As, choose HYSYS XML Cases, and import that.
Separators, heaters and coolers, valves, pumps, compressors and expanders, exchangers, mixers, tees, recycles, columns, pipe segments and Set operations come across with their specifications. Template sub-flowsheets arrive as blocks.
DWSIM
Compressed .dwxmz and XML .dwxml cases: columns, reactors with their reactions, the liquid–liquid extractor, and the common unit operations, with the case’s own interaction parameters.
A DWSIM Flowsheet unit operation arrives as a sub-flowsheet block, with the simulation it runs inside it, even when that file is embedded in the case.
COCO / COFE
COFE flowsheet files (.fsd). The sample cases include a published ammonia synthesis loop and an oil-and-gas separation plant, both imported from COCO and checked against COCO’s converged results.
Then check it, stream by stream
File > Validate import against reference values compares every stream of the solved case with the value the source simulator stored: temperature, pressure, flow, composition and vapour fraction. Each stream is marked within tolerance, a minor deviation or a significant one, and the worst offenders are listed first.
| Compared | Minor deviation above | Significant deviation above |
|---|---|---|
| Temperature | 0.5 K | 5 K |
| Pressure and flow | 0.5% | 5% |
| Composition (largest single mole-fraction difference) | 0.1 mol% | 1 mol% |
| Vapour fraction | 0.005 | 0.05 |
Agreement with another simulator shows compatibility, not correctness: a mistake both programs share still agrees. That is why the validation report keeps these comparisons apart from checks against published data.
Nothing is absorbed silently
Every import writes a report onto the drawing: what came across, what was approximated, and what was left out. If something is not in the report, it imported cleanly.
- A unit the app does not have yet is carried as a named pass-through, so the flowsheet stays connected
- A property package the app does not have is replaced by the nearest one, and named
- A column specification with no equivalent is replaced by the source’s converged value, and said so
What an import does not do
Chemistry this app does not model yet
Amine (acid gas) electrolyte chemistry and CPA association have no equivalent here yet. Those sections import and solve on the nearest package, which is not a reproduction of the original.
An import is not a certificate
Importing a case does not reproduce the original simulation environment or guarantee the same numbers. Every imported case must be reviewed by a qualified engineer before it is used for a decision.
Independent interoperability. The importers were developed independently. They read the information in a file you supply and convert it into AI Process Simulator’s own model. They contain no code from, and do not call or require, Aspen HYSYS, DWSIM or COCO, and they do not bypass any encryption: an encrypted case is not read. You are responsible for having the right to use every file you import. Aspen HYSYS® is a registered trademark of Aspen Technology, Inc. AI Process Simulator is not affiliated with or endorsed by Aspen Technology, the DWSIM project or the COCO project.
Bring a case you know well
The best test of a simulator is a case whose answer you already trust. Import it and see how close it lands.