The best time to understand a CMMS renewal is before the first contract is signed.
By renewal, the organization may have years of maintenance history, trained users, configured workflows, integrations and operating habits inside the system.
That does not make renewal a bad outcome.
It makes the initial commercial baseline important.
Renewal cost is more than an annual percentage increase
A future CMMS price can change for several different reasons.
CMMSBuyersGuide separates them into the Renewal Exposure Map:
Baseline Price
+ Contractual Escalation
+ Operational Growth
+ Tier Crossing
+ Capability Change
+ Support/Hosting Change
+ Commercial Reset
= Future Commercial Exposure
Those are different mechanisms.
A buyer should know which ones the contract permits.
1. Baseline price
Record the commercial state at signing.
At minimum:
- licensed product/edition
- licensing model
- quantities
- unit prices if applicable
- platform/base fees
- sites
- assets if commercially relevant
- included modules
- included support
- hosting
- environments
- discounts
- contract term
- renewal options
Without a baseline, a later price change can be difficult to explain.
2. Contractual escalation
Escalation changes price without necessarily changing operating scope.
Possible mechanisms include:
- fixed annual percentage
- capped percentage
- index-based adjustment
- negotiated adjustment
- then-current pricing
- no stated increase during initial term
Do not assume one mechanism is standard.
AlexRenew's CMMS contract provides a useful public example.
Its renewal-term fees may be adjusted, but increases cannot occur more than once in a 12-month period and cannot exceed the specified CPI-U change under the contract language.
The contractor must request an adjustment in writing before renewal under the stated procedure.
That is a defined price-adjustment mechanism.
A buyer should know whether its own contract has one.
3. Operational growth
Price can increase even when the unit price does not.
If the commercially relevant population changes, future cost can change without an increase in the unit rate.
The same logic applies to asset-, site- or usage-based models.
Separate:
price increase
from
quantity increase.
They are not the same thing.
4. Tier crossing
Some pricing changes happen discontinuously.
Example:
1–25 users = Tier A
26–50 users = Tier B
The 26th user may cause a larger plan change rather than a simple per-seat addition.
The same can happen with:
- assets
- sites
- storage
- transactions
- modules
- support levels
Record the next relevant threshold before signing.
5. Capability change
A renewal can become more expensive because the organization expands what it buys.
Examples:
- inventory
- purchasing
- advanced analytics
- additional mobile capability
- API/integration packages
- condition monitoring
- enterprise asset-management capabilities
- premium support
Do not call every future addition a “renewal increase.”
Separate added scope from increased price on existing scope.
6. Support and hosting
Confirm whether these are:
- included in subscription
- separately priced
- separately escalated
- tied to another commercial quantity
- optional
- required
That is useful because recurring components do not always move together.
7. Commercial reset
Some contracts preserve initial pricing rules into renewal periods.
Others may allow renewal at a new commercial basis.
The buyer should identify:
- whether initial discounts survive
- whether renewal uses quoted option-year pricing
- whether pricing becomes then-current/list pricing
- whether quantities can be reduced
- whether minimum commitments change
- whether renegotiation is required
- whether new order forms supersede original pricing
Do not infer these terms.
Read the contract or order form.
Option years are evidence, not certainty
Public procurements often price or define option years.
Option-year structures are useful because they make future commercial assumptions visible.
They do not eliminate the need to read exact exercise and pricing terms.
Notice dates matter
Renewal economics can be affected by administrative deadlines.
Record:
- renewal date
- notice required to renew
- notice required not to renew
- deadline to request pricing adjustment
- deadline to reduce quantities if permitted
- budget/procurement lead time
Do not leave these dates buried in the contract.
Create a renewal calendar at signature.
The Renewal Baseline
Create a one-page record when the contract is signed.
Commercial identity
Product
Edition
Modules
Sites
Meter
Named users / concurrent / assets / sites / other
Quantity
Current committed quantity
Included quantity
Next tier
Price
Base/platform
Unit price
Recurring support
Hosting
Other recurring components
Protection
Initial term
Option years
Escalation formula/cap
Discount treatment
Price validity
Change triggers
Added user
Added asset
Added site
Added module
Added environment
Support-tier change
Dates
Renewal date
Notice deadline
Pricing-adjustment deadline
Exit/transition
Data export terms
Transition assistance if contracted
Relevant termination obligations
This becomes the reference point for every later renewal discussion.
Run three renewal scenarios before signing
Scenario A — Same operation
No growth.
Same modules.
Same quantities.
What can price become?
Scenario B — Expected growth
Use the organization's realistic operating plan.
What changes commercially?
Scenario C — Contraction or change
Fewer users, closed site, reduced scope or migration away.
Can quantities decrease?
When?
Does pricing change?
What obligations remain?
The third scenario is frequently ignored.
A commercial model should be understood in both directions.
Separate known from unknown
Create a Renewal Exposure Register.
For every mechanism mark:
Defined | Capped | Formula-based | Negotiated | Unknown | Not applicable
Unknown is not automatically bad.
But a material unknown should be resolved before it becomes a surprise.
Renewal is an ordinary future
Eventually, a CMMS becomes an operating system that has to be renewed, expanded, renegotiated or replaced.
The initial buying process should prepare for that ordinary future.
The buying principle
Do not wait until the renewal notice arrives to reconstruct what you bought.
Capture the baseline, pricing mechanism, quantities, thresholds, escalation rules, notice dates and change triggers when the original agreement is signed.
Renewal risk is created at the initial signature, not at renewal.
How to compare two CMMS proposals on the same price boundary
Sources
- Alexandria Renew Enterprises — RFP No. 22-001, Provision, Implementation and Maintenance of CMMS
Contract terms state that fees may be adjusted for a renewal term, that rates shall not increase more than once in any twelve-month period, that no increase shall exceed the change in CPI-U for the stated twelve-month period, and that the contractor must submit a written price-adjustment request not less than ninety days before the renewal term.