ARIS vs. BizFlow BPM Suite

Well suited for enterprise architecture modeling where the intent to document elements beyond processes as well, such as risks and controls, KPIs, systems, org charts, etc. It also has the excellent capability of creating custom reports, hence if looking for various views right from summary to detailed, this is a great tool. It is less appropriate for implementing the processes as it is not very strong in BPMN.

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.

Incentivized

• Query feature is excellent to extract information in a specific manner.
• Ability to create custom reports.
• Collaboration feature is very good.
• Semantic checks to check validation errors.
• cloud based central repository.

Incentivized

• 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.

Incentivized

• Defining databases, use of entities and relationship diagrams, define data, like data models, there is still a part they could improve.
• Providing more standard reports and improving on access rights and privileges functionality

Incentivized

• 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.

Incentivized

I am a BPM and Enterprise Architect Consultant and hence have been using different BPM and EA tools for consulting practice. Until now I have used Opentext Provision EA,Sparx EA, MS Visio and IBM Blueworks. All of the tools used are good and have their own unique features and capabilities. ARIS BPA is widely used by my current organization for different projects.

Incentivized

It has good, even complex functionality that is provided by its library and ability to create relations between items, yet it is not hard to use. Anyone can use it in a short time. It provides reporting abilities and good documentation with the availability of exporting options. The only drawback I have seen was user management/login issues.

Incentivized

The Service area, they have been very useful. ARIS suite is covering number of applications. ARIS engine is very powerful and robust. The tool can be configured in many ways which can be beneficial but can be a curse at the same time. As a user, you need to apply this flexibility with care.

Incentivized

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.

Incentivized

• Documentation of processes made it possible for anyone to see who does what, how and using what systems.
• Dependency on specific people is eliminated.

Incentivized

• 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.

Incentivized