Download PDF
VEEVA SUCCESS STORY Mundipharma Spain
Technology Category
- Functional Applications - Enterprise Resource Planning Systems (ERP)
Applicable Industries
- Pharmaceuticals
Applicable Functions
- Sales & Marketing
Services
- Cloud Planning, Design & Implementation Services
- Training
The Challenge
Mundipharma sales representatives had been relying on an antiquated customer relationship management (CRM) system that had very limited functionality and was difficult to integrate. Outside of call reporting and expense recording, the on-premise CRM system didn’t meet Mundipharma’s growing needs, especially as it set out to launch a new analgesia product. The company had a manual system where all of their sales information, including physician lists, budgets, call tracking, and customer profiles, was stored in different areas. This forced reps to seek out all of that data to build their own lists and reports – a highly inefficient process. Mundipharma needed a modern solution that would better support their sales team and administrators.
About The Customer
Mundipharma and its independent associated companies are committed to improving the health and quality of life of people everywhere. Over the last 50 years, their associates have become leaders in pain management, developing new drugs and patented formulations to relieve chronic pain for patients and to help them improve their lives. Mundipharma also have a strong presence in onco-hematology treatments to help transform the lives of even more patients.
The Solution
Mundipharma began the search for a new CRM solution, narrowing it down to three options from leading CRM providers. After carefully reviewing the technology and testing the usability of all three systems with the sales team, Veeva proved the frontrunner. Plus, Veeva promised it could install the system, have it operational and train all users within Mundipharma’s tight timeframe of three months. Within six weeks, Mundipharma implemented Veeva CRM across several business units, including analgesics and oncology. The company was shocked, but what surprised executives even further was how quickly its users were trained. In less than two hours, more than 50 sales representatives had been completely trained on Veeva CRM and were prepared to use the new system for day-to-day operations.
Operational Impact
Quantitative Benefit
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.