Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Inside SAP Cloud ERP

Inside SAP Cloud ERP artwork

Inside SAP S/4HANA Episode 84: How Roche Manages Real-Time Shipments and Temperature Control in Clinical Supply

Mar 22, 202313 minAudio
ShareXLinkedInFacebookWhatsAppEmail

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Hi, everyone, and Welcome to our episode. 84 where we will talk about how Rush monitors real-time shipment and Temperature Control in clinical Supply. To answer this question, I'm honored to have a special guest on the show today. Let's work on guia De Boracay, to product manager for Clinical and API supply chain from Rush agita. How you doing today? Hello, Marcus good to see you. I'm well and excited to take part in this podcast. Thanks for being here and let's

start right into the subject agita. What does monitoring real-time shipments and Temperature Control in clinical Supply mean, how can our audience Envision the processes and what are the legal requirements? Let me answer this question in two parts. The why? And the what? So first monitoring temperature? During transportation in the clinical Supply is the same process as in a lot of other Industries in a nutshell. We must ensure that our products

are exposed to the temperatures inside of the allowed range. That is ambient product should not be frozen or heated and cool chain products must maintain their low temperatures. However, there are several additional aspects that we must consider in the clinical Supply. First is Pharma, industry is highly regulated. So we must ensure that our clinical products reach the patients in the intended, State

and safety Second clinical product have relatively short shelf life. As these are new medications and they are not yet approved and often the stability studies are still ongoing Third, any potential deviation in terms, of temperature is a reason to discard the product. This, of course, minimizes the risk for the patients. And at the same time, is costly for the company.

Lastly, clinical shipments are usually going directly to the hospitals. So let's say, the difference is that in a regular supply chain a wholesaler or other professional storage facility, is usually equipped, To keep the required conditions and to end public institutions, like hospitals, might have a variation in handling the products and knowing these conditions that they are exposed to their is especially important. So now the second part, what do

we do about it before the implementation of the smart sensors in Rush clinical Supply, we relied on the traditional temperature monitoring either time-based where the product should arrive within the Find number of hours or we had USB loggers with the local storage. Given the reasons I mentioned in the first part. It was not enough, the old methods. And last year we went live with implementation of smart sensors. So how does the process look

like in the first step? In the warehouse deliveries being picked? Backed and paired with a small physical device, which we call a smart logger, and this device is put into a shipping box as a Step, they're also printing special pairing. She to about the information. What logger is inside of that box? And also a QR code that I will come back to later. Then our year p is triggering the interface to the cloud

application, where we send the very high delivery data source, destination addresses, then we ship this box. And then, as the last step, the delivery arrives at the hospital, the medical Cool workers taking the pairing sheet scans, the QR barcode. And this link is then providing the temperature report and the person in the hospital can download it and file it, which is a regulatory requirement.

So, to wrap up the first question with this processor ocean. Clinical investigation sites have the temperature information for the whole duration of the shipment as compared to the previous methods. And this ensures that our shipments are handled in required conditions not only during Transportation but also at the receiver side which consequently is also safe medications to the patients. Maybe we go more into the implementation and if I would be another sap customer operating

in clinical Supply, and I would call you up and ask you. So, tell me a little bit more about the software and Hardware, I would need to implement Your solution. What would you tell me? So the basic kit for real-time temperature monitoring during shipping consists of two parts. First, you need the smart device that collects the temperature then data and sends the real time to the cloud application. And second you need the cloud-based software to collect this data with the front-end to report.

However, the real benefit comes if you integrate this process into your supply chain and especially the quality decision making software. For that, you would need three additional elements. First Integrations between the companies Erp and Cloud vendor systems. Second logger report repository that is a database to store the temperature reports about each shipment. In our case, it can be accessed by Rush as well as by the

hospital's via QR code. And the last useful tool is a power bi for reporting and data visualization. You mentioned that you're using a cloud-based supply chain, monitoring tool, or solution. Even a cold chain as a service solution, Section of my hair that cloud is not suitable and regulated environments where their concerns before the project started. Maybe you can elaborate a little bit on that, you're absolutely right Marcus data. Safety was a key Topic in our project so generally data is

especially sensitive and clinical studies, as some Studies have blinded setup that is some drugs are pills with active pharmaceutical ingredients and some are placebos. It is called double blinded because neither patient nor Hospital must know which is which therefore any unblinded information related to materials batches. It's absolutely to be avoided to be leaked or sent to other systems especially Cloud

systems. In our case we built, we got created for architecture and we used it to allow to send only the basic data to the cloud about the delivery header. So to say so that we have the relationship between the liver and logger, but do not send the sensitive information on materials and batches. In case of temperature deviation, our middleware is receiving the data from the

