1. QlikView alongside ‘Traditional BI’ stack vendors January 2012 Mike Saliter
This presentation is aimed at showing how QlikView can be used to compliment existing investments with ‘traditional BI’ solutions such as Cognos, BO, OBIEE, etc. Many large organizations have significant investments in these traditional solutions and it is helpful for htem to see how QlikView compliments (and not necessarily competes) with these solutions.

2. Common BI Challenges Business says…
I can’t access data in a timely manner
Existing BI performs too slow and I only use it for export to .XLS
I need more flexibility and self service
BI projects take too long to deploy
IT says…
Business can’t define requirements
We don’t want to lose control of our data
Has anyone seen these challenges within their organization? We hear them every day from clients. This “brick wall” often exists between IT and the Business and both sides are frustrated when it comes to traditional Business Intelligence. Business Discovery is aimed at breaking down those walls and empowering the business to truly perform self service while IT still has control over the data and system. Business Discovery can be considered the ‘next evolution’ of BI where business users expect fast access to their data just like they can access information on their personal devices such as smartphones or PCs.
We need centralized administration, security and auditing
We must adhere to corp. standards

3. Gartner: “BI bifurcation”
Traditional BI (aka: “Stack Vendors”,
“Mega-vendors”, “Report-centric” etc)
Business
Discovery (aka: “Data Discovery”,
“Visual Analytics”, “Agile BI”, etc)
In Gartner’s June 2011 report, they highlight the ’bifurcation’ of the BI market. In other words, there are 2 separate but related requirements to truly fulfill BI requirements: one for traditional BI covering areas such as managed reporting and a second (newer) focus on Business Discovery (aka: Data Discovery). QlikView compliments your existing BI investment and this approach has been vallidated by leading companies worldwide.
SOURCE: Gartner Emerging Technology Analysis paper on Visualization-Based Data Discovery Tools, June 2011

4. QlikView Comparison to Traditional BI
Traditional BI (Cognos, BO, OBIEE, etc)
Managed reporting (prompting, scheduling, etc)
Pixel-perfect reporting
Pre-defined controlled reports
OLAP analysis (cubes w/ pre-determined heirarchies)
Prepackaged metadata
Fixed drill paths
Statistics and predictive analytics (via SPSS, SAS, etc)
SQL or MDX queries
Business / data discovery
Dynamic dashboards
Interactive / visual analytics
Search live data
User-centric interactivity
An associative experience
Access relevant business data from any device
Speed-of-thought analysis
In memory data store, fast performance
Here are some of the common requirements which fall into each of these 2 categories. As you can see, the requirements are different and warrant a separate solution. The ’one size fits all’ model has proven ineffective as most organizations struggle to get value out of traditional BI when it comes to being nimble and providing business driven data/business discovery capabilities to users.

5. While QlikView empowers the business user, it is not done in a way that violates any IT standards or control. IT still maintains control over the data and enterprise standards, but they are no longer bogged down with ‘backlogs’ of reporting requests. Instead, they enable access to data and the business users are empowered to explore data and even develop their own data discovery dashboards. IT can have as much control (or as little control) as they would like.

6. The Evolving BI Landscape
REPORT-CENTRIC ARCHITECTURE
(IT-driven, tightly controlled)
END USER
Predefined reports and queries
Pre-configured dashboards
Fixed drill paths
STACK VENDOR BI
Managed reporting
Locked-down data definitions
Prepackaged data
IT DEPARTMENT
IT ROLE
Create data models
Establish semantic layer
Build reports
Tightly control data
The 2 approaches to BI (Traditional BI and Business Discovery) result in different architectural approaches. On the left, we see the ‘traditional’ approach which is very IT driven and locked down.
OPERATIONAL DATA SOURCES

7. The Evolving BI Landscape
REPORT-CENTRIC ARCHITECTURE
(IT-driven, tightly controlled)
BUSINESS DISCOVERY ARCHITECTURE
(Business user-driven, self-service)
END USER
Predefined reports and queries
Pre-configured dashboards
Fixed drill paths
STACK VENDOR BI
Managed reporting
Locked-down data definitions
Prepackaged data
IT DEPARTMENT
BUSINESS USER
User-centric interactivity
An associative experience
Access relevant business data - from anywhere
Speed-of-thought analysis
Rapid time to value
QLIKVIEW
Dynamic dashboards
Interactive analytics
Search live data
Reports
Any device
IT ROLE
Create data models
Establish semantic layer
Build reports
Tightly control data
IT ROLE
Assemble data
Deliver relevant data
Enable self- service BI
Ensure security and scalability
On the right, we see the Business Discovery (Data Discovery) approach which is a business user drivem, self service model
OPERATIONAL DATA SOURCES

8. QlikView Positioning – within a BI Stack
Start with an empty matrix – customize the dimensions
As you look to decide which technology is best for the requirements, we suggest a ‘best in class portfolio approach’. You can begin with a capabilities matrix such as the one above. Here, you map out all the common datasources and BI capabilities.

9. QlikView Positioning – within a BI Stack
Fill in current state of BI tool stack – highlight or score boxes to call attention to areas of need
Next, you fill in which tools are best for the job. For example, Cognos may be best ‘Production/Corporate Reporting’ solution whereas SAS may be the best Statistical/Predictive Analytics solution. Just as you would use a hammer for nailing and a screwdriver for screwing, we suggest the right tool for the right task.

10. QlikView Positioning – within a BI Stack
Fill in “To Be” state with QlikView and start to define BI Patterns that fill those boxes
Here we see QlikView being positioned for the areas where it may fit best in your organization. The Data Discovery (Business Discovery) column is a clear fit but there are other areas such as dashboarding, analysis, etc which will often fit based on your needs.

11. QlikView Positioning – within a BI Stack
Completed Sample – mock data only
Over time, we often see QlikView growing into other areas as companies find how quickly QlikView can be deployed and how much lower it is to maintain and develop compared to traditional solutions. The idea is that QlikView will often spread wider but there will still be a place for traditional BI particularly related to pixel perfect production/corporate reporting. In the end, everyone wins with a best of breed approach!