Tulip Frontline Operations Platform

My main use case for Tulip is to fill up all the data which will be available from backend for the use of a warehouse. In a warehouse environment, I use Tulip by recording all the data, which made it an easy-to-build application. The implementation involved different stages where people from different warehouse departments would use it and fill up the data.

Tulip's best features include the front-end design, which is easy to use with drag and drop functionality to create applications quickly. The database connection is also straightforward, making it an easy-to-develop application overall.

The biggest difference for my work came from the database connection, which is easy to use, easy to populate with data, and easy to work with. The front-end is also easy to update if there are any changes, and it is very fast. We can make changes and adapt to user requests quickly and efficiently.

Tulip has positively impacted my organization by making it easier for developers. Managing one to three projects can be hectic, but with Tulip, if changes are needed, we can discuss them quickly, implement them, and deliver them on time. This saves our time significantly. For projects that would take two to three days in other applications, Tulip allows us to complete them in one day.

Tulip can be improved by offering better design and better functionalities. While making the application workable is really good, we should also focus on being great and user-friendly. Tulip is already user-friendly, but it can be enhanced further.

I would like to suggest that buttons and other fill-up elements in Tulip can be improved and made more visually appealing so that anyone looking at the UI part would be attracted to it and think that it is easy to build and looks attractive as well.

I have been using Tulip for three months.

Tulip is stable.

Tulip's scalability is good.

I am not sure about the customer support as I did not get an opportunity to talk to customer support directly. However, when I did certification, there were many people reaching out to me, which was really good.

I did not previously use a different solution before Tulip. We were using a Chrome web application prior to adopting Tulip. That web application takes more time, but Tulip looks much more beautiful, much more user-friendly, and easier to operate.

For pricing, setup cost, and licensing, I was not working on that aspect. There was a different team handling those areas. My core part was the development.

I have seen a return on investment with Tulip. Fewer employees were needed, and both time and money were saved. I cannot share the specific metrics as I am not aware of them.

Regarding Tulip's AI capabilities, I believe its accuracy and reliability of output is good. Whatever data we provide from the data perspective is displayed, and whatever UI is created is there as intended.

My advice to others looking into using Tulip is that it is really good, user-friendly, and can be developed very fast. If you want to create a prototype or any initial version of an application to show the client, Tulip is really good. However, if you want a much larger version with better scalability and more UI features, you can consider other products. For the starting phase, Tulip is a good choice. I would rate this product a 7 out of 10.

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.

I'm the tech lead for Tulip platform in Roche, and our users have been developing a number of applications such as e-logbook, e-cleaning software, and a number of checklist execution software. E-logbook is being used to help operators and technicians add details to what happened during certain events. They would input information by voice or by text on the specific events and relevant information to the system. We also have a use case where Tulip is being used to manage water sampling collection for a factory in which the water needs to be sent to the labs for periodic checks. E-logbook is being used to create the tasks or checklist for operators to sample the water and record the details to be sent to the labs.

What has really improved is the time taken to develop and deploy applications. I think we save many weeks of work weeks in the development phase. It's not the conventional way of programming where we would take easily 50 to 100% more time to develop the application, but with Tulip, it has been shortened.

I believe we are still at the beginning stage of using Tulip, but it already opened a lot of eyes in realizing that the process to digitize our manufacturing processes and the process to simplify a lot of manual things has been really easy compared to the conventional way of developing applications. I think more and more people are now willing to start developing applications by themselves. Each successful use case has been studied and has been a reference to other new user groups, and that's good for the growth of using Tulip in our organization.

For us, it's more about time saved. What we're seeing is time saved in developing applications and time saved for operators to perform their work, especially those manual tasks that have been translated to electronic applications. A lot of time saved has been recorded, and it also improved data accuracy.

Tulip offers fast and very comprehensive capabilities for process owners to create the applications. Another big plus would be the AI features that would enable users to optimize the use case in order to meet their expectations.

Tulip can improve with better or closer support in developing the applications, especially when we as a pharmaceutical company would have our specific requirements and needs that are mandatory for our industry. If Tulip can really cater to most of those requirements, that would be good.

The main challenge for our team is to validate or qualify the applications. As a pharmaceutical company with the GXP and CSV practice requirement would require more steps to validate the process. Tulip can really help in catering to these specific needs. Efforts have been made, but I think more can be done.

I believe Tulip is a very useful and modern tool that would give the process owners capability to develop their own apps. The use cases that can be handled by Tulip are very vast, but there will be room for improvement that will reduce the issues or the challenges that users are facing.

I have been in Tulip projects for the last one and a half years.

Tulip so far has been very stable. We don't have any downtime yet. I think only once we had a performance problem, but I think that's related to the distance of the instance and the users. I think we have multiple instances around the globe, and it's just for the user to pick the correct one.

Tulip is highly scalable. It's quite easy to scale the platform to our new sites globally and each application that is being released or deployed is easily scalable to new sites or to new factories.

I would rate customer support as 7 out of 10. Improvement can be made in responding to our questions and responding to some of our technical needs, documentation, and other things. Other than that, I think it has been good.

