Part of CAPE-OPEN standard v1.1

The Thermodynamic and Physical Properties Interface is a business interface specification for thermodynamic software components being used by PMEs.The Thermo SIG delivered the initial version of this specification in October 2006. This was the outcome of a process involving a review of the Thermo 1.0 specification, an analysis of the new requirements developed, and of a design phase. This specification was prototyped as a plug and a socket leading to improvements to the specification. A Request For Comments was conducted in June 2006 and its results led the CO-LaN Management Board to authorize its public release on September 26, 2006. A revision of that specification document was undertaken by the Thermo SIG in order to incorporate a number of clarifications that seemed important enough to justify a new document.

Thermodynamic and Physical Properties Interface specificationThermodynamic interface 1.1 (current document: issued in May 2011)

Comment: It is important to point out that, through the revision issued in 2011, the interface design has not been changed whatsoever since its original release): the IDL and the corresponding type library remain unchanged. Still many clarifications have been brought to the original document. Developers are especially asked to carefully read sections 7 and 8 of the new document: it provides useful information on how to implement the Thermodynamic and Physical Properties interfaces in version 1.1 of the CAPE-OPEN standard. It is hoped that this new document will help developers implement more easily the corresponding interfaces so that the end-users enjoy an even better experience through CAPE-OPEN interfaces.

Errata and Clarificatons: current document was authorized for public release on December 13, 2012.

Comment: clarifications are related to the expected behaviour of a Property Package Manager, to the frequency of calls to SetMaterial method, to the request bubble and dew point calculations, to the behaviour of a Material Object around a CalcEquilibrium call, to the order of specifications in a CalcEquilibrium call, to the recommended use of CheckEquilibriumSpec and to the interpretation of UNDEFINED as a CapeString. All developers should take a look at the Errata and Clarifications in addition to the full specification document.

Developers are encouraged to report errors and to request further clarifications. Comments and inquiries are to be sent to the Thermo Special Interest Group.