There’s a fair amount of TM1 knowledge on the web.

The best TM1 knowledge on the web is here at Cubewise’s Tech blog.

Upgrade from TM1 10.x to Planning Analytics

Migrating from TM1 10.2.2 to Planning Analytics is not complicated, but it is a process with multiple layers that requires sufficient planning.

With IBM’s decision to stop support for TM1 10.2.2 in September 2019, we compiled a decision tree to ensure you know which questions you need to answer to find the most suitable path for your environment to effectively plan your upgrade to Planning Analytics.

PAL Installation Guide

Once you have gone through the PA decision tree and technical implications articles and decided to upgrade to Planning Analytics, the next important question you must ask yourself is “how do I technically do it?”. Many people are afraid of the upgrade, because of the general perception that this is a very complicated process, more time consuming than ever before. This is however not true. Of course, it requires some preparation and execution time, but generally not more than when you upgraded from 9.x to 10.x.

The following list contains information about requirements and the installation steps for Planning Analytics.

Converting Perspectives Reports to PAx

Moving to an upgrade where an update is required on workbooks can easily be addressed by making use of the additional functionality provided within the Planning Analytics software.

Making use of Snap Commands in Planning Analytics Workspace

With the release of IBM Planning Analytics Workspace (hereinafter referred to as PAW) came a new interface, new ways of interacting with data, and the addition of Snap Commands.

PAW’s Snap Commands are simple commands that can be used to accelerate common tasks. They allow the use of natural language to find, create, and interact with visualizations. Snap Commands can be used for finding specific views or cubes, as well as creating and modifying views and visualizations.

Technical implications when moving to PAL: A TM1 upgrade checklist

With just under one year left of IBM supporting TM1 version 10.2.2, it can be assumed that most TM1 customers have at least started preparations for an upgrade to Planning Analytics (PA). The support aspect appears to be an underlying driver for the version upgrade, particularly if corporate policy prohibits the use of unsupported software. However, Planning Analytics offers other features such as alternate hierarchies, new clients (PAX, PAW), improved clients (TM1 Web), performance boosts following new configuration parameters, or the option to move to a cloud-based system. Most of these features can but don’t have to be used, which leaves TM1 customers with some decisions to make.

Adjusting server configuration for Planning Analytics

Planning Analytics comes with a host of new features. If you are upgrading or considering upgrading to PAL then you should make sure that as a minimum you optimize your server configuration file (tm1s.cfg) to get the most out of the latest version and get best performance from your TM1 server. When launching new features IBM has a history of first disabling new features by default and in later releases changing the default behaviour. Examples of this can be seen with ParallelInteraction, PersistentFeeders and MTQ which were all initially disabled by default but are now enabled by default. We would expect the default values for the new features of Planning Analytics to all switch to being enabled within the next few releases. In the meantime read on to see what configurations you need to change to get the most out of the new TM1 server.

Planning Analytics Workspace Installation guide

The installation would seem daunting at first as the installation of Planning Analytics Workspace is not as straight forward as the usual TM1 installations. To continue with the Workspace installation, confirm the current version of planning Analytics Local as at least version 2.0.0 or greater is required before you can continue with the installation of Workspace.

We oldschoolers need to revisit the language we use to talk about dimension structures

TM1 oldschoolers have long been used to being sloppy in our use of language to describe dimensions, hierarchies and rollups. Now that Planning Analytics supports named hierarchies the term "hierarchy" has a specific meaning which we need to respect. Clear and unambiguous communication is important. It may be difficult at first, but if you catch yourself saying “hierarchy” when you really mean “rollup” stop and correct yourself. It doesn’t take long to change the habit and the sooner we all do we can stop second guessing each other.

Cloud versus On-Premise Deployment

Reviewing your Software environment can result in many questions. Which is the best option? How do I choose between cloud and on-premise? How would it change the way we manage our systems? Can the cloud environment be managed by internal IT team?

Both environments have benefits, therefore the best question to find an answer to is “Which solution suits us best?”.

Attributes in TM1. More things to be aware of

TM1 has supported MDX for a long time, but TM1’s own “dialect” of MDX can be a little quirky. Compared to standard MDX TM1 can be very concise, but it is also ambiguous which can be a problem as using TM1's "shorthand MDX notation" it is only possible to tell by context whether a member, a member property, or a subset is being referred to.

Of course, TM1 doesn’t just speak its own dialect of MDX, it also understands standard MDX and using standard MDX solves solves the problem of ambiguity. However, there is still a potential for typing and name conflicts between TM1 attributes and built-in intrinsic MDX member properties. This article makes Planning Analytics developers aware of these conflicts and how to deal with them.