BizFlow BPM Suite (also called BizFlow Plus BPM Suite) is a BPM platform offered by BizFlow (formerly HandySoft). Capabilities include process design and execution, case management, business rules, web application and form development, tasking and action tracking, ad-hoc reporting, and mobile access. The product can be deployed on-premises or in the cloud.
N/A
ProcessMaker
Score 9.0 out of 10
N/A
ProcessMaker is a process automation platform that helps organizations optimize and scale their business operations. By combining workflow automation, AI-driven decision-making, and advanced analytics, ProcessMaker empowers businesses to streamline complex processes, improve efficiency, and enhance customer experiences.
Although the tool was developed locally in South Korea, it is still a good tool and is already validated in a number of industries. The problem is, no one seems to know the future of the product. It is okay to use it as a pilot tool for any non-commercial purpose, but to be used in a professional or enterprise setting, maintenance, licensing, and other things need to be guaranteed by HandySoft.
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
BizFlow has a long history of development and implementation in a variety of industries. Its modeling tool is well-designed and user-friendly.
BizFlow supports seamless integration with backend services like MySQL databases and web services. Since it is an enterprise-wide BPM tool, system performance was stable and robust.
It supports modern m-health requirements, with social BPM functions and mobile support. Mobile integration especially was good, with the provider's secure messaging functions.
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.
It's not even clear that BizFlow is still managed by the company. It was a good tool before, but it looks like it's been fading out.
Although this was an R&D project in an academic institute, business support was extremely poor. We had no idea how to resolve issues; there were no online communities, documentation, or anyone who knew this product.
Few references in healthcare and clinical settings. We tried this for a proof-of-concept though, so it didn't matter.
At the beginning of the project, we considered popular tools for the modeling and execution of business processes: jBPM, Activity, Tibco, etc. jBPM is the tool we liked because of its strong support of BPMN 2.0 and strong online community and support. We had different expectations for BizFlow, like professional and business supports. In the end, although haven't decided yet, most likely we will move forward with jBPM instead of BizFlow. Unless things change, the tool will fade out from the market silently.
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.
We ended up deciding to not use BizFlow for future projects. The main reason wasn't due to ROI or cost, but was due to our uncertainty of the management and future direction of the tool by the company.
Besides the business issue, as far as reasonably priced software goes, it is a good tool.
Adopting BizFlow into a healthcare industry may come with additional expense due to its lack of references in the industry, which should be additionally considered.
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.
