Speed and APIs have boosted scientific workflows but multi-environment deployment still needs workIn the product, they have started taking the right direction with Revvity Signals Notebook. They have added in-vitro analysis. That is, within Signals Notebook, you can define your experimental workflow steps. However, that is not very customizable. They have started adding those automation steps within in-vitro analysis. If you have a simple workflow, you can automate that within Signals Notebook itself using in-vitro analysis objects. You don't have to go to VitroVivo; you don't have to depend on Spotfire skill because VitroVivo requires your Spotfire skills. They can mature it because they have now started adding different plottings, such as P3 and P4 kind of plotting and curve fitting plotting. However, it is still at a very early stage. They can work on that area to mature their in-vitro analysis, to showcase all kinds of visualization and make their different steps more customizable. They have been adding more and more features in ADT. They can continue doing that with more and more functionality. For other functionality, they can also do things such as how they can combine multiple ADTs together. If we have to do a joining of two ADTs' data and putting it into other ADTs, or if we have to do a union of ADTs, if they can do it at the Signals Notebook level itself, then it will be quite flexible. Many tasks can be taken care of at the notebook level. You don't have to utilize the Signals Notebook API and then integrate it in your Python-based scripting or any other data pipeline scripting for doing this kind of task. Many things can be done at the notebook level. There are improvement areas in Signals Notebook itself, in the area of ADTs, combining data, and joining data. They can add the filtration as well. Currently, the limit in the ADT is 2,000 rows, so they can increase that limit to 10,000 and more than that. If somebody is joining one ADT to another ADT and then the result is getting saved into an ADT, then this row limitation should not come as a hurdle. For the stability of Revvity Signals Notebook itself, the rating is 9 out of 10. However, the only demerit of one feature of Signals Notebook is their deployment product. If you have multiple tenants, for example, one for the development area, another is for the QA area, another is for UAT, or then the production area, if you have multiple environments configured, and you want to deploy your experiments templates from one environment to another environment, that is a big pain. They have called it CTT functionality, and that is a very unstable functionality they have. It is one of the worst functionalities in Signals Notebook, that CTT tool they have. However, after getting complaints from the client side, they have started working, but the approach is still not that great. They don't have a seamless deployment application available from one tenant to another tenant. If I have to rate it, for deployment from one environment to another, I would be giving 2 or 3 out of 10.
