IBM Cognos is a full-featured business intelligence suite by IBM, designed for larger deployments. It comprises Query Studio, Reporting Studio, Analysis Studio and Event Studio, and Cognos Administration along with tools for Microsoft Office integration, full-text search, and dashboards.
$10
per month per user
Infor Birst
Score 3.7 out of 10
N/A
Infor Birst offers multi-tenant cloud BI for deployment in a public or private cloud, or on-premises. It provides an in-memory columnar data store and a BI layer comprising a reporting engine, predictive analytics tools, mobile native apps, dashboards, discovery tools, and an open client interface.
Birst provide a much better web UI and end user experience and distribution mechanism than both Tableau and SSRS. Power BI simply did not have the full complement of features that we needed at the time of our selection to be competitive and Pentaho was too custom and would have …
Cognos - this tool is also more difficult to set up, takes more time to develop dashboards, harder for the business user to navigate MicroStrategy - this tool is also more difficult to set up, takes more time to develop dashboards, harder for the business user to navigate MS …
We use other BI tools within the organization. These tools have been there before we got BIRST and while comparing, BIRST did score well against these tools but the migration cost to convert existing reports/data prevented us from replacing those tools with BIRST.
QlikView - on the face, similar system design, agnostic data sources, Cognos - previous experience MS Reporting Services - fit with internal systems/tools/environment.
It came down to QlikView, Tableau, Cognos, and Birst. QlikView and Tableau were eliminated because they are simply reporting tools, and it was eventually determined that we wanted to set up a data warehouse. Birst beat Cognos because it had nicer looking reports, was much …
Our first and most basic scenario was to automatize the creation and publication/sharing of business reports that used to be created manually by employees throughout our organization. Using Cognos for that first use case worked well. The advanced analytics functionalities we used on the aggregated data were also as expected. However, the user interface is not always intuitive, and there is a steep learning curve, so I would recommend Cognos only to large organizations where there is a need for the most advanced functionalities (AI analysis/prediction).
Birst is well suited for an organization looking for a cloud-hosted analytics solution that is contained within one package. It is able to connect to a very wide variety of different data sources, and has options for either light or involved ETL procedures, depending on the users experience with preparing data. As with any BI project, it would not be suitable for an organization where there is no dedicated team to maintain and manage the project.
Birst is an platform that provides connectors to some of the applications we use, but also allows us to bring in data from disparate systems to perform ETL and integrate all of the data for analyses. It makes no assumptions about your data, which is good for us, as we have a lot of customizations to many of our systems.
Sometimes there might be performance issues when dealing with large and complex data.
Although IBM provides full documentation but sometimes it's difficult to find answers to questions and connect with their customer support.
It relies on external tools for data cleaning, transformation and also for some integration tasks. It can also improve on providing wider range of data sources for integration.
For an existing solution, renewing licenses does provide a good return on investment. Additionally, while rolling out scorecards and dashboards with little adhoc capabilities, to end users, cognos is very easily scalable. It also allows to create a solution that has a mix of OLAP and relational data-sources, which is a limitation with other tools. Synchronizing with existing security setup is easy too.
We have been able to overcome any of the drawbacks we've found with Birst easily and it has fulfilled almost all of our analytic needs to date. Having seen their roadmap it would be highly unlikely we would move away from this platform any time soon. You simply can't beat the functionality that Birst provides for the price and the things I see coming out of the company solidify that our decision to choose Birst was the best possible choice. We have never regretted the decision.
We have a strong user base (3500 users) that are highly utilizing this tool. Basic users are able to consume content within the applied security model. We have a set of advanced users that really push the limits of Cognos with Report and Query Studio. These users have created a lot of personal content and stored it in 'My Reports'. Users enjoy this flexibility.
I would like to see additional usability put into the ETL scripting. Recently, Birst added a nice function reference inline to formula creation which has kept me from having to return to documentation so much. The same in ETL would be very beneficial. The interface problems related to the Flex framework are being addressed in a rewrite to HTML 5, but for now they are still a hindrance to a higher usability rating.
Reports can typically be viewed through any browser that can access the server, so the availability is ultimately up to what the company utilizing it is comfortable with allowing, though report development tends to be more picky about browsers and settings as mentioned above. It also has an optional iPad app and general mobile browsing support, but dashboards lack the mobile compatibility. What keeps it from getting a higher score is the desktop tools that are vital to the development process. The compatibility with only Windows when the server has a wide range of compatibility can be a real sore point for a company that outfits its employees exclusively with Mac or Linux machines. Of course, if they are planning on outsourcing the development anyways, it's a rather moot point
We frequently experience -103 errors due to us using the Live Connect functionality, which does not seem to handle even minor interruptions in connectivity, and treats all future connection attempts or data requests as errors, even if the issue does not exist any longer
Overall no major complaints but it doesn't handle DMR (Dimensionally Modeled for Relational) very well. DMR modelling is a capability that IBM Cognos Framework Manager provides allowing you to specify dimensional information for relational metadata and allows for OLAP-style queries. However, the capability is not very efficient and, for example, if I'm using only 2 columns on a 20-column model, the software is not smart enough to exclude 18 columns and the query side gets progressively larger and larger until it's effectively unusable.
Everything runs very fast and smoothly. The only process that I wish was faster would be processing the data after uploading new data or making changes to the existing data model. It can take 15-20 minutes (roughly) to upload and process new data once you start getting into 10's of millions of rows. Given my experience with how long it takes me to pull the same data using SQL Server Management Studio, I don't think Birst is unreasonably slow - but for me to give a higher rating, I would want it to be unreasonably fast
Why is their web application not working as fast as you think it should? They never know, and it is always a a bunch of shots in the dark to find out. Trying to download software from them is like trying to find a book at the library before computers were invented.
When we have an issue that is stopping our business from proceeding, I want answers sooner than later. While Birst does have a published response time for each case level, we always wish it could be quicker. What response improvement could there be with a larger support team? In response to first question: Blackhole of issues - Birst needs to improve upon closing issues that resolution was dependent upon code fixes or enhancements, perhaps someone to add a comment on all case tickets at least every 60 days. Escalation - I always have the ability to electronically or via phone escalate a ticket. I also have my Customer Success Manager through whom I can escalate topics.
Onsite training provided by IBM Cognos was effective and as expected. They did not perform training with our data which was a bit difficult for our end-users.
I have attended two different training sessions. The first one was my initial training on the system. It was well paced, clear and concise. If there were questions that were not able to be answered by the instructor, he took down the question and actually followed up and provided us a response quickly. The second session was specific to the dashboard and report design components. This training was very good though there were some attendants who had little or no experience and their questions slowed the class.
The online courses they offer are thorough and presented in such a way that someone who isn't already familiar with the general design methodologies used in this field will be capable of making a good design. The training environments are provided as a fully self contained virtual machine with everything needed already to create the environments. We've had some persisting issues with the environments becoming unavailable, but support has been responsive when these issues arise and straightening them out for us
Although I found the online resources helpful, a lack of appropriate examples for certain tasks key to report creation and advanced modeling make the online training/documentation less than perfect. For an inexperienced BI professional, the online training would not enable a streamlined launch of the product.
Make sure that any custom tables that you have, are built into your metadata packages. You can still access them via SQL queries in Cognos, but it is much easier to have them as a part of the available metadata packages.
Have clean data! Birst flexibility allows - Start small, then introduce functionality and complexity along the way. If you try to present all the functionality [bells and whistles] and wow them, but bad data is uncovered, the end user blames the new application and turns away.
In the past Management had used Excel and Workiva capabilities to create the reporting dashboards that were being used to make decisions. Since switching to IBM Cognos Analytics the Company has been much more efficient and decision making has been streamlined. IBM Cognos Analytics was chosen due to its reputation and data visualization capabilities and neither have been wrong.
During the vetting process, we looked at 14 different products (one of them internal) to see if they would fit our needs and whittled it down to this one over a three month period. We did not contact sales for all of them (sales sites were enough to rule out some), but did have a lot of demos with a significant portion of them and reviewed several of the major industry studies as well. We had representatives of both user interests/design and the technical backend on the evaluation process.
The major features we were looking for a product that we could embed inside our own SaaS application, connect to a sharded Postgres database, had multitenancy and allowed for customer generated reports/ self-reporting. Some of the minor "nice to have" features we were looking at was scheduled reports, especially if we could plug it into our own scheduling system (for CAN-SPAM compliance), internationalization, and support.
In the evaluation, Birst hit all of the must-haves and enough of the nice to haves that they made it down to our final two and the trial was the clincher to make it our final choice.
The Cognos architecture is well suited for scalability. However, the architecture must be designed with scalability in mind from day one of the implementation. We recently upgraded from 10.1 to 10.2.1 and took the opportunity to revamp our architecture. It is now poised for future growth and scalability.
we can see that loading a lot of data can cause a noticable slow down in performance. Birst support indicated that they don't really consider anything less than 30 seconds to be an issue, but that is not the case for our customers, so we have had to change some of implementation to address this
Being a manufacturing company we tend to lag behind technologically. But having all the data for different ERP systems in one place has been an eye opener for the executives. It has lessened the need to convert some legacy ERP systems.
Having such a simple reporting tool is a great asset to some of our sites that have traditionally had trouble gathering data from AS400 systems.
