The UNIT SIG held a conference call from 4:30 pm till 5:30 pm Central European Time.
Agenda
Modifications to revised Petroleum Fractions interface specification.
Participants
AVEVA (represented by Krishna Murthy PENUKONDA), Bryan Research & Engineering (represented by Michael HLAVINKA), AmsterCHEM (represented by Jasper van BATEN), Cesar PERNALETE (University of Ghent), Michel PONS (as CTO from CO-LaN, contractor), Shell (represented by Richard BAUR), ChemSep (represented by Harry KOOIJMAN).
Highlights
UNIT Special Interest Group reviewed modifications proposed by CTO to the revised Petroleum Fractions interface specification:
- omit references to methods of version 1.0 of the Thermodynamic and Physical Properties interface specification,
- adopt only isPetroleumFraction as the Boolean Compound Constant to designate a Compound as a Petroleum Fraction,
- remove the requirement that all Ports of a Refinery Unit Operation must be connected to Material Objects supporting Petroleum Fractions, i.e. implementing ICapeThermoPetroleumFractions,
- define what a Refinery Unit Operation (REF-UNIT) is in the glossary of terms special to the Petroleum Fractions interface specification.
The above modifications were approved as part of version 5.46:
- version 1.0 of the Thermodynamic and Physical Properties interface specification has been deprecated by CO-LaN and still making reference to it would defeat the purpose of the deprecation,
- choosing a Boolean type for the Compound Constant designating a Compound as a Petroleum Fraction is considered as a better solution than relying on a Compound Constant expressed as a string (it leaves the possibility to define new Compound Constants if the need arises for other types of Compounds to be identified, and it is easier to deal with the situation where real Compounds do not carry this Compound Constant),
- UNIT SIG recognizes the possibility for a Refinery Unit Operation to have Ports connected for example to a stream carrying only steam, where support for Petroleum Fractions is not necessary,
- the definition of what is a Refinery Unit Operation may have been dropped from the document at some point in time, and needs to be reinstated.
Categorizing a Refinery Unit Operation differently from a CAPE-OPEN Unit Operation within the Windows registry was discussed as an additional modification. Use Cases supporting the need for a separate category of CAPE-OPEN Component will be developed to help decide if such a category needs really to be defined, so that a decision on this proposal can be made before or at the next meeting of the UNIT Special Interest Group.
