‘Ship-Shape’ Management of Active Pharmaceutical Ingredient (API) Stock and Shipments at Debiopharm
Company Size
200-1,000
Region
- Europe
Country
- Switzerland
Product
- Dotmatics solutions
- Dotmatics Cascade-based system
Tech Stack
- Web-based platform
- Data migration
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Digital Expertise
- Productivity Improvements
Technology Category
- Analytics & Modeling - Data-as-a-Service
- Platform as a Service (PaaS) - Data Management Platforms
Applicable Industries
- Pharmaceuticals
Applicable Functions
- Product Research & Development
- Quality Assurance
Use Cases
- Inventory Management
- Supply Chain Visibility
Services
- Data Science Services
- System Integration
About The Customer
Debiopharm International SA is a pharmaceutical company that specializes in drug development, particularly in the areas of oncology and bacterial infections. The company has over 400 employees and operates two sites in Lausanne and Martigny, Switzerland. Debiopharm also works with numerous global Contract Research Organizations (CROs) partners. The company uses Dotmatics solutions for various purposes, including reagent registration, stock management, electronic lab notebooks (ELN), API chemical registration, DPM assignment, analysis/results sharing, API stock/shipment management, and analytical lab analysis requests. Debiopharm's goal is to deliver new therapies to patients faster.
The Challenge
Debiopharm, a pharmaceutical company, was facing challenges in managing its Active Pharmaceutical Ingredient (API) stock and shipments. The company synthesizes compounds at internal labs and at numerous Contract Research Organizations (CROs). Similarly, analysis is done both internally and at specialty CROs around the world. With so many stock movements, there was a risk of error. The company was looking for a solution that could provide real-time, accurate account of shipped samples and remaining stock, streamline the request and fulfillment process, and offer real-time tracking of stock sent to Debiopharm sites and between CROs.
The Solution
Debiopharm collaborated with Dotmatics to implement a centralized research-data platform that united data from all sites and CROs, streamlined workflows, and improved decision-making. Dotmatics configured an API stock and shipment system for Debiopharm using its solutions for inventory management, lab requests, and web-based searching and reporting. The inventory system tracks all inventory, including incoming stock synthesized by both in-house scientists and CRO partners, as well as outgoing stock being sent internally or between CROs. A simple form takes researchers’ detailed API requests and sends them to directly inventory managers for fulfillment. An interactive inventory summary report lets all users see details around a particular compound’s history, such as current sample availability, associated batches, and request and shipment history.
Operational Impact
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
Case Study: Pfizer
Pfizer’s high-performance computing software and systems for worldwide research and development support large-scale data analysis, research projects, clinical analytics, and modeling. Pfizer’s computing services are used across the spectrum of research and development efforts, from the deep biological understanding of disease to the design of safe, efficacious therapeutic agents.
Case Study
Fusion Middleware Integration on Cloud for Pharma Major
Customer wanted a real-time, seamless, cloud based integration between the existing on premise and cloud based application using SOA technology on Oracle Fusion Middleware Platform, a Contingent Worker Solution to collect, track, manage and report information for on-boarding, maintenance and off-boarding of contingent workers using a streamlined and Integrated business process, and streamlining of integration to the back-end systems and multiple SaaS applications.
Case Study
Process Control System Support
In many automated production facilities, changes are made to SIMATIC PCS 7 projects on a daily basis, with individual processes often optimised by multiple workers due to shift changes. Documentation is key here, as this keeps workers informed about why a change was made. Furthermore, SIMATIC PCS 7 installations are generally used in locations where documentation is required for audits and certification. The ability to track changes between two software projects is not only an invaluable aid during shift changes, but also when searching for errors or optimising a PCS 7 installation. Every change made to the system is labour-intensive and time-consuming. Moreover, there is also the risk that errors may occur. If a change is saved in the project, then the old version is lost unless a backup copy was created in advance. If no backup was created, it will no longer be possible to return to the previous state if and when programming errors occur. Each backup denotes a version used by the SIMATIC PCS 7 system to operate an installation. To correctly interpret a version, information is required on WHO changed WHAT, WHERE, WHEN and WHY: - Who created the version/who is responsible for the version? - Who released the version? - What was changed in the version i.e. in which block or module of the SIMATIC PCS 7 installation were the changes made? - When was the version created? Is this the latest version or is there a more recent version? - Why were the changes made to the version? If they are part of a regular maintenance cycle, then is the aim to fix an error or to improve production processes? - Is this particular version also the version currently being used in production? The fact that SIMATIC PCS 7 projects use extremely large quantities of data complicates the situation even further, and it can take a long time to load and save information as a result. Without a sustainable strategy for operating a SIMATIC PCS 7 installation, searching for the right software version can become extremely time-consuming and the installation may run inefficiently as a result.
Case Study
Drug Maker Takes the Right Prescription
China Pharm decided to build a cloud-based platform to support the requirements of IT planning for the next five to ten years which includes a dynamic and scalable mail resource pool platform. The platform needed to have the following functions: all nodes support redundancy, ensuring service continuity and good user experience, simple and easy-to-use user interfaces for end users and administrators and good compatibility and supports smooth capacity expansion.
Case Study
ELI LILLY ADOPTS MICROMEDIA’S ALERT NOTIFICATION SYSTEM
Pharmaceutical production is subject to a strict set of enforced rules that must be adhered to and compliance to these standards is critically necessary. Due to the efforts of WIN 911’s strategic partner Micromedia, Lilly was able to adopt an alarm notification infrastructure that integrated smoothly with their existing workflows and emergency hardware and protocols. These raw energy sources enable the industrial process to function: electricity, WIN-911 Software | 4020 South Industrial Drive, Suite 120 | Austin, TX 78744 USA industrial steam, iced water, air mixtures of varying quality. Refrigeration towers, boilers and wastewater are monitored by ALERT. Eli Lilly identified 15000 potential variables, but limitations compelled them to chisel the variable list down to 300. This allowed all major alarms to be covered including pressure, discharge, quantity of waste water discharged,temperature, carbon dioxide content, oxygen & sulphur content, and the water’s pH.
