Tulip Reviews

I am using Tulip for digitalizing my client's shop floor MES applications. They are tableting manufacturing line, converting the physical MBR to the digital operations.

One of my client engagements involved being part of a core team that built eight connected Tulip applications replacing a tablet manufacturing line for the client. The eight tablet Tulip applications include a whole manufacturing line, starting from batch process applications, moving to weighing and dispensing material management, then tableting, primary packaging, and secondary packaging. These are the applications that I built for the client and these are the shop floor use cases for Tulip.

I would also like to add one experience and project with another life science client, which is a global digital operational excellence platform. Through this platform, we take up several common use cases from the client's side, such as cleaning, e-logbook, and asset tracking, and then globalize it and localize it accordingly. We create different Tulip instances for different sites while managing it globally. That is another use case that interests me while using Tulip.

Tulip applications are the common and basic features that Tulip offers. An application is nothing but a recipe for a SOP or a manufacturing order to which the application is being created. Another feature is Tulip tables. Tulip tables are an inbuilt Tulip database that is similar to a NoSQL database. A third feature would be Tulip dashboards. Dashboards are useful to track and analyze data throughout Tulip instances. Another feature is Tulip connectors, which are used for connecting different applications and different software to Tulip in an ecosystem.

One of the best features that I feel Tulip has introduced is more AI-related and AI-compliant features. Tulip offers an AI feature or agent that can connect to different Tulip instances and applications to create an agent so that we can use AI in Tulip itself. Another AI use case in Tulip is a Tulip chat widget, which is a widget that can be added into the application to give operators access to the AI feature. A third AI feature, although I don't know the exact name of it, takes the PDF of an SOP and converts that PDF into a Tulip application itself through AI. Those are the features that I feel are best when it comes to Tulip.

Definitely, AI in a regulated industry is something that is a concern of the clients. However, Tulip can stick to 21 CFR Part 11 strictly when it comes to Tulip's AI capabilities. Tulip has already started to look forward to compliance-related things. For example, Tulip's AI widget offers data reading throughout the site. It does not allow any AI to interact with external systems when we apply firewalls on it. In this regard, if Tulip continues in that way, they can definitely stick to the governance and security.

As of now, I didn't face any issue related to their AI capabilities. It is working fine but not accurate, which is a red flag in a GXP regulated system. This is my feedback on their AI capabilities. This has been introduced into the latest LTS version and needs more hands-on experience. Before that, I cannot give a direct justification or feedback on their AI capabilities being reliable and accurate. However, at the extent that I have used them, they are accurate and reliable as of now.

Tulip is an emerging platform and being a cloud-native MES, it has a lot to improve. According to me, traditional MES like FactoryTalk PharmaSuite has more complex features and user-oriented use cases and complexities that the application itself handles. However, when it comes to Tulip, all the things that matter are in the hands of a developer. That is something that Tulip can improve on. Tulip can switch to a traditional way of delivering in the pharmaceutical industry while keeping the cloud-native impact intact. One improvement that I can give an example of is that Tulip has application templates. Instead of templates, they can offer concrete applications to their pharmaceutical or any specific industrial client for their specific needs, such as a recipe designer and production management for a pharmaceutical client. Then production or material tracking or BOM tracking for a discrete client. In that way, I can see an improvement where Tulip can perform well.

I have been working in the current field for 3.10 years, and in that time I have worked with MES Tulip.

Tulip is stable with no downtime or reliability concerns. However, when it comes to large data sets, it sometimes takes time to load data from a Tulip table to the applications. The delay is about two to three seconds, which is not much but is noticeable.

When it comes to scalability, Tulip is much more scalable. Tulip suggested multiple sites and multiple instance approaches instead of staying on one interface. This solution addresses scalability concerns for clients when it comes to Tulip.

