Many clients ask us how to reduce their IBM licensing costs. One of the easiest wins is correctly identifying non-production servers and assigning the appropriate lower-cost licenses.
It’s a common blind spot — especially with products licensed by the number of cores on a server (e.g. PVU, RVU, VPC).

Having worked on hundreds of IBM licensing projects, I’ve seen this oversight cost clients millions — and it’s almost always avoidable. The good news? It’s usually easy to fix, and in most cases, no technical changes are needed.
If you’re using ILMT and reporting sub-capacity usage, this guide will help you prepare a list of non-production servers. That list can unlock savings of hundreds of thousands (sometimes even millions) in IBM license costs.
Why It Matters
IBM’s Passport Advantage terms allow for reduced or even zero licensing for some non-production scenarios — but only if you’ve done it correctly.
To be compliant, you need to ensure:
- Servers are correctly tagged and documented
- The software usage matches IBM’s accepted non-production definitions
- ILMT or BigFix reflects this usage properly
- You can provide proof if audited
Get it right and you can significantly reduce license requirements and costs. Get it wrong, and it will come back to bite you in a future audit.
What Counts as Non-Production?
Definitions vary slightly by product, but broadly, IBM accepts the following server roles as non-production:
- DEV – Used by developers only
- TEST / QA – For functionality, performance, or regression testing
- UAT / PRE-PROD – Staging ahead of go-live
- DR – Passive or cold standby only*
- HA – Certain IBM products allow lower-cost licenses for high-availability setups
- EVAL – Temporarily evaluating a product
- TEMP – Parallel running during migration or upgrade, valid for 90 days (unless otherwise agreed)
- DECOM – Decommissioned or no longer in production
*Note: DR servers used actively (e.g., for testing) may be deemed production. See our Guide to IBM Licensing for Hot, Warm, and Cold Standby Machines for details.
How to Find Non-Production Servers
If you’re working with a long list of servers, here’s how we usually approach it. Each non-production server you find and downgrade could save you thousands — it’s worth the effort.
Start with a master server list
Begin with a complete inventory from your CMDB or similar system. Compare this to ILMT’s list and fix any discrepancies.
Filter for IBM product deployments
Refine the list to only servers running IBM software. ILMT helps here, but check for servers with IBM deployments not covered by ILMT.
Use server naming conventions
Most organizations use naming patterns (e.g. “P” for prod, “T” for test). Confirm the scheme with DevOps or network admins and filter accordingly—Cross-check with CMDB status.
Filter by data center or IP range
Non-production servers are often hosted in dedicated data centers or within specific IP ranges. Use this as another filtering method and reconcile it with your existing shortlist.
Ask the DBAs
Database administrators maintain excellent records of which databases and servers are linked. They know which are backups, hot or cold standbys, etc. Tap into their knowledge.
Other useful sources
- Cybersecurity teams – Non-prod often have different protection rules
- Outsourcers – May track server status for billing
- Cloud teams – Usually tag non-prod workloads
- DR runbooks – Often list backup servers explicitly
Verify Your Non-Production Server List
Verifying the list (and the reasons behind it) is essential. It justifies the license treatment and prepares you for any questions from IBM or an auditor.
Verify with service owners
Ask the business or service owners to confirm the server status. Let them know cost savings may be possible if a server can be confirmed as non-production.
Verify with system admins and DBAs
Explain what you’re doing and why. With a clear goal — reducing IBM license costs — admins are usually happy to help. They may even flag additional servers.
Verify against IBM’s definitions
Be careful:
- UAT environments refreshed from production may not count as non-prod
- DR servers that auto-failover or are frequently active could be seen as production
Verify with an IBM licensing expert
An expert can review the list and ensure the classifications align with IBM’s rules. They may also identify additional opportunities to reduce license needs further.
Verify cloud and container environments
Non-prod classification becomes trickier with containers and hybrid cloud environments. Make sure to:
- Use Kubernetes labels or tags to flag workloads
- Keep logs or snapshots
- Document the use case (DEV, TEST, TEMP, etc.)
I Have a List of Non-Production Servers. Now What?
Update BigFix / ILMT
IBM tools don’t distinguish between prod and non-prod by default. If a product is found, it’s assumed to require a full license. It’s up to you to adjust reports to exclude eligible non-prod servers and reduce costs.
Update the ELP
An Effective License Position (ELP) matches software deployed to entitlements held.
IBM auditors or consultants typically begin by assuming that all deployments require full licenses.
Your list of non-production servers, along with the rationale, enables them to assign the appropriate lower-cost entitlements.
Need help?
If this hasn’t been done before, there’s a reason. You may not have the time or tools to tackle it alone.
At LicenseHawk, we can:
- Help identify non-production servers
- Update ILMT, BigFix, or your ELP
- Correct your license position to meet IBM audit standards
- Save you thousands (or more) in the process
FAQs
Yes — but not always full-price licenses. Some roles (like cold standby) may not require a license at all, depending on the product and IBM policy.
No. ILMT scans for deployments but doesn’t distinguish usage types. You must manually configure and justify non-production designations.
In an audit, IBM may reclassify it and retroactively charge for full production use — often with backdated costs and penalties.
At least quarterly. Frequent changes in infrastructure, especially in cloud or container environments, mean roles can shift without notice.
Some organizations use scripts or CMDB integrations to help tag servers. But expert review is still needed to ensure compliance with IBM’s definitions


