Qlik Sense Reviews

Within the University of Miami healthcare system (UHealth), we wanted to see a high level view of our contracting performance. We currently are utilizing multiple systems of truth. We utilize the Advisory Board's PIC (Payment Integrity Compass) system to model all of our hospital contracts. For professional services, we use Experian's modeling tool. We wanted to consolidate all these different inputs of expected payment values into one view or report. There was a need to compare expected contractual values with actual over time. 

It helps our team get better at predicting the future if we continue to monitor and follow. Our hope is that actual values would materialize from our expected values.  

In our own wheelhouse, we were able to identify easy things, such as when a contract was loaded incorrectly. We also began to see how our processes and other team's processes were negatively affecting the bottom line. We were able to provide tips to other teams to help improve their processes.  

Qlik Sense data visualization building gives users tons of insight and connections that they may not have thought about. When you start play and building with knowledge that is presented, it just begs for more. 

Trending percentage volume over time in a new way, instead of using multiple pie charts, just have a percent scale and line that shows the percent change over time.

The ability to free form visualizations without coding, I know it is a tall order.  There is so much right about Qlik Sense that it is hard to ask for improvements.  

The product is super stable. We have no issues

With memory and disk space being so cheap, we have not had an issue

Excellent support with constant communications.

I previously used a combination of SQL and Crystal reports. It takes a lot more time and effort to get similar results. Qlik does much of the work for you, like a great assistant.

The initial setup is very quick and simple.

Vendor assistance.

Currently, our ROI is clear and concise decision-making. This timely addition will easily add $15 million to our bottom line in 2017. 

You will spend more time on educating your staff than licensing the product.  Ultimately, the cost is low, and it implements fast. The limiting factor is how quickly your staff can keep up.  

I looked at Power BI and Tableau. Both were missing many things, including the academic healthcare community and expertise around Epic.

It is a great tool for those companies or institutions that really want to empower their users to do great things. 

The overall ability to build quick wins with simple data to drive insights.

We are still new in rolling out dashboards. We still have an estimated 9,500 hours worth of data discovery and application building based on our needs assessment with internal business clients.

Dates. My goodness, working with dates in set analysis can be a nightmare! Much room for improvement.

One year.

Yes, we are still working to get things set up properly with our nodes and load balancing.

No issues.

No issues.

An eight out of 10.

An eight out of 10.

No

Complex, multi-node environment, with security certificate errors. I went to upgrade and had to wipe everything, then start fresh. Issues were non-allowed characters were in our password.

We used a vendor team for installation. Their expertise was a seven out of 10.

Not applicable.

Start small with tokens. You can always buy more.

Yes, Tableau, Alteryx, and Microsoft Power BI.

It is worth the frustration, but do not underestimate the difficulty of working with dates in set analysis.

Qlik Sense is much more user-friendly and easier to read then QlikView.

We currently use QlikView for much of our business needs, for example, we use QlikView for our inventory tracking. However, there are other departments in which the need for such extensive tracking is not needed. These users are looking for reports or KPIs that they can share with their teams that are easily read.

Possibly offering some more basic, simpler templates. We have some users who have some technical proficiency but others who may just want to create a simple graph or pie chart from the data they have been given. It would be nice to be able to break down the templates by user type: beginner, intermediate, or advanced. Therefore, the administrator can allow the end-user some flexibility based on their technical knowledge. This should allow the user to have more control over how they would like to see the data they need and be able to understand it easily.

We have used it off and on for the past few years but have only recently been discussing incorporating some Qlik Sense along with our current QlikView.

Not yet.

No.

No.

An eight out of 10.

A nine out of 10.

We currently use QlikView.

We use the basic free version now. We have not implemented it yet.

Not applicable.

The cost is not bad considering the flexibility and support you receive from Qlik. I believe it is worth the cost.

Tableau.

• Easy to use interface
• Leveraging and reusability of already existing QlikView assets and knowledge
• Powerful data extraction process
• Rich API and web integration capabilities
• Performance

Reducing the number of Excel spreadsheets in house, or at the very least, improving the accuracy of the numbers in those Excel spreadsheets (which come as exports from Qlik charts).

Multi-server deployment: not just cloud, but on premise too, and hybrid. Needs lighter protocols to communicate between the different services and with the clients.

