Does QlikView is replacing only horrible “Cubes” from traditional BI approach or it is against Data Warehouse too

Dear Readers,

After long time I am back to my QlikView blog as I was busy with sales calls.Last quarter was excellent and I was able to win some reputed accounts for my company. Notable deal was a decent sized order from KPMG.

This post is again comparing QlikView with traditional "Cube" based business Intelligence software. The point of discussion is "Does QlikView is replacing only horrible "Cubes" from traditional BI approach or it is against Data Warehouse too"

 

                                

Traditional OLAP Based BI Architecture                   QlikView Next Generation BI

If we see two pictures above, left one is explaining OLAP based BI architecture and picture in right is explaining QlikView Architecture.
I will first explain OLAP based architecture.

We use a third party ETL tool ( It may be from same vendor but as different product Require expertise to work on) to create "Data Warehouse" or "Data Marts" from original data source. It require a huge investment in database licenses and man power to built "Data Warehouse". ( see layer 2 in picture above in left side).

The next step is to define,build and to deploy different cubes (e.g Sales cube ,Finance Cube,Production Cube etc.) these cube are rigid in architecture and take time to deploy and practically there is no relation defined in between these "Cubes". These cubes are holding some limited dimensions. ( A cube can handle not more than 6-8 dimensions Efficiently). ( see layer 3 in picture above in left side).

Once the cubes are deployed it is require to have a third party GUI editing software (It may be from same vendor but as different product. Require different skill sets to work on it) to create GUI and this GUI is delivered to end users. ( see layer 3 in picture above in left side).

To deploy entire architecture it is require to have excellent hardware that have there own cost.

But real story begins when end users start using it. First of all it is really difficult to invite leadership for long and boring training sessions and some how if they get trained on this ( It is really rare) still they show resistance in using it due to big hierarchical structure while they see reports.

Consider some how IT team has managed that at least second row of end users to use it then  what will  happen if requirement changes? A new question in business has came??? What if it is require to have another dimension or set of dimension??? The only solution is new "Cubes". And if required dimension is also not in Data Warehouse then it require rebuilding entire setup it will take its own tie and it has own cost ( May be the same time to deploy as new one and more investment than entire new setup).

Looking at cost of maintenance and time taken it is obvious that finally people will start using Excel sheet. After a big investment of Money and time they came back to Excel sheet. Where is so called value delivered?? Dose it matter now, how clean our data is ?,that we have managed to get in Data Ware house? I am leaving this question on you to give answer. ( see layer 5 & 3 in picture above in left side).



Now I will talk about QlikView while comparing with OLAP based Architecture.

QlikView take data out from data source by using its own inbuilt integration layer it dose not require any third party ETL tool. It create a associative data model which  "in any way"  is not a relational data model so it is not a Data warehouse and the size of this is reduced up to 90 % as compared to original source data. Since it is not a relational data model the question is how to perform search in this data model? QlikView use a patented technology called "AQL" or Associative Query Logic. Which work like how our mind work and perform a non linear search on associative data model ( Unlike that of linear search in Relational data model). AQL is supported by in memory technology to deliver faster result than relational data model. ( See layer 2 in picture above in right side)

Now it use its won inbuilt GUI layer to create Excellent GUI that require no learning curve and is similar to Excel sheet on which your end users have long practice to work. Thus if a person know how to use mouse can use QlikView without any training. ( See layer 3 in picture above in right side)



The point to note here is that layer 2 and layer 3 ( Associative data Model and GUI) in QlikView is single layer. Actually QlikView create a application file with extension ".qvw" which is a single layer i.e data and GUI both is there in same ".qvw" file.

The difference between Data Warehouse and this Associative Data Model is that former is based on relational model and require different software licenses and have high cost and later is having same data with different way of handling data, and there is no horrible "Cube" is required to query this data.

This blend of Associative Data Model with in - memory technology finally combined with excellent in built GUI gives more faster and easier way to use deliverables without any learning curve. The strength of QlikView is that it do not use "Cubes" to access data not that it is not require to have Data Warehouse.

If there is any new dimension require and if it is in Associative data model it require few "clicks" to add in GUI and if it is in data source it require few minutes only to get added.



Finally I would suggest to go for Seeing is Believing ( SiB). A SiB would take few hours where you can evaluate QlikView on your data for your own end users. During SiB you will get a chance to feel Speed of Deployment,Flexibility,Ease of Use, low risk and High ROI of QlikView- The world's fastest growing BI software.

