Tag: planning analytics

  • 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…

  • 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.…

  • Adjusting server configuration for Planning Analytics

    What this article is about Planning Analytics or TM1 server v11 comes with a host of new features. In order to get best performance and control behaviour of the TM1 server if you are upgrading or considering upgrading to PAL then you should make sure that as a minimum you optimize your server configuration file…

  • Planning Analytics Workspace Installation guide

    What do I need to start the installation of Workspace? 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…

  • We old-schoolers need to revisit the language we use to talk about dimension structures

    Back Then … In the TM1 world, many people have for many years been used to saying “hierarchies” when referring to hierarchical dimension structures e.g. Ancestor > direct children (consolidated) > intermediate consolidations > ultimate leaf descendants When TM1 was just TM1 and dimensions didn’t have named hierarchies this was OK as it was still…

  • Using hierarchies for PickLists

    PickLists, a quick recap. As we know PickLists in Planning Analytics can be defined in 3 ways: as static lists using the form static::item1:item2:item3 based on dimensions using the form dimension:dimName based on subsets using the form subset:dimName:subName PickLists can be defined either via naming a dimension attribute “PickList” and defining a string value for…

  • The (increased) importance of attributes in Planning Analytics

    The importance of attributes in PA Attributes have always been very useful when developing a TM1 model but until now have never been an essential component of development. With Planning Analytics this changes. This is a forgotten or little known point that all TM1 developers should be aware of and is relevant for anyone with…

  • Upgrade from TM1 10.x to Planning Analytics

    Upgrade TM1 to Planning Analytics Planning Analytics (PA) is the next step to provide a complete planning solution on the powerful, multi-dimensional technology of TM1. With PA available in the cloud and on-premise, including various new front ends – the upgrade could seem daunting. Make use of the above roadmap to find the most suitable…

  • What is the Cubewise EDU TM1 and Planning Analytics Developer Credential?

    With growing interest, I keep getting asked: “what exactly is the ‘Cubewise EDU TM1 and Planning Analytics Developer Credential’”? The Credential was developed in partnership with DeakinCo. and is another initiative in Cubewise’s ongoing contribution to the ideals of #DoGoodTM1. At Cubewise, we had a growing list of TM1 and Planning Analytics customers that were…

  • Let’s talk about element and attribute naming

    This article isn’t about naming conventions. My opinion on naming conventions is that they are necessary both for end-users and developers to assist in making a system understandable and navigable. But I don’t have an opinion on what the best naming convention is other than it doesn’t exist. Whether a naming convention uses spaces, underscores,…