I have experience connecting with their customer support. When it comes to day-to-day activities, they are really supportive and they jump into our problems to solve issues from their perspective as well. I also have experience with their support while upgrading the instance for Tulip. When it comes to long-term support upgrades for Tulip, they are very supportive. I would rate their customer support 9.5 out of 10.

Previously, my client did not choose a different solution, but they have used traditional MES platforms like Werum's PAS-X, Siemens' Opcenter, and FactoryTalk PharmaSuite from Rockwell Automation.

I'm not sure about the exact numbers, but I can say that 60 to 70 percent of the development gets faster. When it comes to development, if a traditional MES takes three to four months, Tulip can do it within two to three weeks. That is one of the measurable things. In one of our client engagements, Tulip also offers analyzing station monitoring. Tulip charges their client on a station and interface basis. We saw a gap where according to the client's site and station, Tulip charges them. This indirectly has an 80 to 90 percent dependency on the use case. Those are the only metrics that I remember when it comes to cost and compliance.

In a general sense, I can say a client saves 60 to 70 percent when it comes to Tulip compared to the traditional MES when it comes to money. When it comes to time, it saves 70 to 80 percent when it comes to the deployment and development of the feature and digitalizing process.

Tulip costs less than a traditional MES and it charges according to the use case of the client. Those are the main three positive impacts that I can see our client's organization has positively experienced with Tulip.

My client and I are mostly of a pharmaceutical background. FactoryTalk PharmaSuite is one of the competitors that is stated close to Tulip when it comes to delivery. However, when it comes to cost, Tulip charges less than FactoryTalk PharmaSuite. The client has a traditional FactoryTalk PharmaSuite for their day-to-day production activities. On the other hand, for adopting a cloud-native platform, it switches to Tulip and stays relevant for the common use cases and simple use cases when starting it. It moves towards more complex MES solutions throughout the application development.

Tulip's main use case for our organization is making paperless applications. Previously, our site used a paper-based process to manufacture vaccines on the shop floors, but now we are automating that paper-based process to electronic MBRs. People in the shop floor now use tablets and Tulip applications to follow the manufacturing process instead of using paper.

We have downstream and upstream applications. Previously, the process was manual and took more time to manufacture. There was significant scope for human errors because people recorded data such as temperature or calculations manually. Now, there is no scope for mistakes because everything is done using logic and triggers in every step on the back end. Everything is done automatically, so the scope of human errors is very minimal. The batches of vaccines being manufactured now are produced very fast. Previously, it took considerable time, but now we can manufacture batches of vaccines in a very short timeframe.

The process is automated and audit history is available. Everything is recorded in the back end automatically. Whenever a quality check is done, people can see the complete history, including what has been done for the process from batch creation, whatever steps have been covered, whatever steps have been performed, what calculations were done, and who signed it. Tulip offers the capability of electronic signatures. Everything is transparent and the scope of error is minimal. Manual efforts are reduced. Additionally, the process is environment-friendly because we used so much paper previously in the shop floors, and now there is no use of paper. This is helping the environment and making the process eco-friendly and cost-effective.

Previously, the process was fully manual and paper-based. We did not use any technology previously in the shop floor. Now we are using Tulip to convert the paper-based process to paperless.

Tulip's best features include electronic signatures. Additionally, no knowledge of hardcore coding is required in Tulip because it is a low-code platform. People with basic analytical skills can use it. Whenever we require resources for our projects, we do not have to search for someone with very advanced knowledge. Tulip is very easy to learn with self-paced courses available in Tulip University. It is very easy to use and drag-and-drop based, so no hardcore coding is required.

Electronic signatures are very useful. In one click, we are able to do the signature. This is a very useful feature in Tulip for doing electronic signatures. It is appropriate for most of our use cases because in our applications, we have many steps where we need the signatures of different people. Tulip also offers the scope of choosing who can sign it. The person running the application can sign it, or we have options for people who have not logged in to sign. These options are available in Tulip. Additional printing, scanning, and again signing and uploading documents is not required. While running the application, people can simply do signatures in one click.

