What is our primary use case?
My clients use Qlik for in-depth analytic analysis, creating touchboards for a variety of purposes. In our case, we prefer an on-premise solution over the cloud, especially for a banking client, to ensure data security and compliance with industry regulations.
How has it helped my organization?
One major benefit of having Qlik Sense in our organization is the ability to establish a strong KPI base. While various solutions offer similar capabilities, Qlik stands out for its remarkable speed, especially when compared to alternatives like Tableau. This speed advantage enhances overall efficiency in data analysis and decision-making processes.
What is most valuable?
The most valuable features of Qlik Sense are its speed and seamless development of web technologies. It is pure HDMI, eliminating the need for cache servers or translation engines, making it one of the fastest solutions compared to others. The direct connection between ML and data adds to its efficiency. Additionally, one standout feature of Qlik is its QVD data model, allowing the creation of data maps that are directly stored in memory, offering fast and efficient data service to consumers. Qlik's ability to handle large datasets with millions of rows is a significant advantage, although there are some limitations.
What needs improvement?
I would like to see improvements in the Qlik Sense SaaS version, particularly in the front-end capabilities. Currently, the visualization options are limited, allowing only basic actions like adding dimensions and measures with restrictions on the number. Compared to older products like QlikView, there is room for development in enhancing the features available on the front end for widgets and visualizations.
Enhancing the formatting options in the SaaS component and making it more visually appealing would be a nice enhancement. Additionally, expanding the library with more versatile widgets would be beneficial. While you can add components from a marketplace or develop your own, there is a need for Java front-end developers to handle this aspect of Qlik Sense.
For how long have I used the solution?
I have been using Qlik Sense for four years.
What do I think about the stability of the solution?
Overall, Qlik Sense is stable, but there can be challenges related to managing the QVD data models, especially when dealing with numerous versions for different periods. While it requires effort to maintain, the system itself is generally stable.
What do I think about the scalability of the solution?
Scaling Qlik Sense is possible by adding more servers, and it is generally smooth for load balancing and disaster recovery. However, making changes to the model can be time-consuming. Overall, it is scalable with effective load management and recovery mechanisms.
How was the initial setup?
Setting up Qlik Sense is easy, especially for default visuals, though coding may be required for more specialized charts. Converting from QlikView to Qlik Sense is seamless for data models. The deployment process involves using Qlik Desktop for model development and two subscription options: on-cloud, which is ready to use, and on-premise, requiring Qlik Sense servers. Maintenance is simplified with admin tools, making it accessible for a developer.
On average, for a consultant company creating reports and delivering a sales model with about five reports, the deployment of Qlik Sense can typically be handled within three months.
What was our ROI?
We have seen ROI with Qlik Sense.
What's my experience with pricing, setup cost, and licensing?
Qlik Sense is pricier than other BI tools, with various licensing models, including potentially expensive token-based licenses. Organizations should carefully assess their budget and licensing requirements before choosing Qlik Sense.
Which other solutions did I evaluate?
Comparing it with other BI tools, Qlik Sense stands out by requiring a front-end developer for optimal project development. Unlike Power BI, which needs BI developers, or Tableau and SAP BusinessObjects that don't require Java developers, having a front-end developer enhances the project quality in Qlik Sense.
What other advice do I have?
Before implementing Qlik Sense, my advice is to carefully assess its development needs, as custom components may require coding. While the deployment phase is generally straightforward, take advantage of Qlik Sense's flexibility in data modeling, allowing developers to write scripts for more tailored solutions. It is crucial to document projects for better collaboration among developers. Overall, I would rate Qlik Sense as a seven out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner