OpenText Magellan BI & Reporting vs. Qrvey

iHub is a decent enough environment that it serves our needs. We can have unlimited users and it can tie into AD although we do not use that feature currently. It is a decent place to store all of the reports in one location, even though for us it is not visually appealing to the end users. iHub is not a place where you want to create robust/interactive dashboards for end users to drill through and follow a "story".

Incentivized

Qrvey is an excellent solution for AWS-based customers looking to add embedded analytics functionality. It is cloud-native and good at scaling. There are BI solutions with greater depth in particular areas (chart types, custom metrics), but Qrvey has an unmatched level of customizability for embedded use cases. Many APIs are also exposed and documented, making them easy to integrate into a data ecosystem.

Incentivized

• It is fairly easy to set the sharing rules for a report/dashboard.
• They have a decent amount of time frame options for setting a schedule to generate a report.
• The support is mostly helpful and timely if you have an issue.

Incentivized

• The platform deploys to our AWS instance which gave us the ability to manage ourselves
• The feature of easily embedding visualizations into other applications
• The powerful features like workflow automation

• Setting up a "dashboard" is extremely lacking in functionality. The different chart widgets you place on the page do not interact with each other. When you select an item from one do not expect it to highlight or filter another.
• The speed and stability are not great, but maybe that is just our environment not being up to snuff...even though we are above the "recommended" settings.
• The main GUI for a user is TERRIBLE. You log into a File Tree format where you have to navigate folders to reach the correct dashboard. There are ways around this, but it would either require an expensive payment to the Professional Services team to revamp to UI or another option they gave us was to create the "Default Dashboard" and provide that link to users and in that Dashboard, you use a new tab to include the navigation back to the main screen so that at least on the initial load the user is taken to a friendly looking dashboard instead of a file tree.

Incentivized

• Merges between heterogenous datasets can occasionally be problematic
• The dashboards/pages are already very powerful, but more interactive elements would always be welcome.
• The administration of a Qrvey instance and underlying datastore can sometimes be complex, but the Admin app helps make this a smooth process.

Incentivized

Our instance of iHub does not stack up against the other larger BI tools out today. It is a good place to store reports in a central location that allows users to run very specific reports on demand, but it is not a place I would want to store all of my "dashboards". As far as holding individual reports that are specific to an individual need, it is a great tool. If you want to create a report that will be used as a Template for a Form or a Label, iHub is a good choice to store and schedule the report or call it via API to generate it and return it to your calling app.

Incentivized

• In one implementation, Qrvey helped our customer quickly achieve feature parity with competitors, reducing churn.

Incentivized