ARIS vs. Hyland RPA

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.

Hyland RPA is well suited for highly repetitive manual processes. It works really well with more modern web applications. It is more difficult to work with older client-server applications where fields, buttons, and links may be harder to identify, but with time and experience using the tools, most problems can be resolved.

• 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

• Configurability
• Transparency
• Ease of Implementation

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

• Lack of dedicated support
• Documentation
• Training

Incentivized

Our teams are now completely dependent on this solution and we've restructured our teams around the new processes we now have in place. It would be extremely difficult to be able to move forward without this product. We are more likely to buy more RPA bots than not renew at this point in time

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

Both RPA Analyst and RPA Designer are easy to learn and with experience almost any manual process can be automated. Once, the infrastructure is understood any organization should be able easily scale up it's automation efforts across multiple departments.

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

Hyland has been very responsive to our support tickets. They have consistently responded within their SLA.

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

Hyland RPA [(formerly AM Ensemble)] is much easier to configure and is fully integrated with Hyland. We probably would have used Selenium to accomplish what we were looking for but that required development resources and we were going to have to build in the integrations with Hyland and OnBase manually. This was useable out of the box and saved on development time

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

• Reduced the need to hire additional staff
• 90-100% coverage of contract settling
• Reducing errors

Incentivized