September 2010
S M T W T F S
« Jun    
 1234
567891011
12131415161718
19202122232425
2627282930  

Benefits to Upgrading Your IBM Cognos Planning Licensing

IBM recently announced a major licensing change in their IBM Cognos Planning licensing. Clients that are on 8.4.1 of IBM Cognos Planning and own Contributor, will receive an equivalent license for IBM Cognos TM1 Contributor. This is great news for clients looking to complement Planning with TM1.

With this licensing change, they are requiring all IBM Cognos Planning clients to be on the latest Cognos Planning Enterprise Licensing Model to download 8.4.1. Clients who purchased Cognos Planning or Adaytum Planning prior to the IBM acquisition may be affected and be required to modify their IBM Cognos licensing.

For all older Planning clients, there are a lot of benefits to upgrading your licenses.

IBM Cognos Planning Licensing Change- Does it Affect You?

IBM recently announced a major licensing change in their Cognos Planning licensing. Clients that are on 8.4.1 of Cognos Planning and own Contributor, will receive an equivalent license for IBM Cognos TM1 Contributor. This is great news for clients looking to compliment Planning with TM1.

The IBM Announcement You Probably Missed, ROCKS THE COGNOS PLANNING WORLD!

IBM Cognos recently announced a licensing change in IBM Cognos 8 Planning Version 8.4.1 . If you weren’t anxiously awaiting the news like Lodestar was, I’ll bet you missed it. Why were we anxious for the announcement? It paves the way for IBM Cognos clients to leverage both Enterprise Planning and TM1 to provide the Best of the Best Planning solution at a reasonable price.

Innovation Part 2

So, hopefully you read my previous blog on Innovation.  It is essential to success in this market.
WHAT IS INNOVATION: A new way of doing something.
Let’s look at a great example of innovation.   In 1968 at the Olympics in Mexico, a man named Dick Fosbury set an Olympic record with a move that others called [...]

Which D-List is this?

The idea behind this is that when creating a D-Cube you create it putting the D-List in order of 1-5. This helps in priority conflicts of formulas and formats. Plus, when you browse the library the D-Lists are sorted by the type of D-List. Easy Right? Maybe yes, Maybe no. The naming convention is open to interpretation. If I have a D-List for Years and it has no calculations, is it a 4 or a 3? What about a D-List that has Current Year Budget, Prior Year Actual, and a variance between Current Year Budget and Prior Year Actual. Is this a 5 since it has versions or is it a 1 since there is a calculation? What about a D-List that was a 3 but I’ve recently included a subtotal in the D-List do I need to go back and rename this to a 2?

The numbering method works great in a training class environment to help us learn the dimension order when creating the D-Cubes. After we learn the order, do we really need to number our dimensions?

Integrating Cognos Planning and BI - Dimension for Publish

Choosing the dimension for publish is one of the most critical steps in the Generate Framework Manager model process. The dimension chosen for publish will be treated as the Fact table in the publish process. In addition, the Generate Framework Model admin extension will model the dimension chosen for publish as the fact table. More simply put, the dimension chosen for publish will be your measure dimension.

Integrating Cognos Planning and BI – Reporting Applications

It is always important to consider any Business Intelligence requirements during the design of planning applications to ensure planned information is structured in such a way that it can be leveraged in Cognos BI. Anyone who has ever used planned information as a source for reporting will attest. That being said, it is not always possible to create a planning application that is both Planning and BI friendly. As a result, we have pioneered the concept of a reporting application to help bridge the gap between Planning and BI Requirements. I like to think of it as a mini data mart masked as a Cognos Planning application.