IBM Cognos Reviews

Report Studio.

Any area for which developer has requirements can be improved, streamlined e.g. Marketing, Compliance, Surveillance, Hotel Accounting, Casino Accounting .

• -Pulling images directly from database with Report Studio
• Graceful ways to consume / report on XML or JSON structure received as a result of API call
• Timely bug fixes

13 years.

I would say IIS configuration is more complex than expected

Possibly but there could be multiple reasons for the environment being unstable especially on virtual servers.

Not really.

Customer Service:

It depends on sales rep. It may vary. Judging on we experienced it could be 6-8 on scale 1-10 (10 is the best).

Technical Support:

It depends on sales rep. It may vary. Judging on we experienced it could be 6-8 on scale 1-10 (10 is the best).

No previous solution.

The first time ever setup is always more complex. After that it is pretty much "known road." Again, IIS configuration may be more complex than it should.

It has always been in-house implementation.

I do not have answer on this but in some areas it may be very high.

Yes. Business Objects, Crystal Reports (while back).

Go ahead, you will not regret.

The Reports and Query Studio functions have been very valuable.

It enables me to see trends of data we have from different angles and each end-user can run ad-hoc queries themselves.

Framework Manager, Map Manager, and Reporting Database Connectivity features should all be free.

3 years including previous version

I was unable to use oracle 64 bit client to connect with oracle 64 bit databases. However, because of Linux I had to use 32 bit anyway.

Not much

We had some minor issues with scalability.

Customer Service:

7-8 out of 10

Technical Support:

8 out of 10

We changed because of the offer of more features and technical support than our previous solution.

For us it was complex to do it for the first time and too much R&D had to be done. Later on it was easier. It may have been complex as it was our first time setting up the Cognos.

Implementation was done by an In-house team who learned from scratch.

Good. It helped the purpose for which we used it.

I have little knowledge of this but I think we pay for each report we deploy

We looked at three other solutions, Netezia, Xplore, and Netcool.

Go for it but it will require training.

- The ease of use and ability to create things.

- The security provided by IBM Cognos compared to other tools.

- Reduced time for answers on business panels; highly visual and interactive control without long waits.

Users used to have to wait long times to see information but can now view their information quickly and easily with IBM Cognos and also given the availability you can create your own reports.

I have been using IBM Cognos for about two years.

No, deployment is all right.

No, no problems were found.

No, no problems were found.

Customer Service:

We were given good service, fulfilling all the requirements that were requested.

Technical Support:

The technical support provided by IBM is good, helps you with any problems with the tool.

No.

IBM Cognos is a good tool for viewing reports, allows us to use the tool in an interactive and easy way, with the option to display it on various mobile devices.

The report designer, Report Studio, is incredibly versatile and easy to use. Reports can be served in multiple formats, such as PDF, HTML, Excel, or even as a JSON data source. The meta-modeling tools allows for a complex security system which can automatically filter data, in any report or ad-hoc tool, based on a user's roles or groups.

The use of ad-hoc tools, like Workspace, has reduced the number of design requests, freeing the reporting team for more pressing and difficult problems.

Dashboards are slow compared to other tools currently on the market. Visualizations are improving, but still difficult to get just right. The default mapping solution included is only useful for the most basic requirements.

9 years.

Some users are afraid using adhoc tools. Migration projects which fail to take into account the different strengths of Cognos, demanding 100% pixel perfect migrations, will often fail.

The querying engine occasionally chokes on very large or complex datasets. Poorly designed meta-models can also cause trouble. Cognos will occasionally create dump files that can be larger than a gig each.

International distributed systems can have latency and consistency issues. The default round-robin load balancing works well, but the admin needs to remember to configure the weighting correctly.

Customer Service:

Enhancement requests take a very long time to get into production. IBM works on the "squeaky wheel" principle.

Technical Support:

IBM technical support can usually solve any problems. If it's not something they've run into previously, it can take a long time to get a straight answer. They provide hotfixes for really urgent bugs that are affecting production.