For SiB on your data please feel free to call me from any where in the world at +91-9312667720 or write me at sudhir@iconresources.com ( Please use your official email id's to get faster response I am lazy to reply to non official email id's)



Also Read

1 -The Reasons Why 69 % Cube Based BI Project Fails And How QlikView Have Success Rate About 98 %


2-
Why QlikView




I invite you comments on my post.

Regards

Sudhir

The Death Of Business Intelligence

Dear Readers,
Today morning I saw an interesting article by Dan Woods at forbes.com with an interesting title “The Death Of Business Intelligence” I found it really impressive.
I am putting first two paragraphs and a link to complete article bellow.

The Death Of Business Intelligence
During the presidential election, CNN anchor John King danced around the newsroom in front of gigantic multi-touch screens, tapping states and moving information around with his hands. He showed a way of analyzing information that is applicable to almost every business.
King did not have to plan his presentations. He could respond to unanticipated questions from reporters and interviewers with a spontaneous narrative that used the information presented in the visual display to help him tell a story. He did not yell backstage, "I need to answer this list of questions, so please prepare reports for me." When a new train of thought came to him, he could jump right on and use the display to show what he was thinking or discover new information that led in new directions. King also didn't stand by and have someone else run the display--he did it himself--and he had access to the latest data read more...

QlikView Vs OLAP – Comparison based on resource required and “Time, Cost & Value”

One of my blog reader “Ms Kaladevi” have asked me the question bellow I decided to answer it as another post on my blog

"I am presently working on a business case for BI project. How do you compare Ms BI tool with QlikView?I case of an Enterprise wide BI project which has to build information from multiple applications...how does this approach w/o data mart work? How will be the performance? "

If I would compare QlikView with traditional BI architecture with QlikView then I can compare on two points.
1- The resources required
2- Time, Cost & Value
If I am comparing on 1st point what are the tolls and resources I require to built entire BI suit.
1- The first thing you require is an ETL tool then you require expertise on ETL who are really a costly resource
2- Then you would require software licenses to create data warehouse &data marts also you need multiple man power to create this data warehouse & data marts which have their own cost
3- Third layer would be your OLAP,Querry and reporting tools & obviously it has its own cost and require expertise to implement this
4- Finally you require to buy an GUI editor and work force to implement GUI
I can draw this like Bellow
Datasource(s) ---(to extract ,transform and load)-----> ETL tool-------> Data ware house & Data Marts-------> OLAP,query & reporting tool ( i.e. your BI software)-------> A GUI editor.
All tools are different and mostly from different vendors require multiple resources to implement, maintain and these projects are highly IT driven.
Now if you look in QlikView it is a single tool having all BI capabilities inbuilt in it like Integration, data compression, Analysis engine, chart and reporting engine and finally user interface.
All in single tool require no costly resources single tool single vendor and it can be implemented by a person who know SQl scripting. QlikView implementation does not require a pool of man power.
If I compare on second point "Time, Cost & Value".
1- Traditional BI projects take at least 4,5 months to show first usable analytical report in QlikView project you can start delivering applications from day one so a average implementation time is 10 day for QV project.
2- Since they are dependent on Cubes you require to built multiple cubes and it is very difficult to provide transition between two cubes e.g. if someone is looking at finance cube for AR report and he need to see details of sales rep associated with a particular customer he need to go back to sales cube.
3- In case of requirement change i.e. if end user require another dimension in cube that is not available in cube or he want to delete a particular dimension it is require to make change in cube it take time to change and for that customer have to be dependent on his BI vendor it has its own cost.
QlikView is based on Associative data model and it is very easy to make change in QV application at any point of time. On demand in time since it is easy!!! This is what I feel is USP of QlikView.

Finally I can suggest that two understand QlikView best way is “Seeing is Believing” or “SiB”. Call your nearby QV vendor for a SiB on you data and see how it is easy to create an application in QlikView what is the performance and how much time you require to implement.
For ‘Sib” you can contact me at sudhir@iconresources.com or call me +91-9312667720

The Reasons Why 69 % Cube Based BI Project Fails And How QlikView Have Success Rate About 98 %

Dear Readers,
After long time I am interacting with you on my blog as I was quite busy with handling new accounts. But I was answering all queries which are coming to me by emails or on my phone. This time I am comparing the reasons why most of traditional cube based or data warehouse based BI projects fails and how QlikView can give you excellent success rate as compared to traditional BI architecture.

1. Lack of user involvement
Almost every time IT department start a BI project and fails to involve user as they found it very hard to involve in. Normally a user has the approach "Let me see something then only I can tell you what my requirements are". It is very difficult to control such cases if IT is doing so, it is not possible with every user or user group that they can able to speculate their need by seeing prototype only. I have seen lot of finance officers asking by seeing sales report "Oh so this tool is for sales analysis?", and sales guys asking after looking supplier analysis "Is it for logistics and my purchase department?" and if you are showing prototype for everyone on his own data, you may go over budget and it is not easy to handle change requests when you need to make changes in BI Cubes.

How QlikView can help
It is not possible to avoid change requests otherwise you are not giving right solution to end user and ultimately your users would be using MS excel down the line 6 months of implementation.
Better you accept maximum changes because you have QlikView in hand and USPs ease of use with no learning curve for IT as well as for end user result of this is rapid deployment. In QlikView one can handle change requests very easily and you can have a prototype ready for every user in average 2 hrs for each user. Once they can see the prototype for their own data set it is easy to involve them in BI project that is first step towards success. Answer is Create involvement by using such tool which can give you power to address any change request in 1/6 time than any other BI software take.

2. Building Enterprise data ware house Warehouse and data marts
Most of the companies start their BI projects by building data ware house. It involves high risk with very less guarantee of success. Companies keep adding more team-members that do not help much and data ware house projects doesn't achieve scalability. Data ware house have give very less ROI and project cost lot of money and projects end in disasters. Some companies start with data marts and try to create enterprise data ware house step by step. it is again a time consuming process and require several iterations.

How QlikView can help
To implement QlikView you don't require creating any data ware house. What it does is it pulls data from transaction system (i.e. ERP, CRM etc) and stores it in to a file that has ".qvd" extension. This file is actually an associative data model and search being made (Subsequently Query is being processed) by using patented Technology "AQL" (Associative Query Logic.)
As GUI is also written on the same file so there is no back end in QlikView when it is processing the data during run time. It takes around 1/6 time to create associative data model than creating a data ware house. Also you do not require to use any third part ETL tool QlikView have its own integration layer that call edit script to load data in ".qvw" file. It also takes care of data cleansing part so you can identify noisy data and its source very quickly and subsequently can take necessary steps.

3- Budgetary Constraints
To start a tradition BI project it requires a big budget. And people normally don't care of expenses of hardware, training and maintenance cost. Having cubes is another issue as whenever requirements change after implementation/or during implementation, changing cubes or building entirely new cube have its own cost and finally project goes out of budget.

How QlikView can help
If we look at overall budget of QlikView or if we talk about total cost of ownership (TCO) including cost of software, hardware, training, implementation services, and maintenance the total cost would be around 1/6 of traditional BI architecture for initial investment and overall it would coat around ½ than traditional BI projects.
As QlikView implementation doesn't required big hardware infrastructure, a implementation time is also around 1/10 of traditional BI projects (Average implementation time of a QlikView project is 10 days) also it do not require highly skilled IT professionals and can be deployed/maintained by in house team budgetary constraints are not in the way of having Business Answer.

4- Corporate Politics
Once the organization start a BI project the first step is fixing the requirements and since the primary user group of a BI project is top guys in any company and they all have different work are and have different thought process, they started feeling that their requirement are not getting covered in this projects ( It is obvious as traditional BI projects are based on cubes and they are very rigid to adopt individual's thought process) so they start playing power game or stop using what they have given by IT department.

How QlikView can help
The best part I have seen in QlikView is it is personalized for individual's need it is easy to deliver a particular user what he is expecting from the BI project. Even in same department an individual head of a particular KPI have his own requirements and that is to be catered individually for him, it is his business requirement, and QlikView is like rubber it can be molded for an individual's need.

5- Wrong Choice of KPI's ( OR KPI's chosen are hypothetical and not solving Business problems)
A finance cube is useless when we are looking at AR report and when we have to see the sales rep detail associated with a particular default account. It happens extensively that while finalizing dimensions for cube IT people are not sure what they are delivering is really the business need and when they deliver it to end user after 5 months (Usually a traditional BI project takes 5 months to show first analytical report ready) they found what they have delivered was not their need or the need has changed during last months. (End users keep asking for something new it is not possible to control demand)

