JMP Pro offers all the capabilities of JMP, plus advanced features for more sophisticated analysis including predictive modeling and cross-validation techniques.
N/A
Looker
Score 8.2 out of 10
N/A
Looker is a BI application with an analytics-oriented application server that sits on top of relational data stores. It includes an end-user interface for exploring data, a reusable development paradigm for data discovery, and an API for supporting data in other systems.
JMP Pro is perfectly suited for statistical analysis but users should have some statistical knowledge before using it since there may be some terms/functions in the software that are not widely used in other fields. No prior coding experience is needed to use JMP Pro. However, most people doing data processing would prefer to code their analysis.
Quick dashboards from Google Sheets - Easier to do the graphs than in Google Sheets - Operational dashboards to be used in the day-to-day work - It is good both for retrospective data and to do a pulse check of the current status - Better for not giant amounts of data and not multiple data sources. - If you need a lot of graphs to be displayed on the same page, it can be a bit glitchy during configuration (then the use works fine).
I think the most awesome thing about JMP Pro is the Profiler component. The Profiler component makes sharing analyses interactive on the web using interactive HTML5. The Profiler makes showing the impact of interaction effects so easy. It's the best statistical software feature I think I've ever come across.
JMP Pro does dashboards well. It is relatively straight-forward to create four pane dashboards that automatically update. I think it's nice.
I think JMP Pro graphics are a massive improvement when compared to the graphics produced by its parent company - SAS. JMP Pro's features are vast, and easy to use and understand.
Filtering - you can filter across different dimensions and metrics to get a more specific "cut" of data
Refreshing - data automatically ingests into Looker which allows reports to be updated and backfilled in real time
Conditional Reporting - you can leverage Looker's reporting features to flag when a given metric or KPI falls below or above a specified threshold. For example, if you had a daily sales benchmark in a SAAS organization, you could use Looker to flag whenever daily sales falls above or below the benchmark
Looker is less graphical or pictorial which makes it less attractive
Consumes a lot of memory when there are multiple rows and columns, impacts performance too
At times when we download huge chunks of raw data from Looker dashbords, the time taken to prepare the file is enormous - The user fails to understand if Looker has frozen or if the data is getting prepared in the background for downloading. In turn, user ends up triggering multiple downloads
We've been very happy with Looker so far, and all teams in the organization are starting to see its value, and use it on a frequent basis. It has quickly become our accessible "source of truth" for all data/metrics.
Looker is relatively easy to use, even as it is set up. The customers for the front-end only have issues with the initial setup for looker ml creations. Other "looks" are relatively easy to set up, depending on the ETL and the data which is coming into Looker on a regular basis.
Never had to work with support for issues. Any questions we had, they would respond promptly and clearly. The one-time setup was easy, by reading documentation. If the feature is not supported, they will add a feature request. In this case, LDAP support was requested over OKTA. They are looking into it.
The intuitive interface JMP Pro offers is more interactive than R studio, but since coding is not required in JMP Pro, programming analysis in R studio is more convenient in some aspects. JMP Pro is able to quickly analyze multiple variables and produce reasonable outputs and models, which is valuable for users doing data analysis.
Looker is an off-the-shelf, free tool for Google business users. Other than the internal cost of time to build, we had no costs to set up what we needed to do. Knowledge sharing internally and using templates greatly reduced this cost, making the overall cost very low.
The overall ROI for JMP Pro was positive because of the Profiler option. This makes communicating the results of regressions as easy and complex as needed. It's such an awesome feature, I wonder why it wasn't offered before.
If JMP Pro didn't have the Profiler feature, I think I would still recommend using JMP Pro, but the recommendation is not a slam dunk. The software has its own programming language, which is not well-known and requires effort to debug.
JMP Pro's dashboards are well-built, and provide a positive ROI from the perspective of creating real-time, interactive reporting. It's very nice for this feature.
Allowing others to self-serve their own analytics and connect it to Looker simply and easily has helped unblock the central data team so they can instead focus on validated dashboards whilst stakeholders manage their day-to-day analysis themselves. Countless engineering hours have been freed up by not having to manage every user permission for each BI tool; we have a BYOBI approach; Bring Your Own BI
Creation and management of a semantic layer (LookML =Looker Modeling Language ) allows peoples sandboxes and production databases to become clutter free. Minor adjustments, conditional fields, and even some modelling can all be done in LookML which doesn't need oversight or governance from the central data team.
LookML, specifying drilldown fields and their sub-queries, as well as generally creating dynamic parameters with Liquid are all great features, but can have a steep learning curve. it may take some time to understand how to create this middle layer correctly, or even pose a risk of inheriting complex code from another source which can be unmaintainable if it becomes too big. Some level of governance is recommended if Looker is used by a large number of editors.
