IBM Cognos Reviews

The jobstreams and the ways SQL-scripts can be effectively organized behind icons.

• It gave the organization a better insight in the quality of the data, which in many ways was poor.
• It gave the call center the possibility to monitor its effectiveness and efficiency a lot better.

• The Cognos Data Manager is very datamart/Kimball oriented, and it should be made more flexible, so that it can be used for architectures like Inmon’s or a data vault.
• Some of its components are not very stable (for instance the lookups).
• The prescribed working order (dimensions and hierarchies, then fact-tables) makes implementing design adaptations a complex and risky operation: loosen one thread, and a lot more go with it, and this should me made more flexible.

I've used it roughly for more than a year.

The stability of the Cognos Data Manager is quite good. It doesn’t crash very often, but of course making daily backups of your work is a wise thing to do, as with any tool.

No issues encountered.

We only had a company provide digital training. Their communication was poor, and they worked with a call center which was totally uneffective.

I had to make do with what could be found on websites and the internet. The information IBM gives here is solid, but very technical and hard to read. Other websites have to be handled with care as many contributions are more enthusiastic then useful.

I started using Cognos Data Manager because the company I worked for already used it.

To start with SSIS:

• SSIS is a lot more flexible than the Cognos Data Manager. In the latter, the user is pushed into the direction of a Kimball datamart architecture (data marts, which in a later stage are to be integrated into a integrated solution). SSIS leaves a lot more room to the user to make his or her own decisions (and suffer the consequences of these)
• The user interface is a lot more user friendly in SSIS, while Cognos Data Manager is somewhat outdated (but can in capable hands still be used very effectively)

In comparison with large scripts in Oracle and SQL Server:

• The Cognos Data Manager provides a comparison of large scripts for a real and substantial improvement. The icons and jobstreams provide a lot of structure, and are a lot easier to read and interpret than large scripts which can be hundreds of pages long
• Functions like lookups are very nice, but not always enterily stable (which is a serious drawback in their use)
• Combining Oracle and SQL Server databases with each other is a definite strong point of the Cognos Data Manager (although no longer a unique selling point)
• The SQL-scripts are pasted behind the icons. It makes tracing errors and the logic of processes a lot easier

It had already been installed, and I got a lot of support from other people in the company. I have no experience with a vendor team.

The company I worked for got a better understanding of its poor data quality, and many inefficiences in its operations. But in their mindset, speed is everything, and precision is often regarded as something of a luxury. They got more insights, made a lot of noise about it, but made no structural efforts for improvement.

• Consider carefully if you want a Kimball architecture with datamarts for your datawarehouse. If so, the Cognos Data Manager is a good option. If not, I think you should reconsider
• Consider what exactly you want to achieve with your datawarehouse. For having a historical database, it can be quite effective. For daily control, in most cases a datawarehouse architecture is unsuitable and unwieldy. Direct reports on source systems are than a better option
• If your organisation has issues with data qualities, a datawarehouse won’t solve these. It can only make these visible (and there are probably a lot of cheaper ways to do that)

• The solution is very flexible, but IT oriented.
• It is an enterprise level solution for BI that holds value in a traditional BI sense.
• It is a full platform that is designed for the full cycle (data warehousing to pixel perfect reporting).
• It provides a managed IT environment.
• It does not excel in any one specific area, such as in visualization. However, there appears to be a lot of development with complementary products such as Watson Analytics and TM1.

We have been able to provide managed data sources and packages to end users. They can use this content to do their own reporting without IT assistance.

It is similar to a competency center, in which IT will help resolve or work on complex requirements or projects.

I would like to see the following improvements:

• Tools: Dashboards, visualizations, and the simplification of the available tools
• Licensing: It is very difficult to know which studio needs to be passed to which users or projects. This is because licensing and tools are confusing and they overlap with one another. Even for OLAP, there are issues with transformers, TM1, dynamic cubes, and compatibility with other vendors’ cubes.
• Simplicity: There are CQM and DQM modes, so it can become very technical.
• Consistency: They made a decision to deprecate Query Studio and migrate to Workspace Advanced. However, that did not happen. They wanted to push the new version which will deprecate Workspace Advanced as well.

Basically, Cognos has been a traditional BI platform. Lately, there has been a trending push for more of a modern BI approach that is heavier on the self service side. This approach does not care for the whole cycle of waiting on a request to go through the IT development chain in order to make it happen for the end user.

I have used it for about nine years. My company has been using it for about six years.

We are on Linux, so we rarely have stability issues. We could run into resource issues, but that would be space or hardware related.

I did not encounter any issues with scalability. Cognos is very good at scaling.

Vendor technical support could be improved. It used to be really great. However, it seems like the focus now is on newer development. The support may not be that good for the more difficult issues.

