Skip to content
caseStudyHeaderBanner

Running A Hybrid Estate Across Owned And Public Cloud Platforms

  • Hybrid Cloud
  • Workload Placement
  • Unified Operations

A Leading Private Sector Life Insurance Company Serving Millions Of Policyholders.

The Insurer Administers Long Term Policies Through Agents, Bancassurance Partners And Digital Channels, Holding Records That Must Remain Accessible And Auditable For Decades. Its Policy Administration Systems Carry Obligations That Span Far Longer Than Any Technology Refresh Cycle Or Vendor Agreement.

Company Profile

  • 18M+ Policies In Force
  • 20+ Years Of Operation
caseStudyInternalBrandMedia

Problem Statement

Two Estates Running Side By Side With Nothing In Common.

problmStatmntMainPic
problmStatmntSubPic1
problmStatmntSubPic2
problmStatmntSubPic3

CHALLENGES FACED

As Digital Channels Grew While Core Policy Systems Stayed On Owned Infrastructure, The Insurer Encountered Several Challenges: With Two Estates Operated By Different Teams Using Different Tooling, Neither Side Could See The Whole Picture.

icon
Connecting Both Estates

Digital Channels In Public Cloud Reached Core Systems Over Unmanaged Ad Hoc Links.

icon
Operating Two Toolsets

Monitoring, Backup And Access Control Differed Entirely Between Owned And Cloud Environments.

icon
Deciding Workload Placement

No Agreed Basis Existed For Choosing Where A New Application Should Run.

Existing System : Core On Owned Infrastructure, Channels In The Cloud

Policy Administration, Underwriting And Actuarial Systems Ran On Owned Infrastructure While Customer Portals And Mobile Applications Had Been Built In Public Cloud By A Separate Team. Integration Happened Through Point To Point Connections Added As Needed. Incidents Spanning Both Estates Required Two Teams To Compare Notes Manually.

Result :

One Estate, Two Platforms.

caseStudyResult

Core Systems Remain On Owned Infrastructure Where Long Retention And Regulatory Obligations Require It, While Customer Facing Workloads Run In Public Cloud Where Elasticity Matters. Both Are Connected Through Managed Interconnect, Monitored Through One Console And Governed By The Same Identity, Backup And Access Standards.

02

Platforms, One Operating Model

67%

Faster Cross-Estate Resolution

99.98%

Integration Availability

100%

Unified Access Control

ourApproachCaseStudy1

Workloads Were Assigned To Platforms Based On Data Retention, Latency And Elasticity Requirements Rather Than Team Preference. Managed Interconnect Replaced Point To Point Links, And Monitoring, Identity, Backup And Change Processes Were Unified So One Operating Model Covers Both Estates.

Our Approach: Placement By Purpose, Operations In Common

ourApproachCaseStudy1
ourApproachCaseStudy2

IMPACT & RESULTS

Faster Cross-Estate Incidents
Deliberate Workload Placement
Consistent Access Control
Reliable Integration
Retention Obligations Met Confidently
A Single Operating Model

Faster Cross-Estate Incidents

Issues Spanning Customer Portals And Core Policy Systems Are Now Diagnosed From One Console Rather Than Two Teams Comparing Timestamps. Resolution No Longer Waits For Someone To Establish Which Estate The Fault Originated In.

frameworks

TECHNOLOGIES - TOOLS USED

The Estate Spans Owned Infrastructure And Public Cloud Connected Through Managed Interconnect, With Federated Identity And Unified Monitoring Covering Both. Backup, Change Management And Configuration Standards Apply Across Platforms, While Placement Criteria And Capacity Dashboards Report The Whole Environment As One.

  • Hybrid Cloud Architecture
  • Managed Interconnect
  • Federated Identity
  • Unified Monitoring
  • Cross-Platform Backup
  • Configuration Management
  • Workload Placement Framework
  • API Gateway
  • Access Governance
  • Change Management
  • Capacity Dashboards
×
×
×
×