IBM Planning Analytics (TM1) Third-Party Support:
Cost Guide & Alternatives 2026

IBM Planning Analytics — formerly Cognos TM1 — is the in-memory multidimensional planning and analytics engine that underpins financial planning, budgeting, forecasting, and management reporting for thousands of enterprises across financial services, insurance, healthcare, manufacturing, and retail. IBM acquired Cognos in 2008 and rebranded TM1 as Planning Analytics in 2016. The underlying TM1 engine — its cube architecture, TurboIntegrator scripting, and MDX query model — has remained substantially unchanged, which is why PA/TM1 deployments from a decade ago continue to function reliably today.

IBM is pushing PA customers toward Planning Analytics as a Service (PAaaS) on IBM Cloud and, for larger enterprises, toward IBM Cognos Analytics with Cloud Pak for Data. Both migration paths involve re-implementation of TM1 models, retraining of finance teams familiar with the Architect and Performance Modeler interfaces, and a shift from perpetual licensing to SaaS subscription pricing. For most PA/TM1 customers, third-party support is the commercially rational alternative.

IBM Planning Analytics / TM1 Version Support Timeline

Planning Analytics 2.0.x reached end-of-support in September 2023. PA 2.0.9+ (the last substantial on-premises release before the Local 2.1 line) reaches end-of-support in September 2025. Both versions represent the majority of the on-premises PA/TM1 installed base. IBM's response to this support cliff is a PAaaS migration proposal — but the economics of PAaaS rarely stack up against third-party support for existing on-premises deployments.

IBM's PAaaS Migration Pressure Playbook

IBM's SaaS pitch for Planning Analytics centres on three claims: managed infrastructure (no patching, automatic upgrades), enhanced AI-assisted forecasting via IBM Watson integration, and simplified administration through the web-based Workspace interface. Each deserves scrutiny from a total cost perspective.

The managed infrastructure argument is valid in narrow terms — IBM handles server patching under PAaaS — but the migration cost to reach that state is substantial. TM1 models must be re-certified against the PAaaS TM1 server version, TurboIntegrator processes that rely on local file system access must be rewritten for cloud-native data pipelines, and integrations with on-premises ERP and GL systems must be rebuilt as API-based connections. For a mid-sized bank with 40–80 TM1 cubes and 200+ users, this is a 6–18 month project costing £500K–£3M.

The AI forecasting argument overstates practical benefit for most PA deployments. IBM Watson-based forecasting adds statistical model selection capability that PA/TM1 users with mature Excel-fed models or Cognos Controller integrations neither need nor want to rebuild their workflows around. Finance teams use PA because of its multidimensional speed and the TM1 model logic built by their analysts — not because of the underlying forecasting statistics, which are already adequate.

What Third-Party Support Covers for Planning Analytics / TM1

Third-party support for IBM Planning Analytics covers the full TM1 server stack: TM1 Server process management and memory tuning (the PA TM1 engine is famously sensitive to memory configuration), TurboIntegrator (TI) process failures and performance degradation, cube dimension integrity issues and consistency checks, MDX query performance and resolution, Planning Analytics Workspace (PAW) connectivity and session management, Planning Analytics for Microsoft Excel (PAFE) integration issues, and Cognos Controller / tm1cm integration for organisations running both products.

Security patches address known CVEs affecting the TM1 Server binary, the Java components used by Planning Analytics Workspace, and the IBM HTTP Server layer used in on-premises deployments. IBM's own security patch cadence for out-of-support PA versions is effectively zero — third-party support fills this gap for the enterprise CVE compliance obligation.

Planning Analytics TPS Cost Model 2026

Four Strategic Options for PA / TM1 Customers

Sector-Specific Considerations

Financial Services and Insurance

Banks and insurers using PA for ICAAP/ILAAP stress testing models, Solvency II reporting, and management accounts have a specific concern about any platform change: model validation. Internal audit and risk functions are required to validate any change to planning models used in regulatory submissions. Third-party support preserves the validated model environment. PAaaS migration triggers full model re-validation — a 6–12 month exercise with capital and resources that most finance functions cannot spare.

Healthcare and NHS

NHS Trusts and healthcare organisations using PA for activity-based planning and NHS Service-Line Reporting (SLR) have procurement constraints that make PAaaS migration complex. G-Cloud framework procurement, data residency requirements (NHS data must remain in UK data centres), and DSP Toolkit obligations for cloud-hosted data each add compliance overhead to a PAaaS migration. Third-party support avoids these obligations entirely.

Manufacturing and Retail

Manufacturing and retail organisations using PA for trade promotion planning, factory budgeting, and SKU-level demand forecasting rely heavily on custom TM1 cube hierarchies and TurboIntegrator ETL processes that load from ERP systems. These integrations are typically 10–15 years old, undocumented, and deeply embedded in financial reporting workflows. Migrating them to PAaaS requires full discovery, documentation, and rebuild — a project that typically uncovers hidden dependencies that extend the migration timeline significantly.

Transition Process: PA / TM1 to TPS

1. Model and environment audit (Week 1): Inventory TM1 server count and version, cube count, TI process library, named user count, and ERP/GL integration points. Identify any open IBM PMRs (Problem Management Records) that need resolution before transition.
2. TPS contract alignment (Weeks 1–2): Confirm response SLAs for P1 TM1 server failures (15-minute response, 4-hour resolution path), security patch coverage scope, and TI performance support inclusion.
3. IBM notification (Week 2): Give IBM the required PA contract notice period. IBM will initiate a PAaaS migration discussion — your TPS contract is the counter-proposal.
4. Knowledge transfer and monitoring setup (Weeks 2–3): GoVendorFree IBM engineers review the TM1 architecture, establish monitoring, and take over the support queue.
5. Go-live (Week 4): TPS active. IBM Passport Advantage terminates at renewal. All TM1 models, processes, and integrations remain unchanged.