Infor Birst vs. Logi Symphony

Infor Birst OEM and embedded analytics are well suited for advanced analytics and business intelligence. It has flexible deployment features and a lot of configuration ability with low code - no coding ability. Ability to ingest data from multiple live data sources. Source data from multiple sources can be segregated into multiple sections based on business criteria. Easily searchable business terms (metadata) across all enterprise analytic content.

For all the scenarios I have so far worked on or I am currently working on, Dundas BI has proved to be more than adequate and apt to handle all of those. It is a very easy-to-use tool with quick shortcuts enabling you to prepare ad-hoc reports or dashboards in a matter of minutes.

Incentivized

• End-to-end solution, from raw source data, ETL, warehousing and reporting, Birst is able to do everything we need in one package instead of needing to develop and maintain multiple technologies
• Intuitive report development. The drag and drop creation of reports is simple. More complicated queries are easy to generate.
• Very user-friendly and interactive. A lot of nice features are available both for developers and end users to streamline the process of preparing and consuming data
• Rich API which allows us to programmatically interact with Birst

Incentivized

• Project organization from Development to Production, you get a production and development license but I think the best way to do it is with DEV and Prod project in the Production box. Use the development box for testing updates and really crazy things. With the Dev and Prod projects on the same box, you just publish from Dev to Prod and you are done. Users only have access to the Prod projects so no one can mess up what you are working on.
• Security - If you have a hierarchy (subsidiaries, divisions, department, teams) and you want each group to see only their data, then Security hierarchies are for you!
• Dependent filters! What's this you ask? Here is an example of how it can be used, in your company you have departments and who works for what department is in your database. You make a dashboard that has a department filter (only show these departments), a managers filter, and employee filter. Not every manager or employee is in multiple departments usually only one. With dependent filters you can say that the manager and employee filter are dependent on what is selected in the departments filter so when you go to filter them they only show the managers or employees that are part of that department, and you can even it do so employees are not only dependent on department but on manager as well. Then it gets even better as it can be done in reverse as well so when you select a manager then go to the department it only shows the departments he works for (there are better situations where this is more useful).
• It is scriptable! From calculate columns, null replacements, button actions, load actions, hover over events there a way to do what you want.
• They are constantly improving and listens to your suggestions.

Incentivized

• Birst prices are fairly expensive. License plus cost of users can add up pretty quickly
• Depending on the size of data, rendering of reports can take a little bit. Need faster processing of data
• Takes a little time to understand how to build reports, not the most intuitive UI

Incentivized

• Not too many cons for how we use the application. It really is easy and powerful. Very powerful.
• Licensing is one thing that could be looked into. It is simple, but a little confusing. For example, if I get a license today, but a new release comes out tomorrow, it seems that the license doesn't work with the new release. Maybe that is by design, but it would be nice to clearly understand.

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.

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.

We are still in the implementation phase, but so far we are finding it to be easy to use and learn. The eLearning courses that they have made available for free, as well as User Forums and other training videos have made even difficult concepts easier to understand.

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

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

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.

We have bi-weekly calls with our Success Manager, as well as access to support as needed. Any question that I have had, multiple people have been willing and able to jump on a call to talk me through it, or send an email with the solution

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.

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.

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.

Providing that you have the client's needs well known, creating BI content using Dundas BI is a walk in the park!

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" solution like that. When we looked at Tableau, we liked its visualization capabilities, but it wasn't going to help us do the extractions, ETL, and warehousing of data. It may have come some distance since then.

Incentivized

Per dollar spent, it offers the widest range of features of the tools that we evaluated. It offers lots of options for how to configure your environment, though they are not always intuitive to figure out. Having an ETL layer was a must have for us, as well as the ability to host to secure HIPAA compliance. It is not a replacement for ad hoc reporting, but does a great job of creating parameterized reports and dashboards that look great.

Incentivized

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.

Incentivized

• Coming from an SQL based standard delivery model, Dundas BI has provided a fantastic rate of ROI.
• The preparation and delivery time has reduced from weeks to just a few hours.

Incentivized