When I came here, they did not have another solution. In my past environment, they had Business Objects, but ended up switching to Cognos for the flexibility it provides.

If you are doing a standalone installation, then the initial setup is easy.

However, if you get into a distributed environment and load balancing, then it requires you to really know the application well. You need to know about the server level for all of the configurations.

Licensing has been simplified over the years. However, we do not like their Processor Value Unit (PVU) model and prefer the named user licensing route.

Pricing can be expensive depending on the number of administrators or developers. Regular consumer licenses do not cost as much. They also have a cloud solution.

If implementing on-site, you will need to have skilled administrators and developers who are experienced with this solution. They are in demand, so they will command a high salary.

Reporting, which includes building reports out of relational schema.

This product has made enhancements in building dashboards, incorporated changes to make it easier for the business users to import and use their metadata to do analysis. That is included in Cognos Analytics version 11. It is more user friendly and in some areas, you do not necessarily depend upon IT to build reports. There is one tool like Cognos Workspace Advanced, which is the hybrid of Query, Report and Analysis Studio.

Dashboarding: Actually right now in Cognos 10.2.2, Cognos Workspace is the dashboarding studio to build dashboards. But I believe some work still needs to be done in order to compete with other tools like Tableau, etc.

Tableau has in-memory capabilities and a lot of depth in visualizations. It can analyze and display a lot of intuitive data quicker. Also, Cognos Dashboard requires more IT skill to create and maintain as compared to Tableau. However, the new version, Cognos 11, is a big step in that direction to make it more user friendly.

Dimensional Modeling Reporting: Dimensional Modeling is used for reporting where the reports can be drilled down to a detail level. It works on the same concept as cubes, except it is live. Performance is a big factor, so it requires lot of expertise to build the right kind of model with the proper aggregation level; otherwise, the performance is impacted. Plus, it requires MDX knowledge to enhance/maintain the model, because SQL doesn’t work in dimensional modeling.

I have used it for eight years.

I have not encountered any stability issues.

I encountered scalability issues when different users are querying at the same time or if one user is running a big report involving large query (SQL).

Technical support is 8/10.

Pricing and licensing is high. It can be lowered.

I didn't make the decision to choose this product.

It is a good product for reporting, not necessarily for dashboards.

The ability to interface with multiple server types (databases) to retrieve data and report on that data in an all-inclusive environment is beyond a doubt the best feature. The reporting interface takes getting used to, but once you familiarize yourself with it, you can create some truly amazing graphical and informational reports.

BI has allowed our product to become open ended as far as the client data is concerned. We have proprietary reporting that is standardized but doesn’t capture everything. BI expands that functionality to include any and all customization a client may have and still get their data.

The GUI for reporting isn’t very user friendly, so beginners struggle with feeling overwhelmed when seeing it for the first few times. I spent my first two years just getting used to where everything was and how to script simple things without looking them up. A better dictionary of examples for functions would have gone a long way with helping me.

They’ve improved it and it’s much better than it was, as well as the tooltips on the page, so I’m thinking they had similar feedback in the past. When I engage new clients on the product, though, they are almost always overwhelmed by the interface and I don’t have a good solution other than redesign. They could create a secondary Page Design pane that is simpler for beginners. They could even merge Query Studio with Report Studio, and as you familiarize yourself with the Query pane and need a little more functionality, you can flip to the Report Studio pane. I would prefer a secondary pane option over an entire redesign since I’m familiar with the current structure.

I’ve used Cognos BI for over seven years now.

I have not encountered any stability issues.

I have not encountered any scalability issues.

I personally have had no problems with IBM tech support, though my experience is from a reporting standpoint not an implementation standpoint.

I did not previously use a different solution.

The only advice I can give here is that there are several third-party companies that will handle implementation as well as provide continued support post-production. I recommend doing your homework and hiring one of them to take care of implementation and support, if you don’t have a dedicated team to do so internally.

Before choosing this product, I did not evaluate other options.

There is a huge cost up front to purchase and get it off the ground, but once you have it, you won’t regret it. To have access to all of your data at your fingertips is impressive and I think it’s a must have for medium and large companies (+500 employees).

Reporting and dashboard capabilities are the product’s most valuable features.

It provides enterprise-level reporting across all departments.

ETL features have room for improvement.

I have used it for nine years.

When we have more than 1000 users logged in to the system, we can see slowdown in terms of performance.

I have not encountered any scalability issues.

Technical support is 8/10.

I did not previously use a different solution. We have always used IBM Cognos product suites.

Initial setup was pretty much straightforward.

We certainly looked at other BI products such as SAP BusinessObjects, OBIEE, Oracle Discoverer, WebFOCUS, Argos, and MicroStrategy but Cognos was our unanimous choice.

