Longview Analytics (arcplan) vs. Tableau Server

It is very suitable for complete corporate BI solutions. If you see BI as embedding information into your organization and business processes, and thus as more than just a few scattered dashboards and reports, arcplan is your platform. It's less suitable for ad-hoc reporting and data discovery. It can do it (everything is possible), but there is strong competition in this area.

Tableau Server is well suited for a data warehouse build and handling big data. Tableau data aggregation, transformation, clustering capability is powerful and easy to implement. The choice of charts and visualisation tools is outstanding. Customisation and dynamic data visualisation capability is superb. The user interface takes some time getting used to.

Incentivized

• Excellent dashboard.
• Well advanced BI metrics.
• Better interfacing to other DW.

Incentivized

• It's good at doing what it is designed for: accessing visualizations without having to download and open a workbook in Tableau Desktop. The latter would be a very inefficient method for sharing our metrics, so I am glad that we have Tableau Server to serve this function.
• Publishing to Tableau Server is quick and easy. Just a few clicks from Tableau Desktop and a few seconds of publishing through an average speed network, and the new visualizations are live!
• Seeing details on who has viewed the visualization and when. This is something particularly useful to me for trying to drive adoption of some new pages, so I really appreciate the granularity provided in Tableau Server

Incentivized

• Positioning and marketing. Most BI vendors use a non-technical sales strategy and focus on shiny, sexy dashboards to sell the story. In order to position arcplan fairly and correctly, the technical and business advantages need to be part of a sales story. So, it is not really an easy product to sell to customers, if it has to compete with now-to-wow-five-minute products.
• Learning/training for developers. It's easy to learn the basics of arcplan, because the interface is logical. But nothing prevents a beginning developer from creating a monstrous application, because there is no prescribed architecture. It really takes some experience to become a good arcplan architect. It's a disadvantage resulting from one of arcplan's biggest advantages.
• Data connectors: arcplan standard comes with a connector of your choice. Additional connectors need to be purchased separately. Many other products come with a full range of connectors.

• Tableau Server has had some issue handling some of our larger data sets. Our extract refreshes fail intermittently with no obvious error that we can fix
• Tableau Server has been hard to work with before they launched their new Rest API, which is also a little tricky to work with

Incentivized

It simply is used all the time by more and more people. Migrating to something else would involve lots of work and lots of training. The renewal fee being fair, it simply isn't worth migrating to a different tool for now.

Incentivized

I think the use case we described earlier about a non-technical user that was copying/pasting data into Word during emergencies is our best reason. This person had little technical ability, and the Tableau mobile solution powered by Tableau server completely resolved the issues. She has since become one of the most vocal proponents of Tableau.

Incentivized

Our instance of Tableau Server was hosted on premises (I believe all instances are) so if there were any outages it was normally due to scheduled maintenance on our end. If the Tableau server ever went down, a quick restart solved most issues

While there are definitely cases where a user can do things that will make a particular worksheet or dashboard run slowly, overall the performance is extremely fast. The user experience of exploratory analysis particularly shines, there's nothing out there with the polish of Tableau.

I think the folks that work in support are generally pretty good at what they do (when you get them on a WebEx). But the process of reporting issues to them and waiting for a response (via email only) is a hassle. I never understood why you can't just call them up and discuss the issues with them. It would take a handful of email exchanges before they would agree to a WebEx session. That was frustrating.

In our case, they hired a private third party consultant to train our dept. It was extremely boring and felt like it dragged on. Everything I learned was self taught so I was not really paying attention. But I do think that you can easily spend a week on the tool and go over every nook and cranny. We only had the consultant in for a day or two.

The Tableau website is full of videos that you can follow at your own pace. As a very small company with a Tableau install, access to these free resources was incredibly useful to allowing me to implement Tableau to its potential in a reasonable and proportionate manner.

Implementation was over the phone with the vendor, and did not go particularly well. Again, think this was our fault as our integration and IT oversight was poor, and we made errors. Would they have happened had a vendor been onsite? Not sure, probably not, but we probably wouldn't have paid for that either

Personally, I prefer QlikView not because it's more stable but simply just for the looks of the dashboard. One of my clients in Sydney recently moved from arcplan to QlikView. The reason was mainly looks and that QlikView has more training materials for the support users to train with. So in all, it does not really stack well against QlikView.

Incentivized

Today, if my shop is largely Microsoft-centric, I would be hard pressed to choose a product other than Power BI. Tableau was the visualization leader for years, but Microsoft has caught up with them in many areas, and surpassed them in some. Its ability to source, transform, and model data is superior to Tableau. Tableau still has the lead in some visualizations, but Power BI's rise is evidenced by its ever-increasing position in the leadership section of the Gartner Magic Quadrant.

Incentivized

• Tableau does take dedicated FTE to create and analyze the data. It's too complex (and powerful) a product not to have someone dedicated to developing with it.
• There are some significant setup for the server product.
• Once sever setup is complete, it's largely "fire and forget" until an update is necessary. The server update process is cumbersome.

Incentivized