AstraZeneca Implements Veeva CRM for Enhanced Functionality and Cost Savings
Customer Company Size
Large Corporate
Region
- America
Country
- United States
Product
- Veeva CRM
Tech Stack
- .Net
- Cloud Computing
- SaaS
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Cost Savings
- Productivity Improvements
Technology Category
- Infrastructure as a Service (IaaS) - Cloud Computing
- Platform as a Service (PaaS) - Connectivity Platforms
Applicable Industries
- Pharmaceuticals
Applicable Functions
- Sales & Marketing
- Business Operation
Use Cases
- Predictive Maintenance
- Remote Asset Management
- Supply Chain Visibility
Services
- Cloud Planning, Design & Implementation Services
- System Integration
About The Customer
AstraZeneca is a global, innovation-driven biopharmaceutical business that primarily focuses on the discovery, development, and commercialization of prescription medicines. The company is a leader in several medical fields, including gastrointestinal, cardiovascular, neuroscience, respiratory and inflammation, oncology, and infectious disease medicines. In 2009, AstraZeneca generated global revenues of $32.8 billion. In the United States, AstraZeneca is a $14.8 billion healthcare business.
The Challenge
AstraZeneca's Medical Affairs team was initially satisfied with its custom-built, on-premise, .Net CRM system. However, over time, the system's functional limitations, high maintenance requirements, and escalating costs became increasingly problematic. The team needed a more robust system with enhanced reporting, planning, and management functionality. The new system also needed to facilitate collaboration with other AstraZeneca teams, partners, and external resources. Furthermore, the new system had to demonstrate its ability to decrease system maintenance effort and cost, increase system flexibility and usability, reduce the time required to make changes, increase scalability, ease system collaboration with partners, improve user productivity and performance, integrate easily with external data sources, and improve reporting efficiency.
The Solution
AstraZeneca conducted an extensive vendor analysis, evaluating both on-premise and SaaS options. After a five-month review process involving a committee of managers, users, and technology staff, AstraZeneca selected Veeva CRM. The implementation of Veeva CRM took less than three months and was completed on time and under budget. The new system has proven to be extremely intuitive and easy to use, with users requiring only one online training session. Veeva CRM allows AstraZeneca to make changes as often as needed, and the company also benefits from Veeva’s nonstop innovation with transparent system upgrades that are automatically delivered every 120 days.
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
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.