Versioning for process and product specifications

Riffyn’s process versioning capability is useful in an environment where a process is being continuously improved and the improved process is being transferred to production groups or other collaborators. You can update and save new design specifications on a process as a new version.  Collaborators or downstream production groups can be notified of the new version.  Those groups have the option to continue using the old process, or upgrade to the new. 

When collaborators use old and new versions of a process at the same time, Riffyn still keeps all the data structured and organized---all the specifications, experimental and production data will be linked together from all versions of the process for later analysis.  That data can be exported in one step as a CSV file (ready for statistical analysis), or through the API.  It can also be visualized and explored directly in Riffyn.

For example, suppose you work in fermentation process development (PD), and you are regularly transferring process improvements to the product manufacturing group.  Initially you may be working on version 17 of the process.  The version is recorded in the sidebar of Riffyn Design mode.

Version 17 has the following parameters on the fermentation.

Subsequently your PD group decides to run a designed experiment varying 3 parameters (temperature, antifoam volume, and seed inoculum density) to try to optimize the batch productivity.  You decide to create a new experiment on version 17 of your process, and place 8 fermenter runs on that experiment with varying values on the three parameters. 


You run the process, collect the data into Riffyn, and then run a multivariate regression analysis.  You identify a new optimal parameter combination that delivers 10% greater batch productivity, which is an improvement on the previous process.

To capture this process improvement, you would open the working version of your process in Design mode and modify the target settings for those three parameters.


Those values are automatically saved.  To give these changes a permanent version number, you save a new version of the process. 

Now those parameters are permanently affixed to the new version 18. 


You or your collaborators can now begin creating new experiments and performing new production batches on the new version. (Or continue using the old version as well.)

As a final comment, we note that Riffyn captures product specifications as well as process specifications, because the outputs of your process are the product (or product ingredients). You can place quantitative specifications on these outputs right alongside the process specifications that should deliver that product.



Have more questions? Submit a request


Article is closed for comments.