How QlikView can help
The USP of QlikView is "Its easy" it is easy for end users to use and it is easy to deploy by IT team. Since "End users keep asking for something new it is not possible to control demand" but we can have a tool that can quickly deliver what they want now. It is the best tool for ad-hock needs it can cater those requirements where end user want answer on phone , like what is my sales as compared to last year what is my production as compare to Q2 in this year. What this particular product is doing in that reason where I had 80 % margin in last three years.
KPIs cannot be fixed they keep changing according to business needs only we can do is, we can have a tool that can give answer quickly than any other tool. "QlikView gives you answer in 1/10 time as compared to traditional BI software".

6- Complex Cubes with limited dimensions
Normally a cube can handle maximum 8 dimensions efficiently putting more dimensions in cube make it slow, but problem here is it hard to decide what are the exact dimensions required for business answer by the time we know it has been too late. Also every one do not require dashboard, or analysis or reporting.

How QlikView can help
QlikView do not work on traditional BI architecture it use tow technology "AQL" and in-memory technology. That make it different that traditional cube based BI software. QlikView can give you information with "n" dimensions.
Also it can be customized for individual's need. One can have Dash board or analysis or reposts or combination of these. In case of change in requirement internal IT team can handle in 1/10 time as compared to traditional BI software. It gives you less than 5% vendor dependency.

Next Step
I can write "n" number of pages on QlikView but it is suggested that don't believe without seeing. I recommend "Seeing is believing" or "SiB" ask your QlikView vendor to create some analytics, dashboards and reports on your data at your premises and play with it ask you end users to use those dashboard for some time before going with it.

For "Seeing is believing" or "SiB" please feel free to write me at my email id sudhir@iconresources.com you can call me at
+91-9312667720

Brainiac: QlikView feature in Time Magazine

 
 

I recently saw coverage of QlikView in Time magazine

 

In the feature article titled the "Braniac" QlikView is strongly positioned and credited for "Making search much more like your brain--and applying it to business analysis". This compelling article is centered around a lively interview with QlikView CEO, Lars Bjork ,  

 

Read the article. Click on the link below.

http://www.time.com/time/magazine/article/0,9171,1912425-1,00.html

 

Introduction to QlikView Developer for Personal Use

• "Free Personal Developer"can create unlimited number of QlikView Document (.qvw files) and can use those documents on his local machine where it as originally created.
  
• Documents created by a "Free Personal Developer"can't be shared with other free developers.
  
• Documents created by "Free Personal Developer"can be used by licensed developer.
  
• Documents created by licensed developer cannot be used by "Free Personal Developer".
  
• Documents created by "Free Personal Developer"can be loaded onto a fully licensed QlikView server and can be used by licensed user.
  
• When using a QlikView developed by a free developer, licensed developers will be restricted in their use of QlikView. If they break a restriction, they "take ownership" of the document and it cannot be opened by the original free developer.
  
• Once licensed developer will use document created by a "Free Personal Developer" they need to "take ownership "of of the document and it cannot be opened by original free developer.
  

  
  

Restrictions on Free Personal Developer

• Only open your OWN QlikView documents
  
• Import layout
  
• "Include" in script
  
• Outside automation
  
• Pasting more than one object at a time
  
• Ignore command-line parameters
  

QlikView vs. SAS

Dear Readers,

In past few weeks I saw some good marketing/Sales activities from SAS, even in some cases they were in competition with me. My prospects were asking for comparison between QlikView and SAS then I decided to share that comparison with you.

Apart from the detailed comparison bellow in my view SAS have some excellent capabilities when it come to data mining, OR and Quality Improvement, and Data Quality (By using data flux). QlikView also cover these parts but not in the way how SAS do. Instead being a good tool SAS requires a good budget also for cost of ownership as well as for cot of maintenance. Also it is not very much helpful when it come to ad-hock reporting and it is not very much helpful to End-user( Top Bosses) and become an IT tool only.

 

I love to see you view on my article.

#	Product	QlikView	SAS
A	Product
1	Product	QlikView: Worlds Fastest Growing BI tool. With 14. customers being added every working day.	SAS EBI
2	Vendor	Qliktech	SAS Institute.
		Qlikview is a IN-memory based BI tool which can be deployed in a weeks time. It comes at HALF the TCO and delivers TWICE the value compared to any OLAP based BI Solution In QUARTER of the TIME
