Message-ID: <1372416184.2742.1419129844304.JavaMail.confluence@ece-vmapps> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2741_1443790691.1419129844304" ------=_Part_2741_1443790691.1419129844304 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The GSIM v1.0 Production group has a mismatch between the number= of subtypes for Process Input and Process Output.= em>
|Process Input||Process Output|
|Parameter Input||Process Metric|
|Transformable Input||Transformed Output|
|Process Support Input||?|
Separately, at the last GSIM IG meeting, the issue of a missing process = output object was also raised. It was felt that there is a need to have an = object to allow for output objects that are neither Transformed Ou= tputs (e.g. statistical data or metadata) nor Process Me= trics (e.g. measures of the performance or effectiveness of the p= rocess step), but more the types of outputs that could be future Proces= s Support Inputs.
"56. A Process Support Input influences the work= performed by the Process Step, and therefore influences its = outcome, but does not correspond to a Parameter Input or= a Transformable Input. Examples could include:
This could be accommodated within the v1.0 style framework by adding a n= ew object, Process Support Output, which would be the output = analogue to Process Support Input.
In the "GSIM Level 2" proposed for discussion, IMF contributor= s dealt with this issue somewhat differently. The concept of Process Metric= is replaced with a concept of Process Measure, which is defi= ned as recording metrics associated with the Process Step and logging work and kn= owledge = objects used in the Process Step and work and knowledge objects cr= eated by= the Process Step. This model assumes that the "work and know= ledge" outputs created need not necessarily be transformations of the = transformable inputs, but may be some type of reusable or otherwise informa= tive byproduct. These byproducts may fit an existing structured object from= elsewhere within GSIM, or may be unstructured explanatory information (whi= ch would fit within the Referential Metadata object in this model)= .
Arofan also had a number of ideas on the call and offered to comment on = this issue.