Pharmaceutical, biopharmaceutical, and medical devices companies turn to Tulip for use cases spanning training, work instructions, line clearance, logbooks, history records, quality control, and batch/device release. With newly released GxP features in the Tulip platform, it is easier than ever for manufacturers subject to regulatory compliance to take advantage of digital transformation.

The Tulip Platform includes prebuilt apps that you can use to understand the ins and outs of the platform for that use case and how easy it is to get started with building no-code apps in GxP environments. Videos from Giovanni Carrara, our Community Lead at Tulip, will give you a firsthand look at the platform in action by exploring these apps.

Let’s take a look at an equipment logbook app. This digital application was built using the Tulip platform and takes advantage of several features designed specifically for GxP environments.

When completing a cleaning task, a technician can use this app to report cleanings performed on specific pieces of equipment or particular a room.

https://cdn.brandfolder.io/GDDASP4K/at/4s76jcnvcmffrpz25hf33jb/image1-6-768x507.png
Home Screen on a Cleaning Logbook App

The app records a logbook of all the cleanings that have occurred on a given piece of equipment including:

  • When the cleanings were performed
  • Who performed the cleanings
  • What equipment/room was cleaned

In the app, the end-user also has the option of updating the cleaning records and viewing history records. More on that below.

To begin recording a new cleaning, technicians are shown a screen prompting them to enter information.

https://cdn.brandfolder.io/GDDASP4K/at/g3xztwbphqvg56jqmwjf7fjn/image7-1-300x198.png
Input Information Step on a Cleaning Logbook App

The end-user can select what is being cleaned and the solution that is used, while the app captures information in the background. This example app displays the time elapsed and the current user, but you can configure the app to include more information if you need to. Furthermore, you can also ask the technician to take a photograph of the piece of equipment, once it’s been cleaned.

After clicking “record new cleaning”, end-users will be prompted to enter their credentials, such as their username and password. This way the assigned user can be accurately linked to their cleaning work order.

https://cdn.brandfolder.io/GDDASP4K/at/g3xztwbphqvg56jqmwjf7fjn/image7-1-300x198.png
E-Signature Step on a Cleaning Logbook App

Once the end-user submits their credential, the cleaning data is automatically recorded and uploaded into the logbook.

To modify a log, the end-user can go into a table, select the logbook that they want to change, and then find the log to modify. Upon updating the cleaning record, end-users will be prompted to enter their credentials again, ensuring the change is associated with the end-user who is executing the app.

To see these steps and the logbook in action, check out this video.

To see how the app was built in the Tulip app editor, watch this video.

To get started with a logbooks app on your own, visit our template app in the Tulip Library.

The next blog in this series will look at the History Widget in Tulip. If you want to learn more about the future of life sciences manufacturing, we recently hosted an event with industry experts full of presentations, panels, and roundtable discussions. You can view the event recordings here.

If you want to learn about how Tulip can be implemented in your operation, contact us.