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.

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.

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.

Tulip is a Manufacturing Execution System designed to understand requirements and convert them into technical requirements. Lab processes that happen inside manufacturing systems can be translated directly into technical requirements within Tulip. Although other tools exist in the market, Tulip is one of the easiest to learn and is very user-friendly for anyone to use, even without development information or software experience. It is a no-code development platform.

One business process for a client involved reducing the burden on report formats that they generally used to generate manually through their local computers. Through Tulip, this is possible. It allows you to generate reports directly from your desktop. With the processes that you have already integrated, it also calculates the necessary items that are required for the reports to be generated correctly. These lab processes already need to be registered into Tulip and these processes need to be followed for successful report generation.

Tulip use cases include digitalizing your shop floor processes, connecting machines, and improving production visibility. Digital work instructions replace paper-based SOPs with interactive instructions that display images, videos, and checklists while ensuring that operators follow the correct sequence. Electronic batch records help you digitally capture manufacturing steps, record operator actions, timestamps, and material usages. All of these items are very important for simplifying regulatory compliance with FDA and GMP. Quality inspections allow you to perform in-process and final inspections, record measurements and defects, and automatically flag any out-of-specification values. Real-time dashboarding shows production counts, downtime, and shift performance. You can connect PLC sensors, barcode scanners, and IoT devices directly with the software to monitor machines. Traceability and genealogy tracking allows you to track your inventory and material inside the MES using barcode or QR code scanning. Work order management and material consumption tracking prevent the use of expired or incorrect materials. Audit and compliance features ensure that you have electronic records instead of paper, time-stamped operator actions, and electronic approvals, which could simplify FDA, GMP, and ISO audits.

The best features in Tulip are the no-code and low-code capabilities because you don't need a lot of experience in handling or establishing a business requirement to convert it into a technical requirement. Tulip is a no-code app builder that manufacturing engineers with no background in software development can easily use to operate, create operator apps, digital work instructions, and workflows without writing code. This can significantly reduce the dependencies on software engineers. Machine and IoT connectivity allows you to connect PLC sensors and barcode scanners, as well as instruments such as weighing balances and legacy equipment that can be used with edge devices and drivers. Open APIs automate data collection. Real-time dashboarding is another valuable feature that allows you to check all the data directly from Tulip's interface. These are very important items that are required for any MES tool to have.

Integration between other systems, such as SAP and ERP, or the ability to connect MES to LIMS databases through REST APIs, allows Tulip to fit into an existing manufacturing ecosystem.

Tulip can do a lot better in user interface. It is not complex, but it is rather not too simple. The user interface could be improved to make it more accessible to people and to market that product more effectively in the open market.

I have used Tulip for about six to eight months.

Tulip is very stable in my experience.

Tulip can be scaled at the best, like any other platform. It can be scaled to multiple users and multiple developers.

Customer support is great.

The client recommended that we use Tulip since it was cheaper in the market compared to other tools.

Other MES tools were evaluated as well. Other MES tools that could be compared with Tulip include Rockwell Automation and Honeywell's tools.

The most important aspect is the no-code and low-code capabilities, which I really appreciate from the platform as a whole.

If your organization has a small number of low-code or no-code developers, or people who don't have knowledge on how to create an application or integrate complex MES tools with Tulip, the platform can definitely reduce the effort and time spent on hiring particular developers for this tool. This would directly result in creating less pressure on the work environment. Tulip reduces paperwork because you no longer have to maintain multiple Excel files, Word documents, and PDFs. All of those items can be eliminated directly with digital workflows. It can improve productivity by having operators receive step-by-step digital instructions and allowing supervisors to spend less time searching for SOPs. Product quality is better because mandatory checks prevent operators from skipping critical steps. All of these items are very important steps in manufacturing execution systems and in business processes of manufacturing items that are generally produced in large-scale organizations.

Organizations should start using Tulip as soon as possible. It is the best tool right now for MES with a no-code and low-code platform. It has many capacities and capabilities like any other MES tools. I would rate this product an 8 out of 10.

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.