The CA AIOps tier shift clause that costs more than it looks.

CA AIOps was sold into the enterprise during the 2019 to 2022 window on a managed entity model. The buyer's licensed entitlement was specified as a count of managed entities, which is the platform's term for the infrastructure objects under monitoring. The entitlement was bucketed into tiers, each with its own per entity rate. The tier shift clause governs what happens when the buyer's actual managed entity count crosses a tier boundary. The clause is short. It is rarely surfaced at renewal. It is also commercially expensive, because crossing a single tier boundary typically resets the per entity rate on the whole estate, not just on the entities above the boundary. Buyers who built their AIOps deployment without instrumenting against the tier boundaries find that the renewal arrives with a 30 to 60 percent uplift they cannot explain on the surface, and the explanation, when surfaced, sits inside a clause they had not read in three years.

The tier model is not unusual. The clause structure is. Most software contracts that meter on a volume metric apply a marginal rate above a threshold. The CA AIOps tier shift clause applies a retroactive rate on the entire entity base when the buyer crosses into a higher tier. The mechanic is what makes the clause expensive. A buyer at 4,800 entities at signature, with a tier boundary at 5,000, who has grown organically to 5,200 entities, finds the renewal priced not at the 5,000 rate plus the marginal 200 but at the higher tier rate applied to the full 5,200. The whole estate reprices. The 200 entity growth carries the cost of the tier shift across the full base.

What the clause actually says

The clause is typically two paragraphs in the middle of the contract's metrics schedule. The first paragraph defines the tiers, lists the per entity rates per tier, and specifies the boundaries. The second paragraph states that the applicable rate for the contract term shall be the rate of the tier into which the buyer's measured entity count falls at the renewal measurement point. The phrase that does the work is "the rate of the tier into which the buyer's measured entity count falls". The phrase does not say marginal. It says the rate of the tier. The whole tier rate applies. The reading is correct under the contract language. The buyer who reads the clause for the first time at renewal is reading it correctly and reading it three years too late.

A second sentence often follows that defines the measurement point. The measurement point is sometimes the renewal date. Sometimes it is the highest count observed in the trailing twelve months. The trailing twelve month variant is the more aggressive reading and the one we see in 2026 renewal positions more often than not. The buyer whose entity count spiked once during a migration window is being measured against the spike rather than the steady state.

Where the price impact compounds

The price impact runs through three channels. The first is the rate reset on the whole base. The buyer crosses the boundary, the whole estate is repriced, and the percentage uplift typically lands between 18 and 32 percent. The second is the forward year sizing. The renewal is built not on the current entity count but on a projected growth count for the forward year. The deal desk's projection is rarely as conservative as the buyer's. The third is the support uplift coupled to the new tier. Many AIOps contracts carry a support tier that scales with the per entity rate. The support cost moves with the tier shift.

"The growth of two hundred entities did not cost the buyer the price of two hundred entities. It cost the buyer the price of repricing the whole base. The clause permits the reading and the deal desk applies it consistently."CA AIOps Engagement Lead, The Desk

The compounding can be material. In one renewal we reviewed in early 2026, a buyer at 6,400 entities, who had crossed a tier boundary at 5,000, received a renewal quote that was 47 percent above the prior contract on entitled volume that had grown by 28 percent. The remaining 19 points of uplift sat inside the tier shift mechanic and the support tier that moved with it. Neither was disclosed as a discrete line on the quote.

The corrective moves available

Three corrective moves are available before signature. The first is an entity scoping review. The buyer's operations team produces an inventory of currently monitored entities and validates which entities genuinely need to be monitored under AIOps. In most estates, 12 to 22 percent of monitored entities are duplicates, decommissioned systems still reporting, or entities monitored under a default policy that no longer reflects the operating posture. The scope reduction can bring the buyer back inside the prior tier and avoid the shift.

The second corrective move is a clause amendment. The buyer requests that the tier shift clause be replaced with a marginal rate model. Broadcom has accepted the amendment in some renewals when the buyer was willing to commit to a longer term in exchange. The trade is usually buyer favourable because the marginal model removes the cliff effect across the full contract life. The third corrective move is a tier definition amendment. The buyer requests that the tier boundaries themselves be moved upward to reflect the buyer's current operating scale. The amendment is harder to win but is sometimes available where the buyer's overall contract value is significant enough that the deal desk wants to retain the relationship through the next cycle.

The numbers

What we have seen on live deals

A European insurer crossed a tier boundary in late 2024 through the addition of a monitored cloud estate that had not been in the AIOps scope at original signature. The renewal quote came in 39 percent above the prior contract. The buyer engaged us to read the quote. The entity scoping review identified that 14 percent of the monitored cloud entities were duplicates of on premises entities already in scope. The scope reduction brought the buyer back inside the prior tier. The renewal closed at 4 percent below the prior contract, with a clause amendment that converted the tier shift to a marginal rate model for the new contract term.

A North American bank could not find scope to reduce. The bank's AIOps deployment had genuinely grown through a regulated workload addition that required the new monitoring scope. The clause amendment route was used instead. The bank committed to a 48 month term in exchange for the conversion of the tier shift to a marginal rate model. The renewal closed at 12 percent above the prior contract, against the 31 percent uplift on the original quote. The marginal model also removed the cliff risk on future growth, which the bank's operations team valued separately.

The takeaway

• The CA AIOps tier shift clause reprices the whole entity base when the buyer crosses a tier boundary. The mechanic is not marginal. It is retroactive across the full estate. The clause permits the reading and the deal desk applies it consistently in 2026 renewals.
• The corrective moves require the work to happen before signature. An entity scoping review typically identifies 12 to 22 percent of monitored entities that should not be in scope, and the reduction often brings the buyer back inside the prior tier without contract amendment.
• A clause amendment that converts the tier shift to a marginal rate model is available in some renewals in exchange for term commitment. The amendment is the more durable buyer position because it removes the cliff effect across the new contract life rather than only at the next anniversary.