C	Applications
1	Business intelligence	Qlikview is a single integrted tool for ETL, DW, Multi Dmentional Analysis, Dashboarding, Reporting, as per the Butler group user takes couple of hours training instead of weeks taken by traditional OLAP based tools	Yes
2	Multi dimensional view
3	Strategic planning		Yes
4	Budgeting		Yes
5	Forecasting		Yes
6	Consolidation		Yes
7	Scorecarding		Yes
D	Hardware and Licenses
1	Warehousing is (Mandate/ Optional)	NOT REQUIRED, One of the the major advantage of usinq Qlikview is, it does not require database which saves money and very wel skilled human resource. With no datawarehouse required Qlikview can be impleted in a couple of weeks saving a lot of TIME, MONEY AND RESOURCES.	Optional
2	Server Licenses(Named/CPU)	Named	SAS predominantly supports CPU based licensing, however in specific scenarios named licensing is also supported.
3	User Licenses (Name/Concorent/Unlimited)	Named	Unlimited
4	Web Users	User lic	Unlimited
5	If preparatory Database specify (Technical and Methodology)	NO: Qlikview uses its integrated Robust ETL to Extarct data from multiple data sources and forms a data repository using its patented Technology (AQL: Associative Query Logic) This technology overcomes the efforts and time required to build datawarehouse, normalization, schema writing, creation of cubes. And Empowers the customer to be independent of the vendor to creat and use analyitcs	SAS Intelligence Storage (SPDS) which is based on OLAP technology i.e. the database is tuned for querying and reporting puposes. However SAS also natively integrates with all major database systems.
E	Technology
1	Supported database	Any OLEDB, ODBC complaing which covers althe datbase in the world today + FLAT FILE, WEBFILE. TEXT FILE DELIMITED FILE. ALSO WORKS WITH SYBASE
	Microsoft SQL Server	Y	Y
	Oracle	Y	Y
	Pervasive SQL	Y	Y
	IBM DB2	Y	Y
	Informix	Y	Y
	Access	Y	Y
	FoxPro	Y	Y
	Progress	Y	Y
	MySQL	Y	Y
2	Supported networks
	Microsoft	YES	Y
	Linux	Y TO CONNECT TO THE DATABASE	Y
	Unix	Y TO CONNECT TO THE DATABASE	Y
	AIX	Y TO CONNECT TO THE DATABASE	Y
	Novell Netware	Y TO CONNECT TO THE DATABASE	Y
	IBM AS/400 (OS/400)	Y TO CONNECT TO THE DATABASE	Y
