Cognos term license vs perpetual posture.
A Cognos estate is rarely all one thing. Term licenses and perpetual licenses carry different rights, different expiry behavior, and different audit risks, and most estates hold a mix of both. Knowing which posture sits behind each deployment decides what a finding can legitimately claim, and that is where the defense begins.
Two postures, two risk profiles
A perpetual license grants the right to use the software indefinitely, with support and subscription renewed separately each year. A term license grants the right to use for a fixed period, after which the entitlement lapses unless it is renewed. The same Cognos capability can be held either way, and the posture changes the audit conversation entirely. With perpetual licenses the question is whether deployment exceeds entitlement. With term licenses the question is also whether the entitlement was current at the moment the audit measures, because a lapsed term is a different finding from an over deployment.
Where the posture confusion creates exposure
The risk is that an audit reads the estate as if it were uniform when it is not. Common patterns include:
- Term deployments measured as perpetual. A term entitlement counted as if it persisted indefinitely can produce a compliance picture that does not match the rights actually held at the audit date.
- Lapsed term not separated from active term. Where term licenses expired and the deployment continued, the finding needs to distinguish the period covered from the period not covered, rather than treating the whole span as unlicensed.
- Perpetual entitlement ignored on a converted product. When a perpetual product moves to a term or subscription model, the prior perpetual entitlement may carry rights that an audit overlooks.
- Support lapse confused with license lapse. Letting support lapse on a perpetual license does not remove the right to use, though it is a recognized audit trigger. The two must not be conflated.
Building the posture map
The defense is to map every Cognos deployment to the posture that actually governs it, with the effective dates that apply. Term entitlements are placed against the periods they cover, perpetual entitlements are credited for the indefinite right they grant, and any conversion between models is reconstructed so prior rights are not lost. With a clean posture map, a finding can only claim what the rights genuinely fail to cover, which is usually far narrower than an estate read as uniform suggests. Dropping support is itself a known trigger for an IBM audit, which is one reason a clear separation between support status and license rights matters before any finding is accepted.
Before accepting a Cognos finding, separate term from perpetual and map each deployment to the rights and dates that govern it. A term entitlement measured as perpetual, a lapsed term not bounded to its covered period, or a support lapse confused with a license lapse all inflate the claim. The posture map decides what can legitimately be counted.
Is your Cognos finding reading term as perpetual?
Our Audit Negotiation engagement maps every Cognos deployment to its true posture and effective dates, separates lapsed term from covered term, and credits perpetual rights so the settlement claims only what your entitlements genuinely fail to cover.
See Audit Negotiation →The IBM Audit Brief
Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.
Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.