Technology Category
- Application Infrastructure & Middleware - Data Exchange & Integration
- Platform as a Service (PaaS) - Application Development Platforms
Applicable Industries
- Pharmaceuticals
Applicable Functions
- Maintenance
- Product Research & Development
Use Cases
- Onsite Human Safety Management
- Visual Quality Detection
Services
- Cloud Planning, Design & Implementation Services
- Testing & Certification
About The Customer
EQRx is a biotech company headquartered in Cambridge, Massachusetts, United States. Launched in 2020, the company has a mission to make innovative medicines available at radically lower prices. To achieve this, EQRx needed to build a modern development platform that could align cross-functional business processes and deliver efficiency at scale. The company is a trailblazer in the pharmaceutical industry, implementing a modern development platform across various departments in a short span of time. EQRx is committed to continuous improvement and has a strong governance framework to ensure the right decisions are made for the company as a whole.
The Challenge
EQRx, a biotech company based in Cambridge, Massachusetts, was launched in 2020 with the ambitious mission of making innovative medicines available at significantly lower prices. To achieve this, the company needed to build a modern development platform that could align cross-functional business processes and deliver efficiency at scale. The platform needed to meet the company's requirements for minimal custom development, sustainable total cost of ownership, and productized integrations to reduce maintenance and complexity. The challenge was to implement this platform across various departments including clinical data, clinical operations, quality, regulatory, and safety in a short span of time.
The Solution
EQRx selected Veeva Development Cloud as the operating system for product development activities. The connected platform with unified suites of applications met the company’s requirements. EQRx implemented 13 Vault applications across various departments in just under 12 months. The company’s three-phase journey began by laying the foundation for growth with essential builds of Vault applications, followed by the integration of systems and data at critical touchpoints. The third phase involved creating seamless, contextual user experiences with the right data available in the right systems at the right time. EQRx took an agile approach to implementing Veeva Development Cloud, assessing, optimizing, and releasing feature enhancements in recurring cycles of continuous improvement. A strong governance framework focused stakeholders on creating a common, end-to-end platform to optimize cross-functional business processes.
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.