Three years, 19 million euros, one mainframe back under control

The mainframe was running at 100% capacity during the online window, with a bank merger imminent and consumption growing structurally month after month. The bank had estimated it would need 1,190 MSU to absorb the integration.

Orizon’s assessment found the real minimum was 1,833 MSU, a 643 MSU gap. Under those conditions the integration was not viable: attempting it risked denial of service to customers, at an incalculable reputational cost.

Orizon combined pre-integration monitoring through Orizon Platform with technical optimizations across the installed base, working on more than 1,950 components in a few weeks. The target was to reduce 105 MSU before the critical day.

The result was 260 MSU/h reduced, 250% above target, and the integration was completed without a single service incident. Recurring savings reached 1.9 million euros a year.

A nine-month project to bring capacity to 1,190 MSU or below, across three workstreams: the online morning peak, the nightly batch peak, and containing growth from an estimated 22,922 annual software changes.

Capacity landed at 1,140 MSU, 50 MSU better than target, and batch SLA improved from 94% to 96%.

Focused on the nightly batch peak and on reducing accumulated technical debt, across three lines: growth containment, deep batch optimization, and on-demand analysis.

Real production savings reached 309.2 MSU/h, 2.4 times the 130 MSU target, avoiding more than 2.5 million euros in extra cost and cutting the bank’s internal workload by more than half versus the previous two years.

When the bank ran for seven months without Orizon’s monitoring, consumption grew by an additional 190 MSU, and on one day the machine hit its 1,136 MSU limit for three hours. It confirmed, with real data, what Orizon had projected: the growth does not stop on its own.