公司规模
Large Corporate
地区
- Europe
- America
国家
- Germany
- United States
产品
- Domo Data Science
技术栈
- Data Analytics
- Data Science
实施规模
- Enterprise-wide Deployment
影响指标
- Customer Satisfaction
- Digital Expertise
技术
- 分析与建模 - 数据即服务
适用行业
- 药品
适用功能
- 销售与市场营销
- 商业运营
用例
- 质量预测分析
服务
- 数据科学服务
关于客户
Grünenthal 是疼痛管理领域的全球领导者,致力于为欧洲、美国和拉丁美洲的 100 多个国家/地区创造和提供改变生活的药物。该公司拥有 4,500 名员工,收入达 15 亿欧元。Grünenthal 的使命是满怀信心地满足患者和护理人员的需求。然而,由于患者隐私法规,该公司很难了解其客户及其需求。
挑战
Grünenthal 是疼痛管理领域的全球领导者,由于患者隐私法规的限制,该公司很难了解客户。该公司缺乏客户数据,因此很难了解客户对其产品和营销策略的看法。缺乏数据导致了一种基于直觉而非具体数据做出决策的文化。Grünenthal 需要一种解决方案来克服数据挑战并改变其文化。
解决方案
Grünenthal 决定与 Domo 合作开展一个短期试点项目,以测试其能力。通过与 Domo 的数据顾问团队合作,Grünenthal 在两周内推出了一个仪表板,并在不到两个月的时间内完成了数据科学展示。基于试点的成功,Grünenthal 在不到一年的时间内向 19 个不同国家的办事处推出了一套一致的高级分析和仪表板。这让每天做出决策的实地人员能够获得洞察力。Grünenthal 还与 Domo 团队合作,创建了一流的数据科学运营。
运营影响
数量效益
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
相关案例.
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.