Most of my clients are long time Cognos users. Some of them are migrating away from Hyperion Brio because of lack of support.

At the most basic level, Cognos is a "next-next-next" install. While this works for very simple, low usage systems, in order to really get the most out of it it requires a great deal of tuning.

As a consultant, the vast majority of my clients hire out the development team. A few times I've been brought on to provide additional temporary support or training.

Hire experts to come in and do the initial setup and meta-model. Learn from them. Get training. Training is invaluable when it comes to using the various tools.

Cognos Reports, Dashboards

Fast KPI tracking, Complex data analysis for decision making.

Versatility, Performance (speed)

5 years

It's hard to change built-in options.

Rarely had issues with stability.

No issues with scalability.

Customer Service:

Depends on the support structure.

Technical Support:

Depends on the support structure.

In-house team

Well, I liked the split Cognos- used to have 2 differents products for reporting. One very friendly for user (query studio) and other one more for super user or tech user (Report studio).
The AdHoc reporting (query studio) are very easy with query studio but this happens only if the package is well done by the modeler. The most valuable feature in query studio is Develop/ Reduce group in a list. For Report Studio, the possibility to create report from SQL Query direct, easy, simple and efficient :)

We reduced IT requests for reporting and improved reports standards. High quality reports.
We used templates and reuse components so it's easy to change lots of report quickly.

Administration and security.

I'm with Cognos's products since 1997. (First products I used was Impromptu, Transformer and Power Play). Last version I have used is 10.1 (Query and Report Studio).

Well, developing packages makes deployment a bit long in case of emergency.
Also, for performance issues, avoid to connect the package's data on OLTP databases. Always use de-normalised databases, (ODS) or OLAP databases.

Server not responding some times

No

Customer Service:

With IBM it is too complicated, I used a partner.

Technical Support:

With IBM it is too complicated, I used a partner.

No

Not too complex.

At that time I was implementing with the Cognos team and in-house. People from Cognos were very experienced.

I can't remember. But now I'm looking to go around looking at BI Tools to advise my customers which ones are best according to theirs needs. I will go deeper in Microsoft (for the price), Tableau for the visualisation and easy deploy and of course Cognos because it can do all BI needs (but it's expensive).
PS. Cognos Express is welcome with lower licensing price.

If you are looking for an all integrated, scalable and high quality reporting tool, Cognos is a solution to consider. But, the price is a factor too.
You need to define well your needs for reporting, chose the right component you want to start first and start small.

Drill through reporting, ease of use, ease of design, and functionality.

This BI tool helped automate and centralize production reports. It provided intuitive navigation for end users. It helped to positively change the reporting landscape while addressing customer needs

It definitely needs better data visualization. I needed to couple Cognos with Tableau to provide a complete reporting environment.

2 years for Cognos BI series 10; 2 years for Series 8 and 7 years for Series 7

No, the company I worked for had a Corporate user (many end users) license which enabled license costs to be minimal.

Customer Service: I did not work directly with Cognos support.Technical Support: I did not work directly with Cognos support.

The IT group in my organization was responsible for the set-up. On version 8, Cognos seemed very unstable. Cognos 10 was much improved.

In house

IT group handled this aspect.

Yes. Our company had many BI tools to choose from but Cognos was the most sustainable and scale-able.

There are many BI tools out there to choose from. Cognos might be the right solution for you but this decision needs to take into consideration the size of your user group, the cost per license, the functionality needed for your reporting infrastructure, and the in-house BI knowledge of the BI tool that you choose.

Graphical interface is good

Ad hoc reporting

Basically, our support to enhancement was our corporate team. Where the Oracle Quality module has more flexibility to develop internal tables to gather data. The Cognos BI team doesn’t have this dynamic approach to do the enhancements. So, Corporate decided to replace this application with Oracle OBIEE.

5 years

No

No

Yes, When it’s integrated with Oracle for Quality reports

Customer Service: 9 out of 10Technical Support: 9 out of 10

Never before.

Straightforward

In-house

No

Consider other alternatives.