Tulip can improve with better or closer support in developing the applications, especially when we as a pharmaceutical company would have our specific requirements and needs that are mandatory for our industry. If Tulip can really cater to most of those requirements, that would be good.

Tulip is our first low-code, no-code platform.

I think it's quite easy. Users wouldn't find any big issues on learning Tulip. The learning curve is above average compared to other tools.

I would rate Tulip 8 out of 10 in my overall assessment.

The online documentation has been very helpful. It's easy to find answers to technical questions online.

I would say try to educate the developers' community with the benefit of using Tulip so that they can develop the right application using Tulip. Also, try to educate the end users of the application so that they understand how this would improve their daily work.

I believe this is not a big issue. We have been integrating Tulip with a few other systems, and it has not been a big issue. I would say it performs a little bit better than most of the other tools.

I am working at Fresenius Digital Technologies as a senior consultant in Global Quality and Compliance, specifically on CSV implementation for global systems and global infrastructure.

I worked for nearly one year at my previous company, Bayer, where I was supported for the global implementation of Tulip system.

I was primarily involved as a validation representative for Tulip MES system, specifically for the China Qudong site.

I supported a pilot project at Qudong, and during that time, I helped identify requirements, conduct risk assessments, write validation plans, create validation reports, and review and approve test cases and validation reports. My primary goal was to deliver a pilot project. Based on the pilot project, we had broader ambitions to establish global implementation. Unfortunately, the project did not succeed as the technical team from TCS was unable to complete all development tasks and configuration tasks. The overall application did not meet Bayer's expectations and business requirements, so the project was scrapped. Later, they connected with another vendor who implemented the solution smoothly.

I received training on Tulip and obtained a Tulip certification. I also supported functional specification reviews, configuration deployment, configuration setup, and field templates.

I see 100% potential for Tulip helping my organization achieve its long-term goals, even though the project did not go live.

Tulip is a pre-configured tool where all fields and options are readily available on the Tulip platform, which impressed me when I evaluated it from a CSV perspective and development perspective.

Tulip is an AI-based tool, and I do not need to do any coding. All configurations are predefined and readily available on the Tulip platform, making it a very simple and understandable tool. A non-technical person can build their own MES application using Tulip.

We had significant ambitions with Tulip, and it gave us an idea to simplify complex processes, including manual documentation. We were using multiple tools to monitor one manufacturing process, and Tulip provided a single point of application to minimize our effort and establish a new thought process that would help improve production and compliance.

I experience a lag in contacting Tulip employees when technical support is needed, which has been very difficult over the last two years. I am unsure how Tulip teams work or provide support currently, but as a new tool in the industry, we need foundational guidance because all staff members supporting the project were new to the platform. We needed initial guidance and proper knowledge transfer from Tulip so that our team could work efficiently to implement or complete development. Unfortunately, this did not occur as the knowledge transfer provided was insufficient. They provided only one day of knowledge transfer and charged for additional items. Tulip requires professional development credits to contact or discuss or review products, which puts me in a situation where whenever we need support despite already making a payment for the platform, we are seeking their help or suggestions for half an hour, yet they request professional development credits. They are the subject matter experts and knowledgeable persons about their product, so when we have questions, they ask for money. This raises significant questions about how Tulip can improve in that respect, and the employee response was very rude.

Tulip can improve its knowledge transfer sessions.

The pricing is somewhat high compared to other market applications. While it is not excessively high, the service cost is very heavy, which presents an area for improvement. This situation creates more opportunities to consider other vendors. In my current organization, we are looking for an application that supports all documentation and repository needs for handling change, test cases, application lifecycle, and managing all application-related documents, including validation, migration, and decommissioning. We are considering an application such as ValGenesis to evaluate how it performs.

Scalability is good as Tulip can be integrated for multiple processes, but practically, I do not have a concrete answer since the product did not go live.

Customer support receives a rating of two in my experience because they are very difficult to contact. Whenever we send an email, they take two to three days to respond. Scheduling a call takes one to two weeks, and they request pricing and money to set up a call.

Previously, we used TrackWise, ValGenesis, and ServiceNow. We considered implementing Tulip because it is AI-generated and reduces dependency on external IT companies such as TCS and Capgemini, which was the main reason for the decision. A subject matter expert can implement whatever change they want, and that was the primary reason we considered implementing Tulip.

The project was scrapped, so I did not get a chance to use Tulip, and I left the organization and moved to another company at that time.

The main factors that led my team to choose Tulip over other solutions were that it provides a single platform with all MES-related support.

Although this project was scrapped, we had ambitions to integrate applications such as Empower and LIMS, and we were uncertain whether this would be practically possible, but that was our initial idea.

Based on industry trends, I expect very positive growth for Tulip. Even though there is upcoming market competition, I have a positive outlook on Tulip. They only need to improve their service quality.

We used ValGenesis for handling change management and training when implementing Tulip.

I found Tulip's documentation and user community to be very impressive and informative.

I would rate this review as a 9 overall.