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
Power BI For Office 365 (discontinued)
Score 8.5 out of 10
N/A
Power BI for Office 365 allowed users to model and analyze data, and query large datasets with complex natural language queries. It has been discontinued in favor of other editions of Power BI going forward.
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.
If you're already using Office 365, Power BI for O365 is an easy choice. Start playing around with the free version and then easily add individual Pro licenses with little risk. However, if you anticipate using this with many users, it can get expensive quickly.
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.
Easy to make visual dashboards from SQL queries. Previously we had to use a third party application that had to run on a web server that was so complex to setup and run. PowerBI removes all that.
Ability to control who/which group has access to each dashboard or report. Ties in well with the rest of the Office 365 ecosystem.
Has many connectors to allow pulling data from various systems, both onsite (via gateway) or external (via APIs), and join the data to create a report/dashboard.
Ability to show data but also export the data, if permitted.
Easy to show PowerBI dashboards on SharePoint or on other websites via embedded code.
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.
Licensing: Currently, Microsoft has a fixed pricing model for Office 365 users, regardless of role/function of the user. Most organizations have a small number of "power users" that create usable content and many more "consumers" that simply view/run reports created by power users. Microsoft does not differentiate between these users, and thus the pricing limits organizations from large deployments of the software.
Version incompatibility: Excel 2010 and 2013 workbooks are compatible with each other. However, workbooks created in 2010 that include PowerPivot databases must be upgraded to 2013 format to run in 2013. Subsequently, you cannot open these upgraded PowerPivot workbooks in 2010. This requires ALL users to be on the same version.
Visualization: Excel charting with PowerPivot workbooks is adequate for many users. Power View also contains a number of GREAT visualizations, including animated bubble charts and a very flexible dashboard/report design canvas. However, compared to some of the other self-service BI solutions, it is still limited in its visualization capabilities.
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
I will continue to recommend this suite to folks looking for a reporting and analytics solution, as I find in MOST cases, it's great at meeting almost every requirement I've been given by a multitude of clients across a range of industries. I've built Capacity Planning solutions that allowed end user input which was then submitted to SharePoint, Executive Dashboards, custom applications, simple analytical tools for teams to easily slice and dice data, and super simple reports as well as some very complicated ones. If you haven't seen the demos online, do a search, and see for yourself - this is a great BI suite! (I do not work for Microsoft, although I do consult out there from time to time. I do occasionally make a recommendation for a different BI reporting tool, but in general, find Excel can accomplish quite a bit for less money and in less time.)
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.
We are satisfied with the functionality and capabilities of Power BI. Product is cost effective and full-fill the reporting requirements of the organization. You can perform most of the report level complex analysis with the help of DAX which makes Power BI very powerful analytic tool. Power BI for Office 365 has gone away and Power BI is the next evolution of it. Power BI comes with your Office 365 E5 subscription or you can purchase licensing for it separately.
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
as of now there is strong community for Power BI, you can get solution for most of your problems from there. Also you can send your error to Microsoft as well. After every 15 days they release updates to overcome all the issues of defects.
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.
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.
Oracle was nice, super expensive to implement if it's not in use already. JobDiva is choppy and heavy on the system while does not give great reports. Salesforce is good; remote access is good however their support is terrible
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.
As a Microsoft Partner implementing Business Intelligence solutions, Power BI has removed the barrier for our clients to begin the "BI journey". So often, projects get hung up in that early phase of procuring and installing/configuring expensive hardware and software. Just simply getting started and designing a beginning solution has allowed our clients to see results in 1-2 weeks using their data that might have taken months to achieve otherwise.
One significant ROI example is process improvement. In many cases, individuals or teams are spending days each month gathering data from multiple sources for reporting to their constituents. We are reducing these times to minutes by automating many of the data collection and integration processes that were previously manual.
