WebSphere term license versus perpetual under audit.
A perpetual WebSphere license and a term WebSphere license can look identical in a deployment scan, but they behave very differently when an auditor reconstructs the coverage timeline. The risk with term licenses is not the deployment, it is the window, and a gap between term periods can turn a fully deployed estate into a finding.
WebSphere is sold both ways. A perpetual license grants the right to run the entitled quantity indefinitely, with support and subscription renewed separately. A term license grants the right to run for a fixed period, after which the right itself ends unless renewed. The deployment is the same software on the same cores. What differs is whether your right to run it was continuous across the entire audit lookback, and that is precisely what a term arrangement puts at risk.
Perpetual: the entitlement is the question
With perpetual licenses, the audit reduces to the familiar reconciliation: did the deployed PVU exceed the perpetual entitlement quantity, accounting for sub-capacity. The right to run does not lapse, so the dispute is about quantity and metric, not about time. Support lapses matter for access to fixes and for some sub-capacity tooling expectations, but the underlying license to run the deployed version persists.
Term: the window is the question
A term license adds a second axis. Even if the deployed quantity never exceeded the entitled quantity, a term that expired and was renewed late leaves a period during which there was no right to run at all. An auditor reconstructing the timeline will look for exactly these gaps, because a lapse between term periods is a compliance exposure independent of how many cores were deployed.
The classic term finding is a renewal that slipped. A term license ends on a date, the renewal paperwork completes weeks later, and in between the deployment kept running. The cores never changed, the quantity never changed, but for that window there was no active term, and IBM will treat the window as unlicensed use.
How we defend each one
- Reconstruct the full coverage timeline from Passport Advantage records, mapping every term period and every perpetual entitlement against the deployment dates.
- For term licenses, identify any apparent gap and test whether a renewal, a grace provision, or a backdated effective date actually closed it.
- For perpetual licenses, focus the reconciliation on quantity and sub-capacity rather than time, and confirm the right to run the deployed version was never in question.
- Separate a genuine coverage gap from a paperwork lag that the contract terms already cover.
- Where a real gap exists, scope it to the specific window rather than letting it taint the whole WebSphere position.
Many term findings dissolve once the coverage timeline is properly assembled, because what looked like a gap was a renewal with an effective date that reached back to cover it. The work is in producing the evidence that the right to run was continuous, or in containing the exposure tightly where it genuinely was not.
With perpetual WebSphere, defend the quantity. With term WebSphere, defend the timeline. The most common term finding is an expiry gap created by a late renewal, not by over-deployment. Reconstruct the full coverage window from your entitlement records before IBM does, and most apparent gaps close on the effective dates.