The product’s most valuable feature is the open environment where we can build from scratch without too many constraints on calculations because that allows us to have extensive customization.

I implement projects using the product, and every time we implement we end up discovering a lot of unaccounted cash that was either being paid to the wrong person or extra money being paid which was unaccounted for. This helps auditing the sales personnel's incentives and also analyzing what incentives show a correlation to an improved performance.

• DBMS scalability
• Debugging
• UX for admins who are developing on the software

I have used it for 4+ years. I am certified in this tool and I primarily work on implementing this tool (among others) for various organizations’ ICM needs.

I have not encountered any stability issues.

I've encountered issues where calculation runs took upwards of six hours because of data storage and build issues.

Technical support is excellent.

I did not previously use a different solution.

It's simple enough to install because IBM takes care of initial setup.

Callidus is usually this product’s competitor.

The product is as good as the team implementing it.

Cognos contains many components that make up the entire Cognos suite.

The starting point is the meta data designer, which is Framework Manager.

Framework manager allows you to pull in database tables from any type of database, this is referred to as the ‘Database Layer’. Then you create the Business Layer where you update the column names with ‘business names’ and remove the geek speak or database names. You can also include data transformations and table joins in this layer. Finally you create the Presentation Layer that points to the Business Layer. The presentation layer is usually the only layer that is published in the Cognos package.

Cubes contain data hierarchies and time dimensions to allow a report consumer to ‘click and drag’ the data elements that they want to analyze to their reports.

Transformer is the product that allows you to pull large amounts of data together, to allow clients to slice and dice their data any way that they want. Report Studio allows for sophisticated reporting. Each of these is valuable; there is not just one that is more valuable than the other.

We developed sophisticated reports in the fundraising area, which pulls in data from many different databases and presents graphs, charts and summary financial information over any time period that the person wants to see. This set of reports are run or used on average 15,000 times per month by hundreds of end users.

Another example is building financial data using cubes. The cubes contain 11+ years of financial data and we have the add-in for Microsoft Excel, which allows end users to build their own ad-hoc reports for trending and analysis.

Right now, we are in the midst of implementing a brand new version of Cognos, named Cognos Analytics. This version is very, very different from prior versions. We are finding ‘undocumented features’ on a daily basis and reporting issues to IBM. We are working thru the issues, but it is very stressful on us, finding out functionality that was in the previous release but is missing now in Cognos Analytics version 11.

Here are just a few examples of issues that we are facing as of today! We have identified other issues, which have been resolved or we have workarounds.

- In our CA production environment, we imported reporting content that included saved output of financial reports. The saved output did NOT import and therefore users will not be able to pull up the reports in production! This works in our other CA environments, but failing in production!

When you have a saved output report that contains links to drill thru reports and you want to open them in a new browser window, it fails! You have to go in and modify the reports to open in the same window, so now the user cannot see the original report that they clicked on.

You also lose the ability to export reports to Excel or PDF when you have drill thrus to a new window.

If you run a report, have it emailed out and you attach a link to the report in the email, it fails only in our production environment.

The Search and Select prompt fails on the prompt page.

I have used it since 2005, so 11 years now.

The product is stable, but we continue to find issues due to the product’s newness.

The product is very scalable and can support thousands of end users. HUGE companies are using this product.

I rate technical support with a 8-9/10. We occasionally need to escalate issues to senior technical support.

I was an independent consultant and have used competing products; they all have their quirks. Here at the university, we for the most part use Cognos.

The initial setup can be complex for large organizations; for smaller companies, it is easier.

For the university, Cognos is very competitive, because IBM offers huge discounts to higher education. My advice would be to work with an IBM business partner.

Cognos was already installed here when I was hired. The university hired me for my experience.

Hire an experienced business partner, who can provide ongoing support and training.

I really appreciated Report Studio, because it can create complex reports fast!

Report readiness has really improved! Cognos provides multiple tools to help create reports. That helps provide clients with what they need ASAP!

Data Manager, InfoSphere, and Framework manager can be a little more user-friendly. But we are able to manage and learn from it. We can create data sources in order for the other data tools to function.

I would like to see a more user-friendly interface. Sometimes it can be confusing to navigate through it.

I have used it for one year.

I have not had any stability issues. It is great software with great tools!

I have not had any scalability issues.

Technical support has been great. IBM has a wonderful support portal where you can submit tickets for issues that are way too complex to understand or control on your own. The fix central portal will get back to you ASAP and provide solutions to fix your problems.

The company has always used Cognos, as far as I know. Personally, I transitioned into this post when they were working with Cognos. I found the transition into Cognos to be easy.

I never encountered this issue, as it was already set up. We are currently in the maintenance and monitoring phase.

It is a great product. It is very simple to use and easy to monitor and maintain.