Tulip is a very user-friendly tool in the manufacturing industry. People can use it and it will help them to automate the process from manual to automated. It is a very useful tool. In the current versions, we have automations and connectors. However, in our applications, we have not had much scope for using connectors or automation until now, so I cannot provide more input on that.

Tulip has some drawbacks. Some complex calculations are not done in Tulip. There is a drawback in that if we write too many triggers in one step, the application slows down. This is a drawback. For complex applications, Tulip is not equipped well as of now. For simple applications and straightforward manufacturing applications, Tulip performs well. However, for very complex applications, Tulip is not a good option.

For complex application handling, Tulip is not equipped well as of now, unlike other low-code applications such as Mendix. Tulip could work on handling complex applications as well. However, for simple and straightforward applications, Tulip performs great. Additionally, the license cost is very high for Tulip. I do not know the exact cost because I do not handle that, but I heard that the license cost is something that could be reduced.

I have been using Tulip for three years.

Tulip is quite stable. There is not much slowness.

Tulip enables manufacturers to build, scale, and deploy digital applications in the shop floor, such as digital work instructions, logbooks, and machine monitoring without replacing existing monolithic back-end systems. Tulip achieves global scalability across enterprise manufacturing sites through several key features because of its composable architecture, multi-site workspace, and cloud-native backbone.

Customer support is good, but I cannot say it is great. Whenever we faced any issues with Tulip that we did not know the solution to, we always reached out to the Tulip support team and emailed them. However, I cannot say that the solutions we received were always quite useful or we did not have to do multiple follow-ups. It is good, but I cannot say it is great.

We did not use any other options previously.

We have achieved significant profit in our organization. We have many projects using Tulip that have generated significant profits. We have done excellent work building around one hundred apps in the last three years using Tulip, and they are all in production and running successfully. We have received huge accolades and appreciations from clients.

Fewer employees are needed because Tulip is a very easy tool and we can create applications in a very short span of time. Many applications can be created and it is a very fast process. Many batches of vaccines are now created very fast. Money is saved, time is saved, and everything is optimized.

Reduction in errors is obvious because previously it was a manual process. There was huge scope for human errors, doing calculations wrongly, doing signatures wrongly, and everything else. Now it is fully automated. There is no scope for doing any errors, so errors are essentially nonexistent. Money is also saved because the process is automated, so faster batches of vaccines are now created. Time is saved, and time saved means money is also saved indirectly.

I do not handle the license, setup cost, and licensing because I am a developer and only do the coding part. The managers handle the licensing part. I am not the correct person to answer questions about this.

If your applications or the process you are doing are mainly used in manufacturing processes in MES, and if your process is a straightforward process with no much complications, no much dependence on other systems, and no very complex calculations or complex things, then you can certainly use Tulip because it will help you to develop applications very fast. However, if your application is quite complex, I will not suggest Tulip. You may reach out to other low-code platforms such as Mendix. Tulip is not good for complex applications.

Tulip is doing great. It is helping us to create applications so quickly. In one sprint, in two weeks, we are completing two or three applications and it is easy to use. That is why it is effective.

I have not used AI capabilities of Tulip as of now. I have only seen in the latest update of LTS 14 that we have a chatbot present where we can use AI. Apart from that, I have not used any AI capabilities of Tulip yet.

Fewer employees are needed because Tulip is a very easy tool and we can create applications in a very short span of time. Many applications can be created and it is a very fast process. Many batches of vaccines are now created very fast. Money is saved, time is saved, and everything is optimized.

I would rate this review as an 8 out of 10.

Our main use case for Tulip is to train people on how to unify lean and technology together so that people don't think they have to do just lean or just technology. Our use case was somewhat unconventional.

We use Tulip as the backbone to set up scheduling and determine what products need to be run in what order. We also use it to run through instructions for how to assemble the product and conduct quality checks, using pictures to store quality check documentation.

