The Methods and Tools Special Interest Group met from 5 pm till 6:30 pm Central European Time.
Agenda
Develop a Common interface specification for reporting
Participants
U.S. Environmental Protection Agency (represented by Bill BARRETT), AmsterCHEM (represented by Jasper van BATEN), Bryan Research & Engineering (represented by Michael HLAVINKA), Michel PONS (contractor for CO-LaN as Chief Technology Officer)
Highlights
The meeting starts from a draft (v2.0.000) put together by Bill BARRETT. The discussion shows the need to precise the scope given to a common reporting interface as well as to the notion of Reporting Client and Reporting Object.
At a first level PMCs may generate reports which are context sensivitive. A possible business case is a phase envelope calculated by a Property Package for specific conditions existing on a Material Object and the phase envelope is handed over as a Report to the Report Client. The Property Package is the Reporting Object in that case.
A second level would see Material Objects act as a Reporting Object. That way Unit Operations, as Reporting Clients, would be able to pull reports from a Property Package through the Material Object. That level calls for additional Objects to carry the interface ICapeReport specific to Reporting Objects.
So far the requirements defined Reporting Objects as implementing ICapeReport and Reporting Clients consuming ICapeReport. Additional requirements are needed such as the reporting process must not change the state of any object in the Flowsheet. These requirements are just penciled at this stage. They will be impacted by the exact scope given to the reporting interface and especially whether context sensitive reports are allowed or not.
The meeting ends at version v2.0.001 of the document describing the reporting common interface.
Next meeting dedicated to reporting interface is scheduled for April 11, 2018.
