QVLogga_nu_då_webb

Climbers QlikView history – from the beginning until now

When we started with QlikView 2005, the tool was an “underdog”. It was mainly the medium-large companies that were interested as they had not previously had access to “Business Intelligence”. The alternative tools available on the market were both expensive and complicated.

We went around together with Qlik and did so-called ​​SIB meetings (SIB=Seeing is Believing), often several times per week. Most of these led to business. The customer bought a server with 10-20 users and we completed the financial or sales application we had started in the SIB meeting.

However, this was only the beginning of taking advantage of QlikView’s capabilities. After a period of using it, most gained the appetite to start looking at new key figures and new areas.

There were also a lot of major companies that had caught wind of QlikView. Through the years, their application portfolios had grown and in 2008 we started working with consolidation and the perception of QlikView was changed from “tool” to “platform”. In addition to basic configurations, we also now began to work with the full suite – server clusters, testing environments and QlikView Publisher. It places higher demands on the entire chain, from development methodology to operational issues. This is something we are working on more and more, even for very large companies such as Nordea, Telia and HSBC.

It has been debated a great deal as to whether there should be a “Data Ware House” (DWH) for QlikView. In the major companies, it was never an issue as there were usually already several “Data Ware Houses.” In 2009, we built our first major “Data Ware House” with QlikView as the prototype tool, and since then it has become an increasingly integral part of many QlikView projects. Therefore, “Data Ware House” and QlikView definitely go hand in hand – under the right circumstances.

In 2008 and 2009, even the big companies started to see QlikView as an Enterprise Business Intelligence solution. In the summer of 2009 we, together with Qlik, beat out both SAS and Microsoft at Lantmännen Unibake that was to change their entire ERP installation worldwide to Dynamics AX, and they chose QlikView and us as BI (Business Intelligence) supplier “on top”. Now we had come a long way from the initial SIB meetings and projects in just a few weeks. Now it involved a roll-out in several countries of a business-critical BI system. The solution covers all the company’s areas of operation.

Timely enough, we had also started to build our own support department that currently serves more than 300 customers. Many of the initial niche solutions had grown and become business critical solutions!

Recent years have been characterised by assignments where we have been able to take more responsibility for helping the customer develop their business, e.g. to maximise their “Business Discovery” with QlikView. Through the years, we have learned to understand how QlikView can provide a good base for our customers to analyse and further develop their business. Although we presently provide a number of “surprises” for our customers, the entire process involving BI and QlikView is as predictable and planning-friendly as ever.

From usually having built solutions that are used internally in companies, in 2011 we built our first open Internet solution based on “QlikView Information Access Server” and “QlikView Workbench”. This was called “Jämföraren” (translated: The Comparer) and built for the Municipality of Nacka in Sweden (Nacka Jämföraren). In 2012, we built a similar solution for the Municipality of Väsby, Upplands Väsby Jämföraren.

In addition to these public solutions, we have also built some external solutions used by our customers’ customers. These are based on the “QlikView Extranet Server” and are used by many users, often with “Session Calls” as the license form.

In addition to our analytical solutions, our customers are requesting the ability to forecast their business based on outcomes or other data in QlikView. This has been solved by a number of solutions over the years, from input fields in QlikView to stand-alone tools like Effectplan. Today, there are solutions for all differing levels of complexity.

To complete the entire chain process, we have now also started to work on what we are geared to replace, that being the hated, traditional report. Using the NPrinting tool, we create reports from QlikView data for distribution, both internally and externally.