We are using Tulip as a representation of systems and not necessarily Tulip itself, but to help people understand the ability to make products themselves, the DIY software adaptability, and how it can help.

The best features Tulip offers include the fact that it is fairly easy to set up and allows you to connect things.

By connecting things, I mean connecting to devices, and that's really what I was evaluating. We connected to a couple of different things, a micrometer and a scanner, but it has a whole list of devices that can be easily connected through developed APIs.

Tulip has positively impacted our organization by allowing us to put together a software package that would help conduct this training class in an inexpensive manner.

One way Tulip can be improved is that the biggest challenge is if you already know programming. Tulip is extremely hard to set up because it doesn't follow standard programming rules. It runs based off more logic rules that somebody who doesn't know programming might think. This makes it a little bit difficult for people with some programming background to use.

The main problem that Tulip has right now is that they're still learning as they grow. They're growing a little bit faster than they can really maintain. Some of the individualism and customer service that they had at the beginning has been lost. I give it a six for this reason.

I have been using Tulip for about two years.

Tulip is stable.

The customer support is one area that they definitely have gone beyond when it is standard customer support. However, when we're doing these fringe, outside of the norm type things, it is not something that they are capable of adapting to.

I didn't really have to deal with any pricing, setup cost, or licensing as it was all handled through my boss and the leadership at Tulip.

I have not seen a return on investment, but that's not really what our use case was about.

Before choosing Tulip, I did not evaluate other options. We developed it as part of the interface being with the leadership of Tulip and the leadership of Mass MEP. It was really developed as part of understanding Tulip to begin with.

The only specific outcomes I can really share are that a lot of people that have taken the class seem really passionate afterwards and see how simple technology can make a significant impact on their company.

My advice to others looking into using Tulip is to really know your use case and start with defining your process. That makes it a lot easier to set it up.

I rated this review a six.

Tulip is a composable MES platform that can tackle multiple use cases. We primarily use it for digital shop floor applications designed for frontline operators who need a screen and user interface to interact with both machine data and business data. This enables us to create various use cases including digital work instructions and overall equipment efficiency for machines. Tulip also serves as an additional layer for integrating with laboratory information management systems or ERP systems, making it highly versatile.

At one of our customers, we are currently creating the blueprint to replace their complete MES with Tulip, which represents a very different approach with composable MES compared to monolithic products. Using Tulip for this customer, we start by blueprinting the order initiation through integration with an ERP system and focusing on the workflow of an operator who starts an order on the production line. We then work on order execution, covering everything an operator does and needs to enter into a system when the order is being executed. After passing through the order registration, the system confirms back to the ERP what raw materials were used.

Tulip is definitely a platform that should be used in an agile way. After creating the first application, you start learning things about the platform and can reiterate that application while moving to the next one. Tulip is really about empowering people to build applications, and those people who build the applications are not necessarily only technical experts or developers. These are business process users who are now capable of making their own applications. Tulip can be considered the new Excel of the new era.

Tulip offers a no-code design editor to build apps and a wide range of connectivity features to connect to both IT systems and OT systems. The platform includes AI features so that you do not have to build AI on top, because AI is embedded inside the platform. This not only assists the application builders or architects but also enables frontline operators with AI capabilities without the technical burden or needing to subscribe to another platform or buy tokens. Everything is included in the same subscription.

The no-code designer feels as though you have PowerPoint. You design your application step-by-step, similar to designing PowerPoint slides. You drag visual components onto your presentation or application and then start configuring the visuals as well as the background logic in a very user-friendly manner. This enables everyone to understand what has been built by experts or start building their own applications. The AI-enabled features include automatic translation of applications to other languages using AI translation, or creating basic applications from a functional description or a standard operating procedure that gives you an automatically AI-generated application you can then start tweaking. AI can also be used to scrape documents, allowing operators to use a chat to converse with the documentation or manuals of their machines if available. Finally, AI can be applied in vision use cases, such as drawing a rectangle over a zone where your hand needs to pass before Tulip understands that you have taken a piece out of a bin, and then it moves to the next work instruction.

