I’m going to start this post assuming you have already CREATED a model / library in Cognos Analyst and are familiar with Cognos Analyst models in terms of modeling and creating an application. Once the Analyst model / library is ready, the end users must be able to access the cubes, enter data, manipulate data and perform all manner of tasks. This is done via the web-based interface which is basically where contributor comes in. The Contributor Application is basically a published version of the Analyst model. As a published model, it is different or enhanced from the model / library in the following ways:
1. Provides a web-based front-end to the end users to access the application(s)
2. e.List creation and maintenance (Analyst can use a dummy placeholder for modeling purpose)
3. Allows user access and security settings
4. Data Validations
5. Translations (or Aliases in Hyperion Planning jargon as far as I know)
Essentially the model from analyst is copied into a contributor application so the underlying structure is the same. The other options like security, e.List, data validations, etc. which are not part of Analyst are managed here and the application is made available to the end users.
The modeler or designer can continue to work on Analyst without impacting the published application until the changes are synced to the contributor application. Even then the changes are not reflected until the Development version is migrated to the Production version (a process that is known as GTP – Go To Production).
I’m going to start this post assuming you have already CREATED a model / library in Cognos Analyst and are familiar with Cognos Analyst models in terms of modeling and creating an application. Once the Analyst model / library is ready, the end users must be able to access the cubes, enter data, manipulate data and perform all manner of tasks. This is done via the web-based interface which is basically where contributor comes in. The Contributor Application is basically a published version of the Analyst model. Continue reading →
IBM Cognos TM1 is enterprise planning software used to implement collaborative planning, budgeting and forecasting solutions, as well as analytical and reporting applications. Similar to Hyperion Essbase, TM1 is a multidimensional data store however it only supports data storage at the “leaf” level.
Having worked with Hyperion Planning solution, I decided to explore the Cognos TM1 offering. The latest version is 9.5 which came out February 9, 2010 and there has been some considerable improvements – the most visible being TM1 Contributor which is a web-based front end. Previously TM1 was basically managed through the Microsoft Excel interface and the TM1 Architect.
In the subsequent posts I will be taking a look at the Cognos TM1 version 9.5 offering starting with the installation.
Teradata was the first to announce a database that could handle 1TB of data. They developed a database that was built to work on a massively parallel scale and hence the high speeds in working with large volumes of data. Teradata was (for at least five years in succession) one of the fastest growing company at that time.
IBM published “Information Warehouse” framework as early as 1987 and hence can be regarded as the other pioneer of data warehousing.
Enterprise Data Warehousing has been the key trend in corporate computing in the 1990s and continues to be so today.
IBM has made an announcement about a new service line being launched. This new service line will be known as Business Analytics and Optimization – more fondly as BAO. This will be part of the Global Business Services (GBS) division. Continue reading →
As a consultant I am usually making recommendations to customers for processes and products. On a recent discussion with a client (a major bank) I was basically working out an enterprise architecture to support their reporting requirements. In a move to consolidate its operations and personnel the bank has made a central body to take charge of ALL reporting requirements of the organization locally as well as globally. Continue reading →