Skip to content
caseStudyHeaderBanner

Controlling Research Compute Spend For A Pharmaceutical Manufacturer

  • FinOps
  • Research Compute
  • Budget Accountability

One Of India's Largest Pharmaceutical Manufacturers With Research Across Multiple Sites.

The Company Develops And Manufactures Generic And Speciality Formulations, With Research Teams Running Molecular Modelling, Trial Data Analysis And Stability Simulations. Compute Demand Arrives In Intense Bursts When A Programme Reaches A Milestone And Falls Away Almost Entirely Between Them.

Company Profile

  • 06 Research Sites
  • 40+ Years In Manufacturing

Problem Statement

Research Compute Spend Growing Without Anyone Owning It.

problmStatmntMainPic
problmStatmntSubPic1
problmStatmntSubPic2
problmStatmntSubPic3

CHALLENGES FACED

As Research Workloads Moved To Cloud For Elasticity, The Company Encountered Several Challenges: With Each Research Team Provisioning Independently, Nobody Reconciled What Was Running Against What Any Programme Actually Needed.

icon
Reclaiming Idle Compute

Clusters Provisioned For Milestones Continued Running Long After Analysis Finished.

icon
Attributing Programme Costs

Spend Could Not Be Traced To Any Research Programme Or Therapeutic Area.

icon
Forecasting Research Budgets

Finance Received Bills That Bore No Relationship To Approved Programme Budgets.

Existing System : Research Teams Provisioning Without Any Cost View

Each Research Group Provisioned Compute Directly When A Programme Required It, Sized Generously To Avoid Delaying Analysis. Environments Were Rarely Decommissioned Because Nobody Was Certain Whether A Colleague Still Needed Them. Storage Accumulated Continuously, With Datasets From Completed Studies Retained On The Fastest Available Tier.

Result :

Compute That Follows The Science.

caseStudyResult

Research Teams Now Provision Freely Within Programme Budgets They Can See, And Environments Release Automatically When Analysis Completes. Spend Is Attributed To Programme And Therapeutic Area, So Finance Reconciles Cloud Costs Against Approved Research Budgets Rather Than Receiving A Single Figure Nobody Can Decompose Or Challenge.

44%

Lower Compute Spend

100%

Costs Attributed To Programme

71%

Idle Capacity Reclaimed

03

Day Budget Visibility

ourApproachCaseStudy1

Cost Was Attributed To Research Programmes Before Any Control Was Applied, So Teams Could See Their Own Consumption. Environments Then Received Defined Lifetimes With Automatic Release At Expiry, And Storage Moved To Tiers Matched To How Frequently Study Data Is Actually Accessed.

Our Approach: Programme Budgets With Automatic Release

ourApproachCaseStudy1
ourApproachCaseStudy2

IMPACT & RESULTS

Idle Environments Released
Costs Attributed To Programmes
Storage Matched To Access
Faster Programme Approval
Elasticity Actually Used
Predictable Research Budgets

Idle Environments Released

Clusters Provisioned For A Milestone Now Expire Automatically Once Analysis Completes Rather Than Running Until Someone Notices. Researchers Extend Lifetimes When Work Continues, So Nothing Is Lost And Nothing Runs Unattended For Months.

frameworks

TECHNOLOGIES - TOOLS USED

Cost Allocation Tagging Maps Spend To Programmes And Therapeutic Areas, Reported Through Dashboards Available To Research Leads. Environment Lifetime Policies, Automated Decommissioning And Storage Lifecycle Rules Operate Continuously, While Forecasting Tooling Projects Spend Against The Research Calendar And Approved Budgets.

  • Cost Allocation & Tagging
  • Programme Chargeback
  • Environment Lifetime Policies
  • Automated Decommissioning
  • Storage Lifecycle Policies
  • Rightsizing Analysis
  • Commitment Planning
  • Anomaly Detection
  • Budget & Forecast Tooling
  • Usage Telemetry
  • Cost Dashboards
×
×
×
×