Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
When your IBM Planning Analytics contract comes up for renewal, you have far more choice than you may realise. The platform itself can be licensed, supplied, and supported by any qualified IBM partner. You are not bound to the firm that built your current solution simply because they built it. Understanding this distinction is the difference between renewing by default and renewing on terms that genuinely serve your agency.
Licensing is widely misunderstood, and not every partner goes out of their way to clarify how it all works. This article is meant to give you a clear, simplified understanding of how it works, so you can get the value for the budget you're allocating.
IBM Planning Analytics (formerly known as and still frequently referred to as TM1) can be supplied and supported by any qualified partner with the right standing. The in-memory engine, the web interface, the forecasting and scenario capability: all of that is IBM technology. It is the same product regardless of which partner sells you the licence. A partner brings implementation skill, support, documentation, and government-finance fluency to the table. What they do not own is the platform itself.
So when you approach a renewal, the right starting question is not "what does our current supplier want to charge to renew?" It is "which qualified partners could supply and support this platform, and what would each of them offer?" That is a wider field than most teams assume.
Lock-in assumptions usually come from one place: the incumbent has built something on top of the platform. Over the life of an implementation, a supplier will often add a small piece of their own intellectual property (a configuration layer, a set of templates, a reporting wrapper, some custom utility) that sits on top of the IBM platform you are licensing.
There is nothing wrong with that in itself. Good implementation work produces useful assets. The problem is the leap that sometimes follows: because there is a bolt-on, the whole arrangement gets treated as inseparable, and the customer is encouraged to renew the entire planning capability with that one firm to keep that small piece intact.
However, a modest bolt-on is not a good reason to hand a single supplier your entire planning capability for another multi-year term. The real value is in your data model, your planning logic, your actual capability. Be clear about the difference before you renew anything.
As of this year, IBM has been changing its global rules around how these contracts renew, moving toward a more open system in which any qualified partner can handle the renewal.
We don't have an exact date or a hard deadline quite yet, but the main takeaway is this: the structures that used to keep contracts defaulting back to the original supplier are loosening. The path to renewing with a different partner is becoming clearer.
For a government buyer, this means the option to test the market is much more practical than it used to be. If you have ever been told that switching partners at renewal is too difficult to contemplate, that assumption deserves a fresh look in light of where IBM is heading.
This is where the licensing question stops being a technical detail and becomes a procurement obligation. A public-sector buyer is required to demonstrate value for money and to give more than one supplier a fair go.
If you ask an incumbent to respond, renew on their terms, and move on, without genuinely testing whether other qualified partners could supply the same platform, you are exposed. Not because anyone has done anything wrong, but because the process itself has not done what it is supposed to do. It has not tested the market, and it has not produced evidence that you got value for money. Governments carry an obligation to their constituents to procure the best solutions available, which is what makes the renew-or-switch decision critical.
Here are the questions you should be asking before you renew:
What are we actually licensed for? Get clear on exactly what IBM software your agency holds, on what terms, and what the renewal covers. This is the foundation. You cannot assess value for money on something you have not precisely defined.
What is portable to another partner? Because the platform is IBM software, your licence and the work built on it are not the personal property of one firm. Establish what would move with you if you chose a different qualified partner: your data model, your planning logic, your configuration. Knowing what is portable tells you how real your choice is.
What exactly is the bolt-on IP, and does it justify the lock-in? Identify precisely what proprietary layer, if any, the incumbent has added on top of the platform. Then ask the honest question: is this piece valuable enough to justify renewing your entire planning capability with one supplier? Sometimes the answer will be that the bolt-on is genuinely useful and worth keeping. Often it will be modest enough that it should not, on its own, decide the whole renewal.
Have we given more than one partner a fair go? This is the procurement question, and it is the one that protects you. If the honest answer is no, that is the gap to close before renewal, not after.
Certainly not. Testing the market is not the same as switching, and it is not a vote of no confidence in anyone. A genuine process might well confirm that your current arrangement is the right one. If it does, you renew with evidence behind you rather than assumption. That is a stronger position to be in.
The point is not to manufacture a change for its own sake. The point is that a renewal decision made without testing the market is a decision made blind. You cannot show value for money if you have never looked at what value looks like elsewhere. Running a fair process either confirms your current choice or reveals a better one. Both outcomes are good for you.
A partner who handles this well will tell you the truth about your licensing options, including the parts that widen your choice rather than narrow it. They will document what they build so your team can understand and run it. They will transfer knowledge so you are left capable rather than dependent. And they will be comfortable with you testing the market, because their position rests on the quality of what they deliver, not on a structural advantage that keeps you tied to them.
Clarity about licensing is the baseline a government finance team should expect, because it is the only way the obligations you carry can actually be met.
IBM Planning Analytics is an IBM platform that any qualified partner can supply and support. A small piece of bolt-on IP is not a sound reason to tie your entire planning capability to one firm. IBM's rules are moving toward making partner choice at renewal more open. And as a public-sector buyer, you carry a real obligation to show value for money and consider all the options.
Well before your contract comes up, be sure to find out what you are licensed for. Determine what is portable, what the bolt-on actually is, and whether you have genuinely tested the market. Doing that will let you renew from a position of clarity and choice, which is exactly where a government finance team should be standing when public money is on the line.