Multi-server computing: the QIX engine is still "limited" to the power of one single computer. While this power increases with better CPUs and bigger and faster memories, data demands even faster handling, only achievable by leveraging on several computers to crunch the numbers.

Data sources connectivity, natively: Drivers tailored to how Qlik processes data and how the sources provide it.

Governance: On the reactive side, see how each node in my development is doing, on the proactive side the ability to spin up new instances for the different needs in different moments (extraction, or data handling in memory or report distribution). Have a unique, central library of apps, but also measures and dimensions which can be used across the different sets of apps. Natively built in tools to analyze who is accessing where, when, providing better insights on apps seldom used and those who are massively accessed, and allowing to provision resources and make these apps more accessible and improve the user experience.

Licensing: Review the named model and move towards a usage model (e.g., cores, memory, computers, API calls, etc.).

More than three years.

No.

Yes, with initial versions.

Mentioned in the area for improvement: Large data sets and sources of data, large applications are limited to a single server (instance or virtual machine).

Good.

Depends highly on the people attending the call, from excellent to poor.

I was not part of this process.

Coming from QlikView, it took some time to get accustomed to new interfaces and functionalities, but all-in-all, quite straightforward. Anyway, Qlik Sense is not QlikView, and the architectural changes require some thought upfront, not just install the server and get it working.

To implement, we used Qlik Consulting Services as well as in-house people, like me.

Cannot measure that.

Triple check with the Qlik Sales Department about your current needs, often smaller than the definitive ones, allowing you to scale the price. Chase them to provide the best solution to your needs, not just a discount, but the one that meets your company requirements (and eventually more).

I was not part of this process.

I have to disclaim that I worked for Qlik in the past, although today I'm a Qlik customer and also a user of other BI technologies in the SAP ecosystem.

• Complex data modeling
• Qlik DataMarket

• Automated a lot of manual reports to save business users' time.
• Provides valuable info with business intelligence analytics.

Reload time is a limit since everyone wants real-time data.

One year for Qlik Sense.

No.

Takes up a lot of memory.

No.

A nine out of 10.

A nine out of 10.

QlikView. Qlik Sense is a newer version, and more user-friendly, with no charge for servers.

No.

Vendor Team using virtual-consulting, which is not very efficient.

I don't know.

Licensing could be cheaper.

Yes, Tableau.

I am very excited about the future generations of Qlik Sense and Qlik Market.

Self-service use of the desktop version with the ability to port applications into the server environment.

Much more information is now available when meeting with vendors to discuss issues and trends.

Ability for the administrator to approve Community Sheets in the QMC and then move them into base sheets.

We have used this solution for approximately 16 months.

There were no deployment issues. It was easy to install with good on-line directions.

There were stability issues. The former synchronized persistence failed and caused database corruption.

There are no scalability issues. RIM nodes are easy to add and performance monitoring is built into QMC.

There is good customer service. There are no issues and they are very responsive.

Technical support is decent. There is a lot of passing around to other other technicians for escalation.

We did not use a previous solution.

The initial setup was not complex. Just make sure to understand the architecture and use the online server planning tools.

We used an in-house team, although the server architecture was planned with the Qlik architecture team.

Understand the break over price point for switching to the Enterprise license.

We evaluated Tableau, Power BI, and Lumira.

Utilize the resources Qlik has online. The white papers, support site, and training are all very good and worth the effort.

Provides self-service capabilities for inexperienced users using the free desktop version.

Gives significant visibility into vendor quality of service.

Enables the approval of community sheets in QMC.

We have been using this solution for 16 months.

There were no issues with deployment. It was fairly easy and well-documented.

The shared synchronization failed between servers.

There were no scalabilty issues. It is easy to add RIM nodes as needed.

Customer service is decent. There is a lot of passing off to other techs during the escalation process.

I would give technical support a rating of C+.

We did not use other solutions, but we did test several solutions prior to going with Qlik Sense.

The setup was straightforward. We used a Qlik architect for the initial design.

We implemented in-house.

We are working on this. A lot of value is coming through warranty data analysis.

You need to determine the break-even point for enterprise licenses early on.

We evaluated Alteryx and Lumira.

Quick reporting.

Logistics work more efficient in real-time data.

More options for the layout.

1 year

Not really.

Not really.

Not really. The solution is scalable.

7/10

8/10

We did not look at any other solutions.

Not complex, straightforward.

8

3 years

The solution is worth it.

We did not.

Keep following the chosen direction.