JMP vs. Logi Info

It is perfectly suited for statistical analyses, but I would not recommend JMP for users who do not have a statistical background. As previously stated, the learning curve is exceptionally steep, and I think that it would prove to be too steep for those without statistical background/knowledge

Logi Composer is the best of the product range that Logi Analytics offers; Logi Info is, in my mind, a terrible experience and should be discontinued. Logi Info is not a BI tool and many CEOs and product managers believe it is. Instead, it is a tool for web developers to create IIS apps with a library of BI-type components, and with everything else having to be hand-coded in JavaScript and CSS. Maybe this was cool back in the early 2000s when Logi Info came about, but today I'd recommend using Visual Studio, C#, .NET, and finding a NuGet package for your visualisations if you wanted to go the route of making your own web app. This said, where it is suited is if you have a burning desire to make a stand-alone IIS-based web application and you don't need or want to leverage any existing skills in .NET or PHP or other frameworks/languages. Instead, you want to use the Logi Info XML-based BI widgets and you're happy to make something quick without needing it to look really awesome.

Incentivized

• JMP is designed from the ground-up to be a tool for analysts who do not have PhDs in Statistics without in anyway "dumbing down" the level of statistical analysis applied. In fact, JMP operationalizes the most advanced statistical methods. JMP's design is centred on the JMP data table and dialog boxes. It is data focused not jargon-focussed. So, unlike other software where you must choose the correct statistical method (eg. contingency, ANOVA, linear regression, etc.), with JMP you simply assign the columns in a dialog into roles in the analysis and it chooses the correct statistical method. It's a small thing but it reflects the thinking of the developers: analysts know their data and should only have to think about their data. Analyses should flow from there.
• JMP makes most things interactive and visual. This makes analyses dynamic and engaging and obviates the complete dependence on understanding p-values and other statistical concepts(though they are all there) that are often found to be foreign or intimidating.
• One of the best examples of this is JMP's profiler. Rather than looking at static figures in a spreadsheet, or a series of formulas, JMP profiles the formulas interactively. You can monitor the effect of changing factors (Xs) and see how they interact with other factors and the responses. You can also specify desirability (maximize, maximize, match-target) and their relative importances to find factor settings that are optimal. I have spent many lengthy meetings working with the profiler to review design and process options with never a dull moment.
• The design of experiments (DOE) platform is simply outstanding and, in fact, the principal developers of it have won several awards. Over the last 15 years, using methods broadly known as an "exchange algorithm," JMP can create designs that are far more flexible than conventional designs. This means, for example, that you can create a design with just the interactions that are of interest; you can selectively choose those interactions that are not of interest and drop collecting their associated combinations.
• Classical designs are rigid. For example, a Box-Benhken or other response surface design can have only continuous factors. What if you want to investigate these continuous factors along with other categorical factors such as different categorical variables such as materials or different furnace designs and look at the interaction among all factors? This common scenario cannot be handled with conventional designs but are easily accommodated with JMP's Custom DOE platform.
• The whole point of DOE is to be able to look at multiple effects comprehensively but determine each one's influence in near or complete isolation. The custom design platform, because it produces uniques designs, provides the means to evaluate just how isolated the effects are. This can be done before collecting data because this important property of the DOE is a function of the design, not the data. By evaluating these graphical reports of the quality of the design, the analyst can make adjustments, adding or reducing runs, to optimize cost, effort and expected learnings.
• Over the last number of releases of JMP, which appear about every 18 months now, they have skipped the dialog boxes to direct, drag-and-drop analyses for building graphs and tables as well as Statistical Process Control Charts. Interactivity such as this allows analysts to "be in the moment." As with all aspects of JMP, they are thinking of their subject matter without the cumbersomeness associated with having to think about statistical methods. It's rather like a CEO thinking about growing the business without having to think about every nuance and intricacy of accounting. The statistical thinking is burned into the design of JMP.
• Without data analysis is not possible. Getting data into a situation where it can be analyzed can be a major hassle. JMP can pull data from a variety of sources including Excel spreadsheets, CSV, direct data feeds and databases via ODBC. Once the data is in JMP it has all the expected data manipulation capabilities to form it for analysis.
• Back in 2000 JMP added a scripting language (JMP Scripting Language or JSL for short) to JMP. With JSL you can automate routine analyses without any coding, you can add specific analyses that JMP does not do out of the box and you can create entire analytical systems and workflows. We have done all three. For example, one consumer products company we are working with now has a need for a variant of a popular non-parametric analysis that they have employed for years. This method will be found in one of the menus and appear as if it were part of JMP to begin with. As for large systems, we have written some that are tens of thousands of lines that take the form of virtual labs and process control systems among others.
• JSL applications can be bundled and distributed as JMP Add-ins which make it really easy for users to add to their JMP installation. All they need to do is double-click on the add-in file and it's installed. Pharmaceutical companies and others who are regulated or simply want to control the JMP environment can lock-down JMP's installation and prevent users from adding or changing functionality. Here, add-ins can be distributed from a central location that is authorized and protected to users world-wide.
• JMP's technical support is second to none. They take questions by phone and email. I usually send email knowing that I'll get an informed response within 24 hours and if they cannot resolve a problem they proactively keep you informed about what is being done to resolve the issue or answer your question.