3	Development tools used to build application	NO THIRD PARTY DEVELOPMENT TOOL REQUIRED. THE CUSTOMER BECOMES VENDOR INDEPENDENT FOR ANY NEW APPLICATION/ CHANGES REQUIRED	COM, Java, SOA
4	Report writer used - which one(s)?	NO THIRD PARTY TOOL REQUIRED	SAS Enterprise Guide
5	Data Extract Transform Load (ETL) tools - which one(s)?	NOT REQUIRED: QLIK VIEW HAS ITS OWN ROBUST ETL INTEGRATED AS A QLIKVIEW SUITE. THE ETL IS WIZARD DRIVEN CAN BE LEARNT IN A FEW DAYS AND OPERATED BY CUSTOMER HENCE EMPOWER THEMSLEF TO CREAT OWN APPLICATION AS AND WHEN DEMAND ARISES	SAS Data Integration Studio
6	Cubes supported - which one(s)?	IN ADDITION TO ITS OWN DATA REPOSITORY QLIKVIEW SUPPORTS ALL MAJOR OLAP CUBES	All OLAPs and cubes created using SAS OLAP
7	Existing integration to accounting and ERP systems - which systems?	ALL ODBC COMPLAINT DATABASE(all the current database in the market) IRRISPECTIVE OF THEIR FRONT END, SAP USING A SAP CERTIFIED CONNECTOR	SAP, PeopleSoft, JDE, SSA Global/BAAN, Portal integration kits
8	Existing integration to customer relationship management systems - which systems?	BY MEANS OF THE GLOBAL STANDARD ODBC, OLEDB CONNECTIONS (all major crm system)	Siebel and other major CRM tools
9	Existing integration to payroll systems - which systems?	BY MEANS OF THE WORLD STANDARD ODBC, OLEDB CONNECTIONS( all major payroll system)	All major Payroll Systems
10	Existing integration to HRMS systems - which systems?	BY MEANS OF THE WORLD STANDARD ODBC, OLEDB CONNECTIONS (all major hr system)	All major HR systems
F	Features
1	Analytic functionality	YES	Yes, please see below (feature # 83) for further details
2	Bubble up exceptions	This feature is better handeled where the exceptions are managed at the lower level and not poped to the upper layer and confuse the user. However all precautions are taken to handle the exceptions eficiently.	Yes
3	Drill down	YES	Yes
4	Drill through to source data	DRILL DOWN TO THE TRANSACTIOANL LEVEL. AS AGAINST TO THE AGREGATED DATA IN CASE OF OLAP BASED APPLICATIONS	Yes
5	Ranking	YES	Yes
6	Sorting	YES	Yes
7	Restrict results by date range	YES	Yes
8	Includes dashboard	YES	Yes
9	Time trending (for example, over 12 months)	YES AS MANY YEARS AS THE DATABASE HOLDS	Yes, along with basic time series forecasting
10	Pareto filtering (automatically groups the categories that amount to less than 20% of a row or column total into "other")	YES	Yes
11	Calculations	YES	Yes
12	Counts	YES	Yes
13	Percentage of total	YES	Yes
14	Allocations	YES	Yes
15	Total and Sub-total	YES	Yes
16	Create OLAP cubes	NOT REQUIRED	Yes using SAS Olap Studio which created MDX compliant cubes.
17	Data extraction and transformation tools	INTEGRATED	Yes
18	Incremental extraction	YES	Yes
19	Impact analysis - objects impacted by change	YES	Yes. Reverse impact analysis is also possible, which means any changes in any of the DWH-BI process can be traced and impact analysis can be performed.
20	Can schedule process to run overnight	YES	Yes
21	Formatting	YES	Yes
22	By dimension	YES: N DIMENTION	Yes
23	By level	YES	Yes
24	By cell	YES	Yes
25	Zero-row suppression	ZERO/NULL FIELD SUPPRESSION	Yes
26	Conditional formatting by cell, e.g., highlight cells below threshold	YES	Yes
27	Returns text (e.g., if value > 90, returns "excellent")	YES	Yes
28	French version	UNICODE: CAN BE IMPLEMENTED IN ANY LANGUAGE	Yes
29	Screens	YES	Yes
30	Reports	YES	Yes
31	Documentation	YES	Yes
32	Metadata	YES	Single Integrated Metadata across complete DWH-BI-AnI process. One interface to manage ETL, Business Intelligence, Dashboards, Cubes, Information Maps (semantic layer), Reporting, Analytical solutions.
33	OLAP functionality	NOT REQUIRED	Yes
34	Skip missing levels - support ragged dimensions	YES	yes
35	Write back	NO	Yes
36	With audit trail	YES	Yes
37	Includes charting tools	YES	yes
38	Access multiple cubes at a time	YES	Yes
39	Excel client	YES	yes
40	Internet Explorer client	YES	yes
41	Netscape client	FireFox	yes
42	Geographical representation	YES	Yes
43	Drag and drop	YES	Yes
44	Attach notes to cube	CUBES NOT REQUIRED SAVES TIME AND MONEY	Yes
45	Attach notes to cells	CELLS NOT REQUIRED SAVES TIME AND MONEY	Yes
46	Password security	YES: UP TO THE FIELD LEVEL( BETTER THAN THE LISTING BELOW)	Yes
47	By company	YES	Yes
48	By department or division	YES	Yes
49	By menu	YES	Yes
50	By function (view, add, change, delete)	YES	Yes
51	By dimension	YES	Yes
52	By level	YES	Yes
53	By cell	YES	Yes
54	Respect active directory authentication	YES: CAN BE INTEGRATED WITH ACTIVE DIRETORY AUTHENTICATION FOR A SINGLE LOG ON PER USER	Yes
55	Respect database security	YES	Yes, row level as well as colunmn level security
56	Portal generation that includes HTML reports	YES	Yes
57	Report writer	NOT REQUIRED: INTEGRATED FEATURE	Yes
58	Web-based	YES	Yes
59	Generate cube	NOT REQUIRED: OVERCOMES CUBE DRAWBACKS	Yes
60	Drag and drop	YES	Yes
61	WYSIWYG report design	YES	Yes
62	Technology	YES (AQL)
63	API-enabled (SDK provided)	YES	Yes
64	Web-based (only need browser at client)	YES	Yes
65	For entire application	YES	Yes
66	Support for .NET web services	YES	Yes
67	Support for Java web services	YES	Yes
68	Transfer data to:
69	Report writer	QLIKVIEW IS NOT A REPPORT WRITER HOW EVER IT SUPPORTS GENERTING REPORTS AND THIS FEATURE IS INTEGRATED PART OF QLIKVIEW.	Yes
70	Excel	YES	Yes
71	PivotTable	YES	Yes
72	HTML	YES	Yes
73	PDF	YES	Yes
74	PowerPoint	COPY PASTE (CTRL+C, CTRL+V)	Yes
75	XML	YES	Yes
76	Views	YES
77	Crosstabs	YES	Yes
78	Charts	YES	Yes
79	Both crosstabs and chart at the same time	YES	Yes
80	Work flow	Open to function with third party tools
81	Alerts can be automatically triggered	YES IN THE FORM OF POPUPS AND CAN BE USED TO AUTOMATE SENDING OF MAILS, ACTIVATE/RUN OTHER APPLICATIONS	Yes
82	Dynamically summarizing data without having to rebuild data?	ANALYSIS AT TRANSACTION LEVEL, WITH DRILL DOWN CAPABILITY FROM THE CONSOLIDATED ANALYSIS	Yes
83	Ability to pre-calculate results (aggregate) when they are available, or dynamically generating result from atomic information when necessary	YES	Yes
84	Ability to control and design cube aggregations	DOES NOT REQUIRE CUBES WHICH CAN HANDLE 3-10 DIMENTIONS ONLY. QLIKVIEW IS BASED ON AQL THAT CAN HANDLE AS MANY DIMENTIONS AS THE FILEDS AVAILABLE	Yes
85	Ability to monitor cube performance and tune the cube aggregations accordingly	DOES NOT REQUIRE CUBES WHICH CAN HANDLE 3-10 DIMENTIONS ONLY. QLIKVIEW IS BASED ON AQL THAT CAN HANDLE AS MANY DIMENTIONS AS THE FILEDS AVAILABLE	Yes
86	Can the cube be built using either of ROLAP, MOLAP, HOLAP techniques	DOES NOT REQUIRE CUBES WHICH CAN HANDLE 3-10 DIMENTIONS ONLY. QLIKVIEW IS BASED ON AQL THAT CAN HANDLE AS MANY DIMENTIONS AS THE FILEDS AVAILABLE	Yes
87	A hybrid database that stores data in relational form and multidimensional form, as appropriate	QLIKVIEW DOES NOT NEED THIRD PARY DATABASE.	Yes
88	Is 'What-if" analysis supported	YES	Yes
89	GUI based Data Mining Capabilities	YES	Yes with SAS Enterprise Miner all different Data Mining Algorithms can be performed and the results can be viewed in desired format.
90	Enterprise Platform	YES	Yes, SAS supports Enterprise Intelligence Platform which provides capability to integrate all components of DWH-BI-AI across organization.
	Statistical Analytical Modeling	YES
91	Statistics	YES	SAS provides statistical data analysis tools to drive fact-based decisions.
92	Data & Text Mining	YES	SAS provides tools to build descriptive and predictive models and deploy results throughout the enterprise.
93	Model Management & Deployment		SAS provides tools to streamline the process of creating, managing and deploying analytical models.
94	Forecasting	YES	Forecasting tools from SAS helps to analyze and predict outcomes based on historical patterns.
95	Econometrics	YES	Use SAS components for applying statistical methods to economic data, problems and trends.
96	Quality Improvement		SAS provides SAS QC to identify monitor and measure quality processes over time.
97	Operations Research		Using SAS components to apply techniques such as optimization, scheduling, and simulation to achieve the best result.
98	Data Quality	AQL TAKES BUSINESS INTELEGENCE ONE STEP FURTHER THAN THE TREDITIONAL DATA WAREHOUSE ARCHITECHTURE - OLAP BASED SOLUTIONS	SAS has its own data quality tool (Data Flux), which is tightly integrated with SAS ETL tool. The Data quality solution comes with Indian Names and Address based Quality Knowledge base. SAS also provides Master Data Management solution.