ARIS vs. webMethods Business Process Management Suite (BPMS)

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.

Where webMethods Business Process Management Suite (BPMS) is well suited is for any use case where there is a business process that can executed over a long period of time (days rather than seconds) and that traverses multiple business applications and/or multiple lines of business and requires manual input from end users to approve or action specific steps. It is not well-suited for any business processes that can be distilled into a traditional integration solution between business applications that does not involve manual end user input, these types of uses cases will execute more efficiently on a traditional integration broker or enterprise service bus style solution.

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

• Great process design user interface and usability
• Excellent tools for monitoring processes at runtime
• Business rules can be managed and updated by non-technical resources

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

• Pricing is opaque and higher than we'd like
• Some of the user interfaces are outdated and looking their age
• Require buy in from business to achieve return on investment

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

We found webMethods Business Process Management Suite (BPMS) to be the most feature complete product in the BPM market when we evaluated it against other products available in the market. It provides the most features, the easiest to use process design and simulation tools, and the most efficient runtime process and rules engine. Just be aware that its pricing reflects this position in the market, but you get what you pay for.

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

• Initial adoption of BPMS was slow and required buy in from the business, which was only achieved through upper management buy in applying KPIs down the line
• Once a critical mass of business processes being automated with BPMS is reached, any processes that remain manual will stand out like a sore thumb and the business will be invested to automate those remaining processes too, so adoption of BPMS is like a slow snowball effect
• Not requiring technical resources such as developer to design and build out processes is a pipe dream and impossible to realise. You will always need experts in the automation tools you apply in your organisation, and webMethods BPMS is no exception

Incentivized