Several end-users of CAPE-OPEN thermodynamics property packages have the desire to set up a simulation on one computer, save it, and then transport the simulation to another computer, run it, and be ensured that this simulation is using the same thermo. This appears to be very reasonable demand.

The mechanism that can be used to do this, is to use the Persistence Common Interface to store the content of the property package along with the document you are saving.

As very few thermo servers seem to implement that, and there appears to be a need for this functionality by end-users, the purpose of this thread is to gather information from both users and software vendors.

Any end users that would like to comment on their experience with the need for (and perhaps the absence of) the persistence interfaces in existing thermo systems are welcome to do so.

Software vendors that have implemented the persistence interfaces on their property packages are invited to indicate this here. Software have not implemented persistence and have reasons not to implement this are also invited to comment on the subject.

Infochem implemented the Persistence interface for our Multiflash Thermo 1.0 and 1.1 components for the version 3.8 release in December 2008. We consider that the type of workflow described by Jasper should be supported by CAPE-OPEN Property Packages when used in 'real-world' applications. The fact that the Pesistence interface is not widely implemented is holding back potential users from using it.

TEA has persistence implemented as well. In addition to that, TEA (and I believe Multiflash too) have Edit implemented. This means that end-users can (if supported by the PME, e.g. in COFE) modify the property package while it is loaded inside the document.

Edit functionality does not make sense if the edited package cannot be stored, so persistence is a prerequisite for Edit.

More important: persistence allows a document including its thermo configuration to be moved from one computer to the other without the need to move all thermo configuration files. Often, end-users are not aware of how thermo property packages are stored - which depends on the underlying thermo server.