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.
$30,000
Per 20 Users Per Year
Tableau Desktop
Score 8.3 out of 10
N/A
Tableau Desktop is a data visualization product from Tableau. It connects to a variety of data sources for combining disparate data sources without coding. It provides tools for discovering patterns and insights, data calculations, forecasts, and statistical summaries and visual storytelling.
We preferred to have an all-in-one cloud solution that could connect to Salesforce.com and on-premise servers. I thought the combination of ETL built into a star-schema was unmatched. QlikView could do something similar, but the resulting data file was not an enterprise grade …
Both Tableau and Qlik needed back end data preparation done before they could start. BIRST has that full process integrated. Most importantly, BIRST's fully integrated stack (we chose the cloud option) allows you to focus on delivering what your organization needs, without …
Birst lacks external modular components power bi has currently. New custom visuals, charts, statistical models created by third party vendors can be added to existing dashboard and enhanced.
Birst lacks interactive dashboard functionality and external inputs.
We evaluated and compared Birst, OBIEE 12c, and Tableau based on several criteria such as "Data Analysis & Discovery", "Data Integration", "Security model", "Data Visualization", "User Experience" or "Infrastructure & Architecture". The only point where Birst was rated higher …
We compared Birst vs Tableau and Lumirra and there's no question that Birst is the best option from a cost perspective. Additionally, the ease of use complemented with our support team has allowed us to innovate on the platform quickly
Birst is not as intuitive or flexible for cube design and aggregations as using SQL Analysis services - at times seems an odd mix between gui based, and required specific code. Power BI is the tool of choice internally, but is limited by security settings that we need to enable …
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 …
Tableau does not have a common semantic layer like BIRST does so we use Tableau for data discovery purposes and BIRST for enterprise BI. Within BIRST, we can increase the level of data governance.
Birst was better than Domo for our needs because we could get in and tinker with it. Our impression of Domo was that it had a lot of connectors and ready to go reports, but it made too many assumptions about applications we use. We customize too much to use a "ready to go" …
We originally selected Birst because they are a Partner of our ERP system provider. We re-evaluated and reconfirmed that decision after our new investment through a one week prototyping exercise that proved how quickly something that delivers real content and value can be built …
We selected Birst over all other options due to the one-stop-shop nature of their offering - it allows us to rapidly develop and deploy a complete product quickly within a single tool.
Visualizations between the two are comparable. Processing and data access seems to be a bit faster with MS. Building dashboards is about the same, with Birst seeming to be a bit simpler (but that might be because I use it more).
Have used Tableau and Spotfire and the …
Birst allows direct access to an internal data store, which none of the products we evaluated provided. We also found the birst ETL layer far more powerful than the other platforms we considered.
Birst back end is more powerful yet complicated while Tableau's front end is more user friendly
Verified User
Analyst
Chose Infor Birst
We chose birst for the cloud based collaboration feature
Verified User
Analyst
Chose Infor Birst
Tableau is the leader in visualizations, from animation to ease of use, it takes the cake. But they do not (did not) have the data modeling capabilities that were offered with Birst. The step back in visualizations from Birst is more than made up for in their modeling. Qlik is …
Tableau Desktop
Verified User
Team Lead
Chose Tableau Desktop
Tableau Desktop has many more features than other competitors. Comparing Birst, the layout is much more efficient. Power BI and QlikView are as easy as Tableau Desktop. The price for Tableau is a disadvantage when compared to Birst and QlikView, but not against Power BI. …
We were interested in expedience at reasonable cost and so didn't do any sort of bakeoff, but tried Tableau first as a potential solution for moving beyond Excel for large scale data analytics. We picked it because it more than met our functional needs at a very reasonable …
Verified User
Analyst
Chose Tableau Desktop
It is easier to start with Tableau. The out of the box ready feel is more with Tableau than any of the other BI products. Product scalability is at a steep cost with Tableau but it gives the possibility to begin small and then grow as it proves its capability as compared to all …
Cass evaluated Domo, QlikView and Birst prior to selecting Tableau. It came down to cost (and by a significant margin); the others have relatively high implementation, hosting and other costs. Additionally, based on a recent Gartner "Magic Quadrant", Tableau exceeds all others …
Tableau is the only tool that can be exposed to end users so that they can build their reports and dashboards and can publish these without the help of a dedicated developer.
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.
Tableau Desktop is one the finest tool available in the market with such a wide range of capabilities in its suite that makes it easy to generate insights. Further, if optimally designed, then its reports are fairly simple to understand, yet capable enough to make changes at the required levels. One can create a variety of visualizations as required by the business or the clients. The data pipelines in the backend are very robust. The tableau desktop also provides options to develop the reports in developer mode, which is one of the finest features to embed and execute even the most complex possible logic. It's easier to operate, simple to navigate, and fluent to understand by the users.
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.
An excellent tool for data visualization, it presents information in an appealing visual format—an exceptional platform for storing and analyzing data in any size organization.
Through interactive parameters, it enables real-time interaction with the user and is easy to learn and get support from the community.
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.
Our use of Tableau Desktop is still fairly low, and will continue over time. The only real concern is around cost of the licenses, and I have mentioned this to Tableau and fully expect the development of more sensible models for our industry. This will remove any impediment to expansion of our use.
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.
Tableau Desktop has proven to be a lifesaver in many situations. Once we've completed the initial setup, it's simple to use. It has all of the features we need to quickly and efficiently synthesize our data. Tableau Desktop has advanced capabilities to improve our company's data structure and enable self-service for our employees.
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
When used as a stand-alone tool, Tableau Desktop has unlimited uptime, which is always nice. When used in conjunction with Tableau Server, this tool has as much uptime as your server admins are willing to give it. All in all, I've never had an issue with Tableau's availability.
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
Tableau Desktop's performance is solid. You can really dig into a large dataset in the form of a spreadsheet, and it exhibits similarly good performance when accessing a moderately sized Oracle database. I noticed that with Tableau Desktop 9.3, the performance using a spreadsheet started to slow around 75K rows by about 60 columns. This was easily remedied by creating an extract and pushing it to Tableau Server, where performance went to lightning fast
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.
I have never really used support much, to be honest. I think the support is not as user-friendly to search and use it. I did have an encounter with them once and it required a bit of going back and forth for licensing before reaching a resolution. They did solve my issue though
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.
It is admittedly hard to train a group of people with disparate levels of ability coming in, but the software is so easy to use that this is not a huge problem; anyone who can follow simple instructions can catch up pretty quickly.
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.
The training for new users are quite good because it covers topic wise training and the best part was that it also had video tutorials which are very helpful
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.
Again, training is the key and the company provides a lot of example videos that will help users discover use cases that will greatly assist their creation of original visualizations. As with any new software tool, productivity will decline for a period. In the case of Tableau, the decline period is short and the later gains are well worth it.
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.
If we do not have legacy tools which have already been set up, I would switch the visualization method to open source software via PyCharm, Atom, and Visual Studio IDE. These IDEs cannot directly help you to visualize the data but you can use many python packages to do so through these IDEs.
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
Tableau Desktop's scaleability is really limited to the scale of your back-end data systems. If you want to pull down an extract and work quickly in-memory, in my application it scaled to a few tens of millions of rows using the in-memory engine. But it's really only limited by your back-end data store if you have or are willing to invest in an optimized SQL store or purpose-built query engine like Veritca or Netezza or something similar.
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.
Tableau was acquired years ago, and has provided good value with the content created.
Ongoing maintenance costs for the platform, both to maintain desktop and server licensing has made the continuing value questionable when compared to other offerings in the marketplace.
Users have largely been satisfied with the content, but not with the overall performance. This is due to a combination of factors including the performance of the Tableau engines as well as development deficiencies.