Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Tableau vs Qlik vs Panorama Necto

1 511 vues

Publié le

Comparison between the top 3 data discovery solutions in the market. Business Intelligence Comparison between Qlik vs Tableau vs Panorama

Gartner positions Panorama as the present and Future of BI with their smart data discovery approach.

Publié dans : Technologie
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Tableau vs Qlik vs Panorama Necto

  1. 1. Panorama Necto VS Qlik View & Sense vs Tableau Necto offers you a full web experience with true self - service features in a single governed web interface. By using Necto you also value from:  Fast ROI with a unique Development method.  Automated insights, Suggestiveness and Collaboration in context.  Notifier (scheduling mechanism) that can be defined by any business user and that can be triggered by exceptions.  Data analysis that is supported by amazing Infographic visualizations. Most of the Qlik features need to be developed in the desktop app by a skilled developer, before reaching the actual end user, which affects the self service level. Also – in case you are using OLAP cubes today – Qlik is not able to connect to them directly, and has to recreate these schemas in its own proprietary, while losing the ability to use OLAP actions and security. Topic Panorama Necto QlikView Tableau Visual – The ability to view insights and analytical business processes in the business language with limitless visualization. In Necto, business users can visualize their insights and their business processes with a full infographic suite. Necto has more than 2000 Infographics in its library, while you can add any other visualization simply & quickly from the web. In Qlikview, the Inner infographics suite is limited, however a super user can Mash up images from the web and customize them in the QlikView Model. Another mash up is the extensions objects that can mash up Maps, Charts and Infographic from the web. Tableau supports infographics using some basic shapes. Users can upload their own shapes. Suggestive –The BI system should recommend to the user the most relevant insight to focus on. Necto Suggestive Discovery engine recommends to the users the most relevant insights to focus on, based on personal preferences and user’s behavior. No suggestive engine. With Tableau the user doesn’t have any Insight’s recommendation and has to search for the insight by himself. Most of the usage of Tableau is done by analysts who search for insights.
  2. 2. Topic Panorama Necto QlikView Tableau Automated Analysis – the ability of business users to find insights automatically and quickly. Necto supports full Exception handling capabilities- including bubble up exception, automated insights, root cause analysis, and defined exceptions. With Necto a business user can find insights and root causes in just 2 clicks. No automated analysis. Tableau doesn’t support automated analysis and the user need to use “brute force” in order to find insight. It doesn’t support “Bubble up exceptions”, or “one click exceptions”. Any exceptions must be programmed. BI Collaboration in context – the ability for users to collaborate in context, on data and insight, and make better decisions. Necto supports a fully collaborative decision making capabilities in context. A user can collaborate with his colleagues to make business decisions in real time. Qlikview supports the following methods of collaboration:  Build and share analysis objects.  Share analysis with bookmarks, which preserve your selections.  Notes and comments, per component.  Shared sessions. Tableau has no collaboration capacities aside from the trivial share and annotations that Necto supports as well.
  3. 3. Topic Panorama Necto QlikView Tableau Cost – total cost of ownership for the first deployment and for users’ growth within your organization. Necto provides a web server + clients from the get go, hence the price to start the deployment and the price to grow is very competitive and much cheaper than Qlik. Moreover, all data connectors come with the system for the same price point, while in Qlik there is an extra cost for it. "$1,350 per named user Enterprise Edition Server Standard Support- 20% of list price & $35,000 per server“ Suite for small businesses- the SMB server is 8,400$ with 100 document users and 25 full users. The overall cost might be larger than expected with all paid features. QV requires each user to have a license, they don’t have unlimited solutions. Tableau has its ‘land & expand” strategy, which means that you pay 2000$ per user to try (desktop) but when you want to grow, you have to buy the Tableau server with a price list of more than 250,000$ (If there are a lot of users. It’s about 1,000$ per user). There’s also an option to buy Tableau Online – much cheaper but only the server is in the cloud. You still need to buy the Desktop version.)2000$ per user) Also, for the desktop version. You must buy the expensive $2000 edition to get all data connectors, with $1000 you only get the Excel flat file basics.
  4. 4. Topic Panorama Necto QlikView Tableau Governed – a system which is very easy to manage. Fully web based with just one web client (no desktop) that keeps one version of the truth. Necto maintains a single version of the truth in a single Web interface for all features. There is no need for Desktop deployment that creates data silos and many versions of the truth. All the Necto applications run in a single user interface that requires minimal training A QVW file (Model + Dashboard) can use different logics to bring same data. This might result in different versions of the truth and also will make it hard on the maintenance of the models. Tableau is mainly a desktop tool. It requires IT to manage installations and each user can create his own version of the truth (views and dashboards) with his un-managed desktop client. When moving into a server deployment, which is very expensive, the IT need to deal with 2 areas, Desktop and Server. Each has its own functionality.
  5. 5. Topic Panorama Necto QlikView Tableau Dashboard development and maintaining effort – a fast ROI with the ability to quickly apply changes and easiness of redesigning. Necto’s concept is a development on a Single Web Interface. This enables more flexibility for developers and for end user. In this way – while developing a few components you see how your changes reflect the other components in the same Workboard, with no need to move between environments, or publish views from client to server. A QVW file (Model + Dashboard) is being developed in the desktop client tool, which needs developer skills. That is because it is done in a Script Language Proprietary Data Layer. After developing the data model, there is a need to publish the data model to the server. Self-service experience is Problematic since you can only use the given data schema, and not change it. Tableau is not fully web enabled. Developers have to work on Tableau desktop tool in order to create a view or a data source. This will enable connectivity between different data sources and is only available for a specific workbook. It makes it difficult to maintain different logic in different workbooks. Once you want to redesign a Dashboard - you have to move back to the ‘views area’ and redesign your view, to then re- publish it if you use a Tableau server. Notifications & Alerts – the ability for an end user to define his own notifications and alerts within the system. Necto provides the business users with the ability to define alerts and notifications within the system based on time, thresholds, exceptions, etc – all that in a just 2 clicks. Business User is not able to create a notification by itself Only systems managers (not users), can define expectations and emails, hindering the ability for the end users to work and report on their needs. The end user can subscribe to an existing subscription.
  6. 6. Working with OLAP This is what we do, bringing in Actions, Security and other OLAP features. Because QV does not use MDX (the Native OLAP language), there is a very limited support to SSAS. For proper QV functionalities, the cubes must be replicated on QV proprietary technology. This is done by a developer who copies the OLAP data schema (DSV) and tries to simulate it in the QVW file. (Every cube turns to be a QVW file. This is causing a lot of overhead for the Qlik implementation, which includes re-defining Actions and security. Also keep in mind that Qlik is not as easy to maintain for complex OLAP solution. Tableau has very limited support to SSAS, since It cannot use predefined Security and Actions. Gartner Magic Quadrant for Business Intelligence and Analytics Platforms, Feb 2015 • Collaboration, analytic dashboards and business user data mashup are key product strengths. • The main reasons why customers choose Panorama's software are its ease of use for end users and developers and its functionality • Panorama Necto offers deep OLAP- style analysis within an updated social and collaboration-based guided data discovery user experience. • Qlik offers two products with two different pricing models that might be confusing for buyers • Qlik Sense is not matured and a work- in-progress • Qlikview scored lower than the overall average in BI administration, metadata management and for business user data mashup • Self-service data preparation is a future road map item for Qlik. 1. Metadata management, development and integration, BI platform administration, embedded BI and collaboration are rated as weaker capabilities of the platform, making it less well suited for centralized and embedded use cases 2. Tableau's enterprise features around data modeling and reuse, scalability and embed ability … are still more limited than IT- 1centric system-of- record platforms.
  7. 7. Other concerns 1. Necto allows to manually define a drill through from one Workboard to another, while slicing on the relevant content. By default this feature is disabled while moving from one Workboard to another 2. The Necto Model generates a SQL server Tabular model, which is fully accessible by all BI tools. 3. Necto pricing is easy to understand. 1. Your users might find the “must have” associative engine complex and difficult to understand and use. 2. The Qlik Model is a proprietary and you cannot connect to it from any other tool 3. In order to work with extensions/API’s/ and different browser – you will need to use Ajax method which is a bit slower than ActiveX. Regarding “Sense” specifically: 1. Sense is fully HTML5 but is lacking basic functionalities and a lot of extensions (I.e. “Share sessions” functionality). 2. Sense has different pricing and different servers which depends on the functionality you may need. Pay attention to Other products or extensions you might need to pay for. I.e. “Publisher” ($20K). 1. The Tableau Model is a proprietary and you cannot connect to it from any other tool