Tulip can be improved to have a lower entry point. Currently, it is a SaaS solution that starts with 10 interfaces minimum, and an interface is a screen where you operate Tulip applications. A lower entry model would allow small to medium enterprises to start using Tulip faster, whereas now Tulip focuses more on big enterprises.

Regarding the technical part, the data model inside Tulip needs improvement. Tulip works with Tulip tables which have a database in the backend, but the user only sees the Tulip tables where they can easily create tables and add new columns. While auditing features exist inside so you can see who has done what inside the table design, one of the shortcomings is relational mapping between tables. One-to-many and many-to-many relations are still quite unclear without the use of primary keys and foreign keys.

I have been using Tulip for two years.

Previously, we primarily built custom software applications for MES use cases. Now we are shifting towards no-code, low-code, and Tulip has been our platform of choice to build MES solutions for our customers efficiently. We also see the benefit for our customers since we have built those first MES applications, and now they are able to continue the development and work themselves using citizen developers. We are also applying a center of excellence strategy and really starting the snowball effect.

We are a partner of Tulip, so we are verified or certified Tulip partners. We buy it directly and sell it directly to our customers.

The time to value is drastically reduced; I would say more than 50 percent. In a typical monolithic project, you start by drafting all the requirements and making an analysis design, and you are easily one or two years further before you see the first results. With Tulip, you start building with very small blocks, and every two or three weeks, you have results. You then iterate faster because you can feel the results, and people become enthusiastic, so they are motivated to continue. Therefore, the time to value is reduced by 50 percent. Additionally, the application life cycle management is embedded in the portal, so you do not have to develop this from scratch, which leads to a total cost of ownership that will be reduced by 30 to 40 percent.

I would rate this review an 8 out of 10.

My main use case for Tulip is that I was the main developer and I am in charge of working with Tulip to implement it in our workstation on the production line, just to be used by the operator.

A quick specific example of how Tulip is used by operators on the production line is that it is used to have the traceability of that specific component or what is the current status of that line, about how many processes we have, how many operators we are running, how much time a specific operation takes, and information about time.

One of the best features that Tulip offers is having a bunch of connections with third-party tools such as ERPs and specific quality tools, just to have correct traceability of what is the concern about one client or something similar.

Those third-party connections, such as with ERPs or quality tools, have helped my team specifically by having a core integration with our ERP provided by Oracle, just to have the production status and how many pieces we build on the production line.

Tulip has impacted my organization positively by having an initial process where we have a reference line that we use to implement Tulip, and it was very useful because Tulip has a bunch of resources in their university.

The specific outcomes I saw after using Tulip are related to KPIs. We did not have anything about what is the process, what is the current time, what is the output. We had a blackboard that we put what is the current status about the production line. So the main purpose that we implemented Tulip was just to have a blackboard digitally implemented in the production line.

Tulip can be improved by implementing more AI features as we are in an AI era, and many features could be implemented thanks to AI.

Regarding the needed improvements for Tulip, regarding integration that you mentioned, because you have a bunch of features of third-party connections, it is not enough.

Tulip is a pretty complete tool just to use at the beginning with MES implementation.

I have been using Tulip for almost two years.

Tulip is stable.

Tulip's scalability is pretty good for having the first application, and if you want to implement improvements in the application, it was pretty easy to implement scalability and new features in that app.

The customer support for Tulip was great.

I did not previously use a different solution before Tulip. It was a legacy tool, and Tulip is the first no-code solution.

It was very easy for my team to learn and adopt Tulip, because Tulip has a university with very useful tools, videos, and articles just to have a complete way. If we have a question, we go there and that is it.

