Jazz Pharmaceuticals: Data Enablement & Analytics

Global Biopharmaceutical Enterprise Focused on Neuroscience and Oncology

Consolidates Data Across All Systems of Record in Near Real-Time.

Jazz Pharmaceuticals is an innovative pharmaceutical enterprise generating medicines to support patients with neurological concerns such as epilepsy, multiple sclerosis, excessive daytime sleepiness, and oncology diseases such as leukemia and lung cancer. Data is crucial in developing, testing, and manufacturing these critical medicines. Salesforce is one of the key systems of record leveraged by the enterprise; however, other locations also generate data. CapStorm powers near real-time integration of critical Salesforce data into Jazz Pharmaceuticals’ global data fabric to streamline analytics and eliminate data silos.

 

 

 

 

 

Graphic of a cog in the CapStorm blue color.

Industry

Icon of a person's silhouette in CapStorm blue.

Company Size

Puzzle piece icon in the CapStorm blue color.

Specialities

Icon representing tech stacks in the CapStorm blue color.

Tech Stack

Blue, black and white cubes floating and falling.

Problem

The organization needed to analyze data across all core systems of record, including Salesforce.

This 20-year-old enterprise selected AWS as the core cloud storage platform for data critical to daily operations. The business uses Salesforce for sales enablement and automation in addition to marketing. The company also leverages various other platforms to maintain complex business operations across 13 global offices in 8 distinct countries. As a result, the enterprise needed a secure method to replicate Salesforce data into the AWS platform in high-frequency increments to power analytics and to integrate data generated in Salesforce into non-Salesforce systems.

Solution

    1. High-Frequency Data Integration

      CapStorm enabled high-frequency replication of each Salesforce Production Organization’s data. These data extracts ran every 2 hours, allowing near real-time data ingestion and integration into the enterprises’ global data fabric. Each Salesforce backup was incremental, meaning replications only occurred for added or modified records. This process minimized the number of Salesforce API calls for optimal resource use. The solution also enabled field history tracking with no limits on the number of fields included or retention of the data changes. These field changes enabled unlimited historical trend reporting for deep business intelligence, improving the business’ forecast ability.

    2. Automatic Schema Mirroring

      The CopyStorm application by CapStorm replicated Salesforce data and metadata in addition to Salesforce schema. These replicas of Salesforce automatically picked up Salesforce data model changes, meaning the automatic addition of new objects, fields, or managed packages to the integration without manual intervention. Automatic schema mirroring results in a scalable solution that updates as the business grows for seamless integration.

    3. Scalable Data Storage

      SQLServer databases hosted on AWS provided scalable data storage and enabled a wide range of data consumption methods. CapStorm provided the replication capabilities, while AWS’s architecture simplified the solution management. CapStorm’s applications also supported multiple extract configurations to a single AWS database, meaning key objects could be replicated at a higher frequency, resulting in near real-time data ingestion. Staging in AWS provided a central location for the ETL process to transform and integrate data into internal systems.

Graphic of white, black and CapStorm blue colored cubes stacked on each other.

Outcome

Checkmark inside of a white circle.

Revealed new insights based on near real-time data.

Checkmark inside of a white circle.

Decreased risk with self-hosted data and solutioning.

Checkmark inside of a white circle.

Reduced maintenance costs with automatic schema mirroring.

Want results like this?

Become a CapStorm Insider

Subscribe to the CapStorm Forecast

Name
This field is for validation purposes and should be left unchanged.