SPSS Statistics is a software package used for statistical analysis. It is now officially named "IBM SPSS Statistics". Companion products in the same family are used for survey authoring and deployment (IBM SPSS Data Collection), data mining (IBM SPSS Modeler), text analytics, and collaboration and deployment (batch and automated scoring services).
$99
per month per user
Spotfire
Score 8.3 out of 10
N/A
Spotfire, formerly known as TIBCO Spotfire, is a visual data science platform that combines visual analytics, data science, and data wrangling, so users can analyze data at-rest and at-scale to solve complex industry-specific problems.
N/A
Pricing
IBM SPSS Statistics
Spotfire
Editions & Modules
Base
USD 3,830
one-time fee per user
Standard
USD 8,440
one-time fee per user
Professional
USD 16,900
one-time fee per user
Premium
USD 25,200
one-time fee per user
Monthly subscription
USD 99
per month per user
Annual subscription
USD 1,188.00
per year per user
No answers on this topic
Offerings
Pricing Offerings
IBM SPSS Statistics
Spotfire
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
For Enterprise engagements, contact Spotfire directly for a custom price quote.
Product Manager - Mobile Computing Analytics Cloud Platform
Chose Spotfire
Our analysis suggested that Spotfire stacked up very well against all of the other vendors. When we looked at our evaluations, Spotfire did not win in any particular category. However, it did very well in all of the categories. Our evaluation also involved a pan-enterprise …
We evaluated on Mobility, Dashboarding, Web Based User Interface and Analytical capability. At the forefront was the user experience which accounted for just over half of our evaluation criteria. No platform was a 10/10 in all four categories - SAS Visual Analytics excelled in …
I described earlier that the only scenarios where I use SPSS are those where we have legacy projects that were developed in the late 90s or early 2000s using SPSS, and for some reason, the project (data set, scope, etc.) hasn't changed in 24+ years. This counts for 1-2 out of around 80 projects that I run. Whenever possible, I actively have my team move away from SPSS, even when that process is painful.
A high level of data integration is available here it supports various data sources and so on. Collaborating features allow users to give access to the dashboard and merge data analytics with other team members. It can meet the demands of both small and large size business enterprises. A customized dashboard and reports are provided to meet the specific needs and get support of extensibility through APIs and customized scripts.
SPSS has been around for quite a while and has amassed a large suite of functionality. One of its longest-running features is the ability to automate SPSS via scripting, AKA "syntax." There is a very large community of practice on the internet who can help newbies to quickly scale up their automation abilities with SPSS. And SPSS allows users to save syntax scripting directly from GUI wizards and configuration windows, which can be a real life-saver if one is not an experienced coder.
Many statistics package users are doing scientific research with an eye to publish reproducible results. SPSS allows you to save datasets and syntax scripting in a common format, facilitating attempts by peer reviewers and other researchers to quickly and easily attempt to reproduce your results. It's very portable!
SPSS has both legacy and modern visualization suites baked into the base software, giving users an easily mountable learning curve when it comes to outputting charts and graphs. It's very easy to start with a canned look and feel of an exported chart, and then you can tweak a saved copy to change just about everything, from colors, legends, and axis scaling, to orientation, labels, and grid lines. And when you've got a chart or graph set up the way you like, you can export it as an image file, or create a template syntax to apply to new visualizations going forward.
SPSS makes it easy for even beginner-level users to create statistical coding fields to support multidimensional analysis, ensuring that you never need to destructively modify your dataset.
In closing, SPSS's long and successful tenure ensures that just about any question a new user may have about it can be answered with a modicum of Google-fu. There are even several fully-fledged tutorial websites out there for newbie perusal.
collaboration - SPSS lacks collaboration features which makes it near impossible to collaborate with my team on analysis. We have to send files back and forth, which is tedious.
integration - I wish SPSS had integration capabilities with some of the other tools that I use (e.g., Airtable, Figma, etc.)
user interface - this could definitely be modernized. In my experience, the UI is clunky and feels dated, which can negatively impact my experience using the tool.
The donut chart is I guess a powerful illustrations but I hope it should be done quite simple in Spotfire. But in Spotfire there are lots of steps involve just to build a simple donut chart.
Table calculation (like Row or Column Differences) should be made simple or there should be drag and drop function for Table Calculation. No need for scripting.
Information Link should be changed. If new columns are added to the table just refreshing the data should be able to capture the new column. No need extra step to add column
Both money and time are essential for success in terms of return on investment for any kind of research based project work. Using a Likert-scale questionnaire is very easy for data entry and analysis using IBM SPSS. With the help of IBM SPSS, I found very fast and reliable data entry and data analysis for my research. Output from SPSS is very easy to interpret for data analysis and findings
-Easy to distribute information throughout the enterprise using the webplayer. -Ad hoc analysis is possible throughout the enterprise using business author in the webplayer or the thick client. -Low level of support needed by IT team. Access interfaces with LDAP and numerous other authentication methods. -Possible to continually extend the platform with JavaScript, R scripts, HTML, and custom extensions. -Ability to standardize data logic through pre-built queries in the Information Designer. Everyone in the enterprise is using the same logic -Tagging and bookmarking data allows for quick sharing of insights. -Integration with numerous data sources... flat files, data bases, big data, images, etc. -Much improved mapping capability. Also includes the ability to apply data points over any image.
Probably because I have been using it for so long that I have used all of the modules, or at least almost all of the modules, and the way SPSS works is second nature to me, like fish to swimming.
Basic tasks like generating meaningful information from large sets of raw data are very easy. The next step of linking to multiple live data sources and linking those tables and performing on the fly analysis of the imported data is understandably more difficult.
Even though, it's a rather stable and predictable tool that's also fast, it does have some bugs and inconsistencies that shut down the system. Depending on the details, it could happen as often as 2-3 times a week, especially during the development period.
Generally, the Spotfire client runs with very good performance. There are factors that could affect performance, but normally has to do with loading large analysis files from the library if the database is located some distance away and your global network is not optimal. Once you have your data table(s) loaded in the client application, usually the application is quite good performance-wise.
I have not contacted IBM SPSS for support myself. However, our IT staff has for trying to get SPSS Text Analytics Module to work. The issue was never resolved, but I'm not sure if it was on the IT's end or on SPSS's end
Support has been helpful with issues. Support seems to know their product and its capabilities. It would also seem that they have a good sense of the context of the problem; where we are going with this issue and what we want the end outcome to be.
The instructor was very in depth and provided relevant training to business users on how to create visualizations. They showed us how to alter settings and filter views, and provided resources for future questions. However, the instructor failed to cover data sources, connecting to data, etc. While it was helpful to see how users can use the data to create reports, they failed to properly instruct us on how to get the dataset in to begin with. We are still trying to figure out connections to certain databases (we have multiple different types).
The online training is good, provides a good base of knowledge. The video demonstrations were well-done and easy to follow along. Provided exercises are good as well, but I think there could be more challenging exercises. The training has also gone up in price significantly in the last 3 years (in USD, which hurts us even more in Canada), and I'm not sure it is worth the money it now costs (it is worth how much it cost 3 years ago, but not double that.)
Have a plan for managing the yearly upgrade cycle. Most users work in the desktop version, so there needs to be a mechanism for either pushing out new versions of the software or a key manager to deal with updated licensing keys. If you have a lot of users this needs to be planned for in advance.
The original architecture I created for our implementation had only a particular set of internal business units in mind. Over the years, Spotfire gained in popularity in our company and was being utilized across many more business units. Soon, its usage went beyond what the original architectural implementation could provide. We've since learned about how the product is used by the different teams and are currently in the middle of rolling out a new architecture. I suggest:
Have clearly defined service level agreements with all the teams that will use Spotfire. Your business intelligence group might only need availability during normal working hours, but your production support group might need 24/7 availability. If these groups share one Spotfire server, maintenance of that server might be a problem.
Know the different types of data you will be working with. One group might be working with "public" data while another group might work with sensitive data. Design your Library accordingly and with the proper permissions.
Know the roles of the users of Spotfire. Will there only be a small set of report writers or does everyone have write access to the Library?
ALWAYS add a timestamp prompt to your reports. You don't want multiple users opening a report that will try and pull down millions of rows of data to their local workstations. Another option, of course, is to just hard code a time range in the backing database view (i.e. where activity_date >= sysdate - 90, etc.), but I'd rather educate/train the user base if possible.
This probably goes without saying, but if possible, point to a separate reporting database or a logical standby database. You don't want the company pounding on your primaries and take down your order system.
I have used R when I didn't have access to SPSS. It takes me longer because I'm terrible at syntax but it is powerful and it can be enjoyable to only have to wrestle with syntax and not a difficult UI.
Spotfire is significantly ahead of both products from an ETL and data ingestion capability. Spotfire also has substantially better visualizations than Power BI, and although the native visualizations aren't as flexible in Tableau, Spotfire enables users to create completely custom javascript visaualizations, which neither Tableau or Power BI has. Tableau and Power BI are likely only superior to Spotfire with respect to embedded analysis on a website.
In an enterprise architecture, if Spotfire Advanced Data services(Composite Studio),data marts can be managed optimally and scalability in a data perspective is great. As the web player/consumer is directly proportional to RAM, if the enterprise can handle RAM requirement accomodating fail over mechanisms appropraitely, it is definitely scalable,
I found SPSS easier to use than SAS as it's more intuitive to me.
The learning curve to use SPSS is less compared to SAS.
I used SAS, to a much lesser extent than SPSS. However, it seems that SAS may be more suitable for users who understand programming. With SPSS, users can perform many statistical tests without the need to know programming.