cloud and then is proactively pulling the required detailed information from the Erp. And then it collects this data into one bag and this forwarding to our quality decision-making system. In this way, we're keeping the confidential information within the rush Network. Very good Ghidorah if you look back on the whole project but we're the biggest Lessons Learned.

And what would you pay attention to a while implementing today, or if you would have to do it again I would like maybe to mention three takeaways First is the close collaboration with your Cloud device supplier. Now a project, the devices got a new software upgrade while when the system was already live and it took agile problem solving, and real-time communication between Russia and device supplier to make it seamless for

the supply chain. The second point is be creative in your architecture. As I And before for data, security reasons, we needed to find a solution to send only the generic data to the cloud, keeping the sensitive data inside and we used the middleware for that. The last point, it's important to have a team in place, that customers can contact. The in case of any issues with Device or report, it is especially important in the

beginning when the sides are learning. How to use the loggers and need to fast and easily accessible support. I would say not only reduces the errors but also has this effect of building trust with the customers. I know you're very creative person and cool to see that your arms are creative at rush and was a really surprised like a personal surprise for you as well. Yeah. What surprised me personally is that the Power of Habit should

not be underestimated. The process with the smart log as was greatly simplified in comparison with the old process. So the receiving side has only to scan the QR code and gets directly forwarded to temperature report that easy. However, I was surprised that some customers have explicitly preferred, the old and more time-consuming process where you would attach the device to the USB, download print and so on

Old Habits for never Estimated right, Deidre and private life. And in business, I completely agree. Can you or I allowed to talk about the return of investment after implementing Your solution or operational improvements? I would say that the biggest improvements were in increased supply chain transparency and quality assurance. So for the absolute majority of shipments, luckily, we have no temperature excursions. And with the data available now,

from the smart sensors, we could automate the quality release of these transports, which highly reduced effort for the quality department and for the deliveries, that did have an Excursion. We were able to see not only that temperature Excursion happened, but also where it happened as the divides records also geolocation and this allowed us to identify. Parts of the supply chain where the temperature excursions happened and address them with

the transport providers, or even sites in in hospitals, for example, improper storage at the receiving end. So what's up with the future? Let's talk about the future. Are there any plans or further plans to enhance your cold chain processes? Absolutely, we do have plans for the future. So the biggest plan is we're moving the solution to as for Hannah. Within next year, we also plan to expand the network where we use the smart sensors in geographical terms to use it in

more countries, more Depots. And the last one is that we plan to connect more quality relevant systems that store, for example data, about product stability, and enhance the data quality for the monitoring reasons, The sounds great. I see a great future for you and for us and I'm happy you decided for sap as for Hannah. Yeah. I think I'm giddy, we could talk forever.

But I think, for time reasons, I think this is a good point. Maybe to stop this episode on. Hopefully, you will be a future guest on the show as well. Talking about the sap as for Hannah implementation, and thank you so much for sharing your knowledge today. Qiblah, Thank you, Marcus for having me. It was a real pleasure listening to you. So I hope you like this episode. As much as I did, as always feel free to drop us an email or via inside as for at recipe.com and let us know which topics are of

your interest tune in next time and be inside as a p as for Hannah.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. TechEd #10: How Joule Studio and n8n Orchestrates Enterprise AI

    Nov 20, 202616 minAudio

    Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP gets into one of the most significant partnerships in the SAP ecosystem right now. Host Yannick speaks with Vladimir Shakhov, Strategic...

    • Apple Podcasts

    Credit the people on this episode

  2. TechEd#9: How AI Transforms Cloud ERP Migrations

    Nov 18, 202614 minAudio

    Recorded live at SAP TechEd 2026 in Berlin, this episode takes a refreshingly grounded, practitioner-first look at what AI in SAP really means in the field today. Host Fernanda speaks with Wouter Lemaire, independent...

    • Apple Podcasts

    Credit the people on this episode

  3. TechEd #8: The Benefit of Laying the Groundwork for AI

    Nov 16, 202615 minAudio

    Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP brings something the series hasn't had yet: the perspective of an actual large enterprise customer architect, not a consultant or partner....

    • Apple Podcasts

    Credit the people on this episode

  4. TechEd #7: The Hidden Risk in Every SAP Transformation — Organizational Change Management

    Nov 13, 202618 minAudio

    Recorded live at SAP TechEd, this episode of Inside SAP Cloud ERP zooms in on the dimension of SAP transformations that gets the least attention - and causes the most damage when ignored: Organizational Change...

    • Apple Podcasts

    Credit the people on this episode

  5. TechEd #6: Five Days to a Working AI Solution — Inside SAP's Forward Deployed Engineering Model

    Nov 11, 202623 minAudio

    Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP gets to the heart of what the autonomous enterprise actually looks like when it's working. Host Yannick speaks with Sindhu Gangadharan,...

    • Apple Podcasts

    Credit the people on this episode