• Clear/Concise view of data. Easily intuitive, amazing drill down capability, fully user configurable panels and dashboards.
• Self-Service is such a powerful tool for facilities that want to create/design their own reports/dashboards, it's instantly recognized as being very powerful and agile.
• Logi software makes the designer realize that they should think outside the box and not stick with "it's how we have always done it limitation". It allows you to be very creative.

• In general JMP is much better fit for a general "data mining" type application. If you want a specific statistics based toolbox, (meaning you just want to run some predetermined test, like testing for a different proportion) then JMP works, but is not the best. JMP is much more suited to taking a data set and starting from "square 1" and exploring it through a range of analytics.
• The CPK (process capability) module output is shockingly poor in JMP. This sticks out because, while as a rule everything in JMP is very visual and presentable, the CPK graph is a single-line-on-grey-background drawing. It is not intuitive, and really doesn't tell the story. (This is in contrast with a capability graph in Minitab, which is intuitive and tells a story right off.) This is also the case with the "guage study" output, used for mulivary analysis in a Six Sigma project. It is not intuitive and you need to do a lot of tweaking to make the graph tell you the story right off. I have given this feedback to JMP, and it is possible that it will be addressed in future versions.
• I've never heard of JMP allowing floating licenses in a company. This will ALWAYS be a huge sticking point for small to middle size companies, that don't have teams people dedicated to analytics all day. If every person that would do problem solving needs his/her own seat, the cost can be prohibitive. (It gets cheaper by the seat as you add licenses, but for a small company that might get no more than 5 users, it is still a hard sell.)

• It is not always intuitive to incorporate JavaScript into Logi Info. The tools are all available, but the process requires multiple resource in translating between Logi and JavaScript.
• The toolbox is too vast for Logi to provide a 'quick implementation' or 'quick start guide'. There are so many tools that Logi expects the client to determine which fit their use case. There are purchasable 'Professional Services' options for implementation, but without these, the toolset is almost too big.

JMP has been good at releasing updates and adding new features and their support is good. Analytics is quick and you don't need scripting/programming experience. It has been used organization wide, and works well in that respect. Open source means that there are concerns regarding timely support. Cheap licensing and easy to maintain.

Logi Info is a very outdated, archaic product that tries to build .NET / Java web apps using an obscure XML-based markup language to implement BI widgets, with a lot of extra CSS/JavaScript needed on your own to make it do the best things. There are many other better tools. It is not a BI tool, and as a web development tool it's not great either. I'd recommend getting some good third-party .NET BI library if you want your web devs to make the reports, otherwise use a proper BI tool like Power BI or Tableau, or even Logi Composer (formerly ZoomData before Logi acquired it.)

Incentivized

The GUI interface makes it easier to generate plots and find statistics without having to write code. The JSL scripting is a bit of a steep learning curve but does give you more ability to customize your analysis. Overall, I would recommend JMP as a good product for overall usability.

Incentivized

I am giving 9 rating because the Logi Info still needs to improve on the tutorials part and make it easy for the beginners. Otherwise, it's a very good analytics tool which offers more than 20 types of visualization. It's predictive analysis feature and easy to embed with technologies make it stand out in the market.

Incentivized

Support is great and give ease of contact, rapid response, and willingness to 'stick to the task' until resolution or acknowledgement that the problem would have to be resolved in a future build. Basically, one gets the very real sense that another human being is sensitive to your problems - great or small.

Incentivized

The support process is bit slow and has a good scope improvement but overall it's good as team is very supportive. They generally take 1-2 days time to respond emails sent to them but some times a delay is also expected. Overall, I did not face any major issues using the service.

Incentivized

I have not used your online training. I use JMP manuals and SAS direct help.

MS Excel with AnalysisToolPak provides a home-grown solution, but requires a high degree of upkeep and is difficult to hand off. Minitab is the closes competitor, but JMP is better suited to the production environment, roughly equivalent in price, and has superior support.

Incentivized

Logi gave us the flexibility we needed to meet the configurable nature of our product and for the need to create custom reports. Other products did not allow flexbility to generate reports via script as was one of our primary requirements.

Incentivized

• ROI: Even if the cost can be high, the insights you get out of the tool would definitely be much more valuable than the actual cost of the software. In my case, most of the results of your analysis were shown to the client, who was blown away, making the money spent well worth for us.
• Potential negative: If you are not sure your team will use it, there's a chance you will just waste money. Sometimes the IT department (usually) tries to deploy a better tool for the entire organization but they keep using the old tool they are used too (most likely MS Excel).

Incentivized

• By embedding Logi in our solution and using the Logi Self-Service Module we can provide this flexibility to our users without requiring custom development work for each new request.
• We succeeded in developing embedded self-service analytics at scale with a combination of Logi analytics as front-end and a Cassandra data lake with Spark aggregation algorithms as back-end.
• We analyze the insurance industry and need to replicate different data formats across hundreds of databases to support multi-tenant (customer) BI reports and "ad hoc" data review on millions or hundreds of millions of records per customer.

Incentivized