Category Archives for "COGNOS BI"

BI is a Business Process, Not Software

One of the most common misconceptions about Business Intelligence is that it is a technology solution. I buy the right software, hire the right consultants, plug it in and Boom……I have Business Intelligence. The reality is that Business Intelligence is a Business solution supported by technology not a technology solution supported by the business. It’s a business process; and if it is not implemented as a business process, it won’t matter how much money you throw at it, you are not going to get the value you intended.

Continue reading

Crosstabs Dimensional Data in Report Studio

Let me first start by saying this is not a how to or even necessarily the right way to do things… rather some options to explore learned from hours spent cursing at the computer trying to get the seemingly ‘simple’ things to work in crosstabs. You know, things like adding two columns together, calculate a variance, or filter out crosstab rows with no data. I run into these issues most when I’m building financial reports where we’re comparing multiple forecast/budget versions across specific spans of time.

Continue reading

2 Cognos vs Business Objects…What’s The Difference?

I have been asked many times “What is the real difference between Cognos and Business Objects?” First, let me say that this is my opinion and not a recommendation for either product. I know that might sound strange because you are reading a blog written by a Cognos partner. Well I am going to give you my perspective based on my experience as a customer, which I think you would want instead of a sales pitch.

Continue reading

BI Reports Not Used?

Report writing is difficult for most people. It requires a level of detail and skill that most people simply don’t have the patience to learn let alone apply. Historically, most report writers are primarily Information Technology (IT) people with very little business experience which makes it impossible to explain why a transaction must be a debit instead of a credit. The language gap between report writers and users can be the difference between speaking English and Spanglish. The report writer might understand basic information about the business but not enough to optimize a report or the user doesn’t understand real constrains such as data quality, database design, or application limitations to understand why a report can’t be written just like their excel spreadsheet.

Report writer I have two words for you … Analysis Studio learn it, love it, use it. Business user I have the same two words… wait for it … Analysis Studio. Let’s assume that you have the groundwork covered such as a multidimensional Framework Package and you have Analysis Studio deployed, you can use Analysis Studio drop and drag functionality to bridge the gap between report writer and business user.

Continue reading
1 8 9 10