Currently a PME may ask any Unit Operation for the list of available reports that the Unit Operation may create, then may select one and retrieves it for display in its own report mechanism. A Flowsheet Monitoring Component "operation" or "calculation" will be trigged by some Actor. Then there is most often the need to display the results obtained by the Flowsheet Monitoring component. As with many UOs, the results may be displayed within the Flowsheet Monitoring component. If the PME controls the triggering of a Flowsheet Monitoring component, then it is worthwhile to let the PME take its results from the Flowsheet Monitoring Component and incorporate them into its general report. If, on the other end, the PME does not trigger the "operation" of the Flowsheet Monitoring Component, I don't see how a report could be obtained in due time from the Flowsheet Monitoring Component by the PME.

Having the ICapeUnitReport interface implemented on a Flowsheet Monitoring component does not seem to me a bad idea if such a functionality is needed. The Flowsheet Monitoring Component has some aspects of a Unit Operation. Why not then reuse some of the interfaces that are specific to a Unit Operation?

The PME will trigger the Monitoring Object by the very act of asking for a report; as with unit operation. ProduceReport() for some unit operations only returns a report that was generated by Calculate, but for other unit operations ProduceReport will perform the required actions to generate the report.

The ICapeUnitReport interface would be very suitable for the Flowsheet Monitoring purpuse. However, its name suggests that it should be only implement by a unit operation. It would be better if the interface had a more 'common' name, such as ICapeReport.