Tulip is pretty customizable for our specific workflows or industry needs because we have various processes, and if we need to customize that process, Tulip provided a very useful way to implement a customized approach.

Tulip helps me monitor and manage compliance requirements in my production environment in a pretty useful way regarding the KPIs and the graphic way, just to have a current status about production status.

Tulip integrates with our existing systems and data sources very smoothly. We encountered one challenge with connection about the ERP that we had, but there was no problem with that.

The user interface and overall user experience for operators and managers in Tulip is intuitive. It is a pretty easy tool for operators to use and for managers, and it was pretty easy to explain how to use.

Tulip helps my team collaborate, share information, or work together in a pretty easy way. We have different environments just to have a correct way, for example, the production, staging, or quality way, just to have the correct version about the app.

Tulip handles updates and maintenance seamlessly for our team. We did not encounter any problems about that.

Tulip supports mobile devices or remote access for my team effectively because they have a mobile version. If you want to implement a mobile or tablet version, we need to build it in the correct way, but it was very easy.

I have seen a return on investment with Tulip. The saved time was a pretty quick way to develop an application.

My experience with pricing, setup cost, and licensing was very easy, but I do not have the status of that because I was not responsible to take that consideration or just to have correct access for that information.

Before choosing Tulip, I did not evaluate other options. We did not have any other solutions to take into consideration, and Tulip was a unique first way to implement applications in our environment.

I chose nine out of ten because it is very useful to have a specific tool in a drag-and-drop tool to have an application in a very quick way. That is the main feature and the main purpose that we had Tulip at my previous work.

Regarding Tulip's AI capabilities, its governance and security were great. We have Tulip on our servers and service in Tulip, and we have a very big security scale implemented in that way.

I do not have the correct answer for Tulip's accuracy and reliability of output because I did not use the AI feature. The version that we had does not have any AI features yet.

My advice for others looking into using Tulip is that if you want to implement Tulip in your environment, you need to take the first certification regarding Tulip. It was pretty easy and useful for me just to have initial steps to implement in our environment. Follow up on the Tulip University path.

It was pretty easy just to implement initial steps in an MES environment.

I rate Tulip a nine out of ten.

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.

My main use case for Tulip is developing apps to digitalize the shop floor by implementing workflows to facilitate current daily operations, connecting system-to-system, and to ERP, making productivity more efficient.

One specific example of how I've used Tulip to digitalize a workflow is the biggest project to make the facility 100% paperless by providing an eDHR application.

Going paperless with the eDHR application has greatly impacted my team's daily work, as you can check records in seconds, instantly on your computer, laptop, or cell phone, and inspect any record that we produce from our product instantly

Tulip has changed my professional life. I started by digitizing a simple inventory process, and over time, I have expanded its use to digitize nearly 100% of our facility’s operations.

Tulip has helped us digitize manufacturing processes, improve traceability, and reduce paper-based documentation. We now have better real-time visibility into production, quality, and downtime, while operators benefit from clearer, standardized workflows. It has also made it easier to connect equipment and systems, automate data collection, and deploy process improvements faster.

Tulip offers numerous best features, as you can implement applications without coding, and if you want to code, there's a way to do it with custom widgets, along with AI tools, dashboards, and many use cases you can implement not just in the production floor, but also in materials, quality, and human resources.

What stands out for me about Tulip's features is that it has its own AI called Frontline Copilot, and you can create agents there, with automations being a particularly exciting feature that allows you to automate transactions between systems.

Tulip has positively impacted my organization as we have developed around more than 300 applications for the shop floor, quality, supply chain and for human resources, allowing managers to consult any data they want, making it a basic part of daily activities.

We have been able to reduce the headcount since there's no longer a need for more people to do manual or traditional transactions on paper because our collaborators use a tablet to make transactions on a real-time basis.

The needed improvements for Tulip are very specific; for example, if there's a function that Tulip doesn't have, it might be very technical and hard to explain.

Tulip has been doing a lot of changes and implementing new features, and whenever I detect something that I want that Tulip doesn't have, they provide a solution, albeit not immediately, but within less than a year—they can implement something we request, especially since we are a medical company that follows LTS releases which happen twice a year.

I have been using Tulip for almost six years.

Tulip is stable; they have a downtime process once per year, but it's infrequent, and they respond by following a very clear SLA to provide immediate support when needed.

The scalability of Tulip is significant, as it can be scaled into many areas, departments, and facilities, and is accessible via mobile phone, laptop, computer, or tablet to view or work with data.

Customer support for Tulip is great; we have an assigned Customer Success Manager who conducts weekly meetings to address our requirements and needs, and we can report bugs directly to him, along with having access to a customer portal for support that follows SLA guidelines for ticket prioritization.

This is the only solution resembling an MES that I have been using so far.

I heard that the company evaluated some other options, but I do not know which ones.

I would say that if you are intuitive and technically inclined, you will learn Tulip very quickly. The implementation was complex at the beginning because nobody knew how to use Tulip, but after a few months, maintaining and expanding the platform became much more straightforward.

We have seen a return on investment as transitioning from a traditional company using paper for manual transactions to a system like Tulip that digitalizes everything results in significant savings, alongside reduced downtime and other efficiencies, although explaining this fully in a short interview is challenging.

Regarding pricing, setup cost, and licensing, it is expensive if viewed merely by cost, but the advantages and inputs you gain are far more than I expected, allowing significant cost reductions through the implementation of Tulip in daily work.

My advice for others looking into using Tulip is to not be afraid of using a new tool because it will truly exceed expectations; Tulip has changed my life, allowing you to do whatever you want with it, making it an excellent choice for innovative individuals.

I believe we are partners with Tulip, but I would say we are primarily just customers, with probably some partnership aspects, yet there is no product relationship between Tulip and the company.

The accuracy and reliability of Tulip's AI output depend on how you handle it and program it, as the agents need specific instructions about the precision desired, necessitating serious iterations to achieve more precision.

Regarding Tulip's AI capabilities, we design our own governance policies internally and need to follow the documentation provided by Tulip due to our status as an FDA-regulated company, which requires adherence to certain policies and governance procedures.

I give this review a rating of 10.

My main use case for Tulip is to build applications for healthcare industries and some product order tracking applications, to work on some HCL internal POCs, and many other applications that I build using Tulip.

Tulip has helped us minimize production manual work and paperwork while storing production data within Tulip tables. The impact has been significant in terms of resource availability and resource consumption regarding paperwork and automation work. Before, we needed many resources to monitor the production control area. Now, with Tulip, we can fulfill requirements and accomplish business objectives with a minimal amount of resources.

Tulip's best feature is the ability to store local data within Tulip tables. Another valuable feature is the ease of use; Tulip is a very handy tool where even no-code resources are able to work with it. Even an operator can work with Tulip.

The impact in terms of resource availability and resource consumption regarding paperwork and automation work has been significant. Before, we needed many resources to monitor the production control area. Now, with Tulip, we can fulfill requirements and accomplish business objectives with a minimal amount of resources.

I suggest that Tulip explore how Ignition provides functionality and add some features that are not currently available on Tulip.

I have been working in my current field for four years.

I have worked on some internal projects which are basic practice projects without any production use cases.

Tulip's governance and security are good.

There are no improvements needed for Tulip.

In terms of integration and analytics, I do not see any other special features that Tulip provides that other modern market solutions do not provide, such as Ignition, Siemens Opcenter, and many other applications. I have not explored Tulip's AI offerings. I did not work on the pricing, setup cost, and licensing as these are managed by the sales team. My review rating for Tulip is 7.6 out of 10.

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.

My main use case for Tulip involves working in the pharmaceutical domain on projects, where I have worked on multiple projects, including the main project which was the EBR, electronic batch record, where I have created multiple applications from scratch.

