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.
N/A
ProcessMaker
Score 9.0 out of 10
N/A
ProcessMaker's low-code intelligent automation platform empowers organizations to design business processes in seconds and without experience. It features an AI-powered decision engine and intelligent document processing (IDP) capabilities to gather insight from unstructure data.
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.
I loved it. You will not get an easier interface. You can develop workflow processes in a simple way, one which allows anyone to understand what you are trying to accomplish; however, you will get into some issues if your employees are scared of coding (when you get to the advanced features). For some, this will never be an issue as the knowledge you need is very basic. But for the school I was working with, it would have stopped them cold
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.
We can write PHP and Javascript code to handle the way the ProcessMaker does. It makes the ProcessMaker more flexible to meet our requests on our workflow.
The Processmaker provides a What-You-See-Is-What-You-Get flowchart design tool, we can draw our process very easy like Visio. And, We can use the flowchart to implement our workflow.
Also, the Dynaform, the electronic form function of Processmaker, is WYSIWYG form design tool, help us design forms participated in the process.
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.
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.)
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.
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.
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
Before making the decision to get ProcessMaker, we assessed different and best options in the market, which are also quite competitive. KiSSFLOW, Blueworks Live, and Bizagi, being the most relevant and ADONIS, to mention the ones we consider the most relevant and capable of meeting our needs. In the end, we went for ProcessMaker because of mainly three things as described before: 1. Real-time process status tracking. 2. Metrics and dashboards. 3. Ease of use for constructing diagrams.
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.
This would have been the easiest program to implement. It would have been the quickest, and the one that most of the employees would have been able to master. That alone would have saved countless dollars in time investment.
Unfortunately, the environment doesn't support knowledge of coding. So, they would never be able to advance further than a certain degree before having to bring someone else in again. It would have saved money at first, but then would have ended up costing in the long run.
