In my implementation projects using Tulip, we created tables for all the recordings, designed the steps, made the wireframes first, and then created the triggers and logics behind, saving everything in tables. I worked mainly on logbooks for a client who was transitioning from paper-based processes. We created applications for the client to save information in the apps, including all details and signatures for keeping equipment clean and ready.
The client's reaction to moving from paper to the digital logbook in Tulip was initially cautious as they needed to become accustomed to the new system, but they primarily loved it, finding it much easier to use a tablet than managing lots of paper.
Additionally, we created and worked on another project where we developed an OEE, an Overall Equipment Efficiency indicator, and I also trained the operators to use it, providing hypercare support, though it was not a GMP product.
Tulip offers the best features because it can be adjusted very quickly to the operator's needs, which is always engaging. In a GMP environment, the engaging part is somewhat limited because validation is required, but I still believe it is much quicker to implement any changes the operators need on the shop floor.
In terms of how quickly I can implement changes with Tulip compared to other solutions I have used, in the non-GMP environment, we implemented solutions and recommendations from operators from one day to another by creating a new version with the changes recommended by the operators, which would be running the next day. In the GMP environment, it depends on the validation and how long that takes for the changes, but it is usually much quicker than other tools, even though it varies from company to company.
Tulip has positively impacted my organization by helping us learn to work in a very adjustable and new environment, coming from old systems where everything is predetermined. In Tulip, you can adjust everything, and while it is also engaging and challenging when you have to create each button and put the writing on it, once you are used to it, the steps are automatically created. However, good initial consideration and planning are necessary, especially if there are many steps to be changed because afterwards, it can be long and exhausting, such as when we had to change the color of one button on fifty steps.
This flexibility and ability to adjust things have led to measurable improvements in our projects, particularly in terms of time saved and user satisfaction. This was also expected by the client, which is why they chose to use Tulip to eliminate the old systems that were no longer needed, especially for the logbooks. The client was very happy to have it completed quickly; in one month, we created approximately forty apps for them, which would be unimaginable with an old MES system.
Tulip can be improved in terms of the struggles we had with languages where operators spoke another language than English. We assumed Tulip assured us there is an integrated AI for translations, but we encountered issues especially with the tables, where the text was in tables. I am not certain how that could be improved, but generally, having good AI implemented for translations of information and instructions in the applications would be significant help. Additionally, implementing AI for making small changes on the steps and wireframes, such as having an AI tool adjust all the writings or buttons and bringing harmonization, would be a valuable addition from Tulip.
Regarding Tulip's AI capabilities, I cannot provide substantial insights as I do not possess much knowledge about that aspect. I believe it is still at the beginning and not really advanced for the part I was using, so it could be improved.
I have been working in my current field for three and a half years.
My advice for others looking into using Tulip is that it is an interesting solution. I would rate this review a seven out of ten.