When it comes to getting some very common and crucial tasks done in IBM Cognos TM1, we found that there are many quite painful tasks to do. They are so painful, that the thought untangling Christmas tree lights for a living seems much more appealing! One such painful task we are going to focus on today is managing security in TM1.
IBM Cognos and Motio Best Practices Blog
It seems like there is a different tech conference every month these days, so sifting through the noise and determining which one is truly beneficial for you and your personal career growth (along with which events will benefit your organization) is a task not to be taken lightly.
If you are a TM1 administrator, you are likely aware of the demand for maintaining efficient memory usage in your Cognos TM1 instance. Imagine this scenario: your Cognos TM1 environment is starting to lag. You know there exists out-dated TM1 objects, but aren’t sure if they are worth deleting. So you decide to delete objects that haven’t been used in a set amount of time, that use up the most memory. How do you determine which objects meet your criteria?
Why are systems like Cognos TM1 so sophisticated yet documentation remains poor? I recently wrote a blog post regarding managing Cognos TM1 with effective documentation and the significant importance it holds. Specifically, managing the complexity of TM1 solutions. In this guest blog post, I will elaborate on the overarching value of systems documentation within your company.