Skip to content
caseStudyHeaderBanner

Managing Cloud Operations For A National Housing Finance Business

  • Managed Cloud
  • Application Operations
  • Service Level Assurance

One Of India's Largest Housing Finance Companies Lending Across The Country.

The Company Provides Home Loans Through Branches, Direct Sales Teams And Digital Application Journeys, Serving Borrowers From Metropolitan Buyers To First Time Rural Applicants. Loan Origination, Credit Assessment And Customer Servicing All Run On Cloud Hosted Platforms Introduced Over Recent Years.

Company Profile

  • 340+ Branches Nationwide
  • 25+ Years Of Lending

Problem Statement

Cloud Platforms Growing Faster Than The Team Operating Them.

problmStatmntMainPic
problmStatmntSubPic1
problmStatmntSubPic2
problmStatmntSubPic3

CHALLENGES FACED

As Digital Origination Replaced Paper Applications Across Every Region, The Company Encountered Several Challenges: With Cloud Platforms Added Programme By Programme, Operational Responsibility Had Never Been Formally Assigned To Anyone.

icon
Assigning Clear Ownership

Each Platform Was Operated By Whichever Project Team Originally Delivered It.

icon
Maintaining Service Levels

No Agreed Response Or Resolution Targets Existed For Any Cloud Hosted Application.

icon
Sustaining Routine Discipline

Patching, Backup Checks And Capacity Reviews Happened When Someone Remembered.

Existing System : Platforms Operated By Whoever Built Them

Each Cloud Platform Remained With Its Delivery Team After Go-Live, Operated Alongside Their Next Project. Documentation Reflected The Original Design Rather Than Subsequent Changes. When An Application Failed, Branch Staff Contacted The Business Analyst They Knew, Who Located Whoever Understood That Particular Environment.

Result :

Operations With A Name Against Them.

caseStudyResult

Every Cloud Platform Now Has Documented Ownership, Agreed Service Levels And A Single Route For Raising Issues From Any Branch. Patching, Backup Verification And Capacity Review Follow A Published Schedule Rather Than Individual Memory, And Delivery Teams Have Been Released From Operating The Systems They Built Years Earlier.

100%

Platforms Under Managed Ops

97%

Incidents Within SLA

62%

Faster Resolution

24/7

Coverage Established

ourApproachCaseStudy1

Each Platform Was Taken Over Through A Structured Transition Capturing Architecture, Dependencies And Recovery Procedures Before Any Responsibility Moved. Service Levels Were Then Agreed Per Application Against Business Criticality, With Routine Operational Discipline Scheduled And Reported Rather Than Left To Individual Recollection.

Our Approach: Transition-In, Then Operate To Agreed Levels

ourApproachCaseStudy1
ourApproachCaseStudy2

IMPACT & RESULTS

Clear Operational Ownership
Delivery Teams Released
Service Levels Actually Measured
Routine Discipline Sustained
Documentation That Stays Current
Confidence To Add Platforms

Clear Operational Ownership

Every Platform Now Carries Named Operational Responsibility Rather Than Remaining Informally With Its Delivery Team. Branch Staff Reporting An Issue Reach A Defined Route Instead Of Searching For Whoever Last Worked On That Particular Application.

frameworks

TECHNOLOGIES - TOOLS USED

Operations Run On Monitoring And Alerting Across Every Cloud Platform, Feeding A Ticketing System With Agreed Severity Definitions And Escalation Routes. Patch Scheduling, Backup Verification, Capacity Reporting And Configuration Records Operate Continuously, With Service Level Reporting Published By Application And Business Unit.

  • Cloud Monitoring & Alerting
  • Incident Management
  • Problem Management
  • Service Level Management
  • Patch Management
  • Backup Verification
  • Capacity Reporting
  • Configuration Management
  • Change Management
  • Knowledge Base
  • SLA Dashboards
×
×
×
×