Software asset management for banks means keeping one trusted record of every license the bank owns and every copy of software it runs, across every publisher, so it is ready for any vendor audit and pays only for what it uses.
A fast-growing bank in India has run it with us as a managed service for five years, across more than 16,300 assets and 25 publishers. Every figure from the engagement is in our managed SAM case study for this bank.
| Assets discovered and reconciled | Publishers under continuous governance | Product areas with documented cost avoidance | Managed SAM term |
|---|---|---|---|
| 16,300+ | 25 | 6 | 3 + 2 years |
| Client | A fast-growing bank in India |
|---|---|
| Estate | More than 14,500 desktops and laptops, and more than 1,800 servers on Windows, Linux, Unix, Oracle Exadata and SuperCluster |
| Publishers | 25, including Microsoft, Oracle, IBM, Adobe, Red Hat and VMware, plus Microsoft 365 for the whole workforce |
| Engagement | Managed software asset management on the Euladox platform, with a Rythium engineer on site |
| Term | Three years, then extended by the bank for two more |
| Outcome | Cost avoidance in six product areas, Microsoft 365 licenses matched to how people work, and license data ready for vendor audits |
Why is software asset management harder for a bank?
A bank runs several estates at once: desktops and laptops in its branches and offices, data center servers on more than one operating system, engineered systems such as Oracle Exadata, and Microsoft 365 for every employee.
Each publisher counts its licenses in its own way:
- Microsoft licenses Windows Server and SQL Server by core, and Microsoft 365 by user.
- Oracle licenses its databases by processor or by named user.
- IBM counts processor value units, and charges for less than full capacity only while its License Metric Tool (ILMT) reports are kept in order.
A spreadsheet goes out of date with every hardware refresh, migration and new subscription. Each publisher can audit on its own schedule, and the bank has to answer every one with evidence.
Where this bank started
The bank had more than 14,500 desktops and laptops and more than 1,800 servers across Windows, Linux, Unix, Oracle Exadata and SuperCluster. Its licenses came from 25 publishers, including Microsoft, Oracle, IBM, Adobe, Red Hat and VMware.
Vendor audits were becoming more frequent, and it had no single license position it could trust. It wanted to stay compliant and cut its software spend at the same time, as an ongoing service rather than a one-off project.
What does a managed SAM service do for a bank?
It runs the whole cycle, year after year: find what is installed, match it to what was bought, keep that record current, and act on what it shows. For this bank we run it in four stages.
- Discover. We scanned more than 1,800 servers with Euladox and ran its Stand-Alone Discovery Agent on more than 14,500 endpoints. We cross-checked the results against the bank’s ManageEngine data.
- Reconcile. We loaded contracts, purchase orders and entitlements into Euladox and matched them to what was actually deployed. That gave the bank a baseline license position for each publisher.
- Govern. We refresh the license position every quarter or twice a year, timed to each renewal date. A renewal calendar raises alerts for every subscription and support contract before it comes due.
- Optimize. We profiled how Microsoft 365 users actually work and rebalanced their license types to match. We also write remediation plans, give cost-avoidance advice and supply license data when a vendor audits the bank.
What is an Effective License Position, and how often should a bank refresh it?
An Effective License Position (ELP) sets what the bank is entitled to use against what it actually runs, product by product and publisher by publisher. The entitlement side comes from its contracts, purchase orders and entitlements. The difference shows two things:
- where the bank is under-licensed and exposed in an audit;
- where it pays for licenses it does not use.
An ELP is only true on the day it is made. Servers are added and retired, projects move workloads, and subscriptions renew with new counts.
So this bank’s position is refreshed every quarter or twice a year, timed to each publisher’s renewal date. A renewal calendar raises an alert before every subscription and support contract comes due, so each renewal starts from a current position.
How do you match Microsoft 365 licenses to how people work?
Microsoft 365 plans differ in what they include:
- E3 plans include the desktop Office apps.
- E1 plans give the web and mobile versions only.
- Kiosk licenses, which Microsoft now sells as frontline plans, are made for staff on shared devices or with a narrow set of apps.
When a whole workforce sits on one plan, some people are licensed for apps they never open, and others may need more than they have. A user-profiling study looks at how each person works and assigns the plan that fits.
For this bank, that study realigned its E1, E3 and Kiosk licenses to how people actually work. Microsoft 365 is one of the six product areas where we documented cost avoidance. Read more about Microsoft 365 license optimization.
What does a bank need when a vendor audits it?
An audit asks for evidence for that publisher’s products: what the bank is entitled to, what it has deployed, and how the two match.
A bank that keeps its license position current can answer from its own records within the audit’s timelines. Without that, it has to build the picture from scratch while the auditor waits. For this bank we supplied license and deployment data for Adobe and Oracle Java audits.
Java needs its own attention. Oracle now prices its Java SE subscription on an employee metric, so a gap that looks small can be priced across the whole workforce. Our Java license review covers that, and our software audit checklist lists what to prepare before any audit.
Why run SAM as a managed service rather than a one-off project?
A one-off license review gives a bank a position that is accurate on the day it is delivered. After that, the estate moves on and the position drifts.
This bank wanted to stay compliant and cut its spend continuously, so it asked for an ongoing service:
- On site. A Rythium support engineer works at the bank’s head office, day to day, alongside the bank’s own SAM team.
- Expert-led. Behind the engineer, our licensing specialists handle the publisher-specific work, led by Sheshagiri Anegondi, a former Oracle vice president, and Anil Nahata.
- Project delivery. Ritesh Verma, our Vice President of Delivery and Operations, manages project delivery.
- Tool and process. The Euladox platform, plus a process study and a SAM good-practice playbook written for the bank.
The bank extended the three-year term by two more years. Our SAM managed services page sets out how the service works for other estates.
The results: Always ready for the next audit
- Cost avoidance documented for Adobe, Oracle, IBM, Microsoft SQL Server, Microsoft Windows Server and Microsoft 365.
- Microsoft 365 optimization. A user-profiling study realigned E1, E3 and Kiosk licenses to the way people actually work.
- Audit support. We supplied license and deployment data for Adobe and Oracle Java audits.
- One trusted record. More than 16,300 assets are discovered and reconciled in Euladox, and all 25 publishers are under continuous license governance.
- A longer term. The bank extended the three-year managed SAM term by two more years.
Talk to us about your license position
Tell us which publishers you license and how many servers and endpoints you run. A senior advisor will walk you through how a managed SAM service would work for your estate.
Talk to an advisor or read the full managed SAM case study for this bank.
More managed SAM case studies: a private-sector bank, on-premises and on AWS; a Red Hat audit defense for a Kenyan SACCO; from license review to managed SAM at a bank in Mauritius.
See more of our analysis in Google: add Rythium as a preferred source
