Customer Company Size
Large Corporate
Region
- Europe
- America
Country
- Germany
- United States
Product
- Domo Data Science
Tech Stack
- Data Analytics
- Data Science
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Customer Satisfaction
- Digital Expertise
Technology Category
- Analytics & Modeling - Data-as-a-Service
Applicable Industries
- Pharmaceuticals
Applicable Functions
- Sales & Marketing
- Business Operation
Use Cases
- Predictive Quality Analytics
Services
- Data Science Services
About The Customer
Grünenthal is a global leader in pain management, dedicated to creating and delivering life-changing medicines to more than 100 countries across Europe, the United States, and Latin America. The company has 4,500 employees and generates a revenue of €1.5 billion. Grünenthal's mission is to meet the needs of patients and caregivers with confidence. However, due to patient privacy regulations, the company was struggling to understand its customers and their needs.
The Challenge
Grünenthal, a global leader in pain management, was struggling to understand its customers due to patient privacy regulations. The company lacked customer data, making it difficult to know what customers thought about its products and marketing strategies. This lack of data led to a culture where decisions were made based on gut feelings rather than concrete data. Grünenthal needed a solution that would allow it to overcome its data challenges and change its culture.
The Solution
Grünenthal decided to conduct a short pilot project with Domo to test its capability. Working with Domo’s team of data consultants, Grünenthal was able to launch a dashboard within two weeks, and do data science reveals in less than two months. Based on the success of the pilot, Grünenthal has since rolled out a consistent set of advanced analytics and dashboards to offices across 19 different countries in under a year. This has put insights into the hands of the people on the ground who are making decisions on a daily basis. Grünenthal also worked with the Domo team to create a best-in-class data science operation.
Operational Impact
Quantitative Benefit
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
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.