For the EBR project, I have built several applications, including primary packaging, secondary packaging, calibration, cleaning, and one or two more applications, though I forgot the names.

Mainly I have used applications for the pharma domain only, but I have also updated several applications which are already built in Tulip with the help of new features, such as changeover application, defect management application, and CIL and CLM, center management system application. These applications I have also updated and deployed to multiple sites.

Tulip offers great features such as being very quick in creating applications as it does not require any specific coding skills. It is a block-based application where I can add blocks, and for storing tables, it has tables. Tulip now includes AI and automation features which add more user-friendly elements, allowing automation to run for specific times based on conditions, even if I am not running the application. For AI, it helps me develop applications more quickly.

Regarding AI features, I find that Tulip now includes AI translation, enabling any text I write to convert to the particular language I want, whether it is Chinese, German, or Spanish. Additionally, I can capture information from images in specific fields and extract data from tables regarding past activities and KPIs, making it very versatile. For automation, if someone needs to create weekly tasks every Monday, I can automate this so that on Sunday morning at a specific time, the automation creates the task and assigns it to particular users for the entire week or any specific time.

Tulip also has another great feature called connectors, which allows me to send and receive data from Tulip to other systems easily by adding APIs to specific fields. Moreover, Tulip features dashboards similar to Power BI, which are important for visualizing data, making it a valuable feature as well.

Implementing Tulip has positively impacted our organization as we have transitioned from paper MBR and EBR to Tulip's online MBR, significantly reducing the time operators spent manually documenting activities, which also made audit trials easier to manage. Now I can see the batch process, track user activities more efficiently, and check audit trails, saving time and speeding up the overall process.

Regarding the weighing application, where users had to weigh samples and document all related information, I found that after using Tulip, we have saved approximately thirty percent more time on the specific weighing task alone.

There are several improvements that Tulip currently misses. For example, if I have a button, I cannot change its name as a variable. If the button name is "confirm," I am confined to a static value. If I could add variables so the button name can change based on conditions, that would be very helpful.

Additionally, I notice Tulip provides courses and videos in Tulip University, but some features are not covered. I would like to see more videos about Tulip features for first-time users to learn how to utilize them. Moreover, there is currently a lack of a specific widget that functions as a looper, and for automation, the lowest frequency can only run hourly. In one application, a five-minute frequency is needed, which is not possible at the moment, so reducing the lowest frequency option for automation would be another improvement.

Regarding Tulip's AI capabilities, I perceive that it is not yet mature and is still in the testing phase, with several features rolled out for end users. I believe Tulip's AI is in its earliest stages, but I am hopeful that future updates will introduce additional features. For security aspects, I find it acceptable since I have not encountered any significant issues; its limitations are quite minimal at this point.

I have been working as a Tulip developer for the last five years.

Tulip is stable.

Tulip's scalability is excellent; adding new applications, users, and roles is straightforward and only takes about five minutes to complete.

The customer support is very good and quick. Usually, when I inquire about functionality or errors within the application, I receive responses within twenty-four hours, and they are effective in handling tickets and explaining issues.

For the customer support experience, I would rate it nine out of ten regarding issue resolution, but I would rate timely responses an eight out of ten.

I have not used any other solution other than Tulip.

I have worked as a Tulip developer but also examined other applications like Mendix. However, I found it somewhat challenging due to its cluttered UI and overwhelming number of options. In contrast, Tulip is neat and clean and very easy to understand in terms of functionality.

My advice for others considering using Tulip is to go for it, especially if you lack coding experience; it offers an easy, time-saving application development process, making maintenance and updates straightforward in the future for additional users or application changes.

I would emphasize that Tulip is a fantastic application with many new features and applications available. Tulip's library functions are especially useful as users can download applications from the Tulip library, modify features, and begin using them without needing to build from scratch. I would rate my overall experience with Tulip an eight out of ten.