ARIS BPA Reviews

We are trying to define our business processes with ARIS BPA. We're just beginning the project, so we can't assess all the current features. We are using ARIS on-prem, not ARIS Cloud.

We chose ARIS because of its good reputation and familiarity with Software AG Tools.

Improvement should be made as per customer requirements.

I have been using ARIS BPA for the past six months.

We haven't had any stability issues with ARIS BPA.

The support from ARIS has been complete and helpful. The vendor's contact center is quick and efficient; we can work well together.

Positive

We can easily deploy the application and process. It's user-friendly. It took about one month to deploy the application and design the process.

The vendor provided a consultant, which was helpful.

Pricing for ARIS BPA is average, not cheap or expensive. It's cost-effective and worth the money we pay.

We researched and compared other tools, including IBM, but ARIS fit our requirements better.

I don't use AI-driven processes with ARIS BPA yet because our metrics level is too low.

 It is an easily implementable solution, the design process is nice and easy, and it's quick to learn. I would recommend this tool to others.

Overall, I would rate this tool a nine out of ten. It's not a ten because no tool is perfect.

We use the platform for document automation and capture all the processes.

ARIS BPA has valuable reporting capabilities.

ARIS BPA's scripting language takes work to understand. Even a JavaScript developer has to learn the language to write the script. This particular area needs to be easier to understand.

The user interface could be more intuitive and better designed. There is a lot of unused space in the interface, which could be utilized. Additionally, the color needs to be changed to make it more user-friendly.

We have been using ARIS BPA for five to six months overall.

The product crashes sometimes. They could provide clearer documentation detailing the right GDPR releases for installation on laptops or desktops. This documentation should not just state a generic version like "JDK 11" but provide specific details, such as recommending a certified or tested JDK version like "GE 11.0.19. Given the frequent updates in JDK releases—such as those from Oracle and Java, occurring nearly every week—it becomes essential to specify the precise compatible version and any performance implications between 32-bit and 64-bit architectures. Additionally, aligning the development environment (potentially using JDK 17) with the executable's certification (such as JDK 11.0.19) is crucial for consistency and stability when users download and use the solution.

We have 20 ARIS BPA licenses in our organization. It is a nice software. I rate its scalability a nine out of ten.

We are also using an open-source VPN solution.

The initial setup is easy. We have deployed it on-premise and in the cloud. We are a large organization requiring an IT team to manage the installation. I rate the process a nine out of ten.

The product is inexpensive.

ARIS BPA's facilitate the visualization of change management during the development phase. We can extract the factory report directly. It is quite encouraging for the users. It has been in the best leadership position in Gartner since 2023.

I rate it a nine out of ten.

Over the years I have used ARIS in many ways depending on the project, and I have experience with many different versions of it. I've used versions seven, eight, and now ten. About ten years ago, I worked on developing ARIS and its standardization for six months.
When I first started using it, I used to build a center of excellence for a global project. We used it to document the expansion process of our company to the global market. There were a lot of Visio files and it was quite disorganized since anyone could edit the files however they would like. We tried to turn the Visio files into something more formal. For a year, we used a low-end tool to document the process. With ARIS, we documented around 2,000 processes. We used it to organize and create a publishment where people could find what they're looking for.

I like everything about ARIS BPA. I've used it for a long time and I think it's a fantastic tool. There is a list of things ARIS has that other solutions do not have.

The solution does not have an efficient way to track employees' work. It shows who worked on something last, but that overwrites the history of changes in a way. It is supposed to provide information on team activity, but it does not do that. The creators of the solution elaborated in great detail on quality control and thought about every possibility, but they didn't make that useful and simple to use. The overhead maintenance is good.

I have been using ARIS BPA since 2010. 

The solution is very scalable. A ten out of ten. There is nothing even remotely close to it on the market. 

ARIS BPA is an extremely stable solution.

ARIS' technical support team is great.

Positive

Many years ago, we used BusinessOptix at our company. 

The initial setup of ARIS BPA is simple. When we first started using it, it was deployed on-premises. The latest version was deployed on cloud and it only takes a few days. It promises to teach you how to do that, but that is not very helpful since your company's team and organization need to be suitable for this kind of complexity. It's web-based, but there are technical limits to what you can do with it. In a way, it encourages you to purchase more and more if you want to maximize its usability. It does not teach you how to use it and it's very formal. Although ARIS is a fantastic tool, it would be better if it was focused on the customer's success. It requires a lot of maintenance.

ARIS BPA is extremely expensive and the training time for it is extensive.

I had a hard time with ARIS' access and licensing policy. It requires you to pay for each step you want to take forward with the solution. To get the documentation, you need to be an administrator. If you want the license to read the documentation of the process, you need to be some kind of administrator/support account, but you will need to pay for the support. Even if I'm qualified they will not provide me with the documentation. Instead, they will ask you to print it out and send the request to them. I had to wait two months to get the account and six months to get the contract. All of that is extremely time-consuming.

I have seen how MEGA works and it is definitely more user-friendly than ARIS.

The requirements are extremely high and it takes a skilled professional to use it properly. Whether it's a big or a small company, it has to be used by someone who is familiar with its complexity. You should be aware before purchasing the solution that it is not simple to use and it takes time to learn. ARIS' free tool is much easier to use. I work in Germany, but I think they made ARIS less complex in other countries.

When it comes to ARIS BPA as a tool, I would rate it a solid ten out of ten. It's a fantastic tool, but it is not easy to achieve results with it. The chances of producing what is promised by the vendor are zero.

We use it for creating a structured record of our processes and for updating them. We also use it to analyze how strategic changes in our company may impact these processes. 

We work with the cloud solution. We don't have to have anything installed on our computers locally. We designed the processes and the framework ourselves.

With ARIS: 

• We now have a better view of how everybody works in our organization and it helps us to see that everybody is doing the work they should be doing.
• We have more standardization, compared to when we first started, when it comes to describing processes. When we started, we saw that different people in the same unit, who should be doing the same work, performed their work in different ways. ARIS enabled us to achieve more alignment there.
• The solution also makes it easier to solve problems, and similarly helps when there is a strategy change or a new product. It's easier for us to pinpoint where the differences will be, compared to the current way things are done. It helps us respond more quickly to things we change in the organization.

The last point helps us to identify where we have to focus when things change. There are no surprises. We know what our processes are now and, if we know where we are heading with the changes, we can use ARIS to see where the changes need to be made. It helps us to speed up the rollout of transformation processes.

It has also definitely helped us to save time on business process analysis. It's now easier to find processes. We have them clearly described and we don't have to work through a pile of Word or PowerPoint documents. We just go to ARIS and we can search and navigate in the system. It's easier to access things. We are now doing more work with the same number of people, without these people having too much on their plates. We're more efficient and we all benefit from each others' best ways of working.

A basic feature that most other tools like ARIS BPA have as well, is a database with all of the relationships in the system. It makes it easier to have more standardized processes across the organization. The database also makes it possible to run reports and do analysis, which is kind of cool.

What also makes it good is the way we have set it up so that we not only have the processes in place, but we also have relationships specified with our IT systems and our organizational chart. That makes it possible to analyze things from the systems point of view and regarding the organizational part of the company. It all comes together in one tool and that is what gives us the most value at the moment.

We use the modeling technique called BPMN, which is a standard way of describing processes. It's independent of ARIS, but ARIS facilitates working with it. All the objects are available in ARIS, which makes it quite intuitive. For me, ARIS BPM is easy to use because I have known it for quite a long time. Others need some training before they can use it properly. They need a basic understanding of how the tool works. But overall, the intuitiveness of the solution is quite good.

Also, access to the solution is good because it's a cloud solution, and the performance is quite good. It's well-organized.

There are reports available in ARIS and you can modify them a bit if you want something more specific, but it's not that easy to adjust them and make modifications. It would be nice to have some kind of tool to do that, something that is more user-friendly for people who are not too technical, so that they could create reports the way they want them. That would be a good feature. That would also help in the adoption of ARIS.

At this company, I have been using ARIS BPA for a year and a half, but I'm quite experienced in using the tool, having used it for about 10 years.

The stability of the solution is quite good. I haven't had any issues with it. Maybe years ago it was less stable, but it's quite stable now.

We don't have that many users, so it perfectly suits our company. ARIS enables you to start small and grow the use of the solution over time, although it's quite expensive. So if you want to start small, it's quite an investment for a small company. But it's perfectly suitable for growing.

I am the administrator of the solution and we only have a subscription for 10 other users and two other designers.

We have used it very extensively over the last 18 months, but due to our strategy for growth, which is a little bit different, and because of what the pandemic has caused, we are not really growing the process area. We may have even turned it down a bit. That's a shame, but we have to focus on other parts of the organization at the moment.

The technical support is quite good. I have had a few interactions with them by email. There are formalities to the process. I have to put my issues in a certain format and then they will respond. 

It might be easier if I could have direct contact, just easily pick up the phone or chat or just write a quick email, so that we could find a solution. There might be some room for improvement there.

Positive

When I started here, we didn't have anything other than descriptions of processes in Word on PCs around the organization. We wanted to have that available in a more structured way.

I have a good deal of experience in setting up an ARIS environment, so I knew quite well what I needed to do. For me, it's not really that complex. We set it up for our needs.

We had it ready within one month, approximately. It's quite important to think about what you want to have, which areas you want to touch, and what you want the results to be. 

It's important to take some time to do a good implementation of the tool. Our implementation strategy involved investigating, defining, and describing what we wanted to have; what we wanted to describe with the tool, and what benefit we wanted from the tool. In that way, we could set it up, from the start, in a way that we wouldn't have to rework it in a few months or a few years. It's better to take some more time to set it up well than to start in with it directly and then see, in a few months, that you're missing some parts.

I created a framework in which we could capture all of the processes across the organization, from IT to delivery to logistics to HR and finance. Gradually, we have been filling it. We have defined five layers of detail. I interview people who are working with the various processes in the field, and I try to describe them as they are right now. When there are changes within our organization, when we have a new product or we have a new strategy, we also look at the processes and see where these changes will impact them. Based on where the impact might be, we can more easily pinpoint what we need to do when adopting a new strategy or a new product.

There is not that much work involved in maintenance of the solution. The maintenance of the content, on the other hand, depends on the business you're in. For us, it's our day-to-day work, making sure that all the processes are in place and correct. But the maintenance of the tool itself, the more technical part, does not require that much work, about half a day per week.

I did it myself. Because of my experience, I didn't need other people to help me with it.

The ROI depends, for our company, on how big we grow. The intention is to grow and we need a tool in place, like ARIS, to make our growth happen. We have to be in control and we need an overview and insights. If we can achieve the growth we're thinking about, the return on investment should take a few years.

In the future, ARIS might help us save on development costs associated with business process transformation. At the moment, we just describe the business processes without going too much into detail regarding the technical IT solutions. That connection is there, but not too extensive at the moment. But if we improve that part, we will definitely see some cost savings there.

If you want customized reports in place and you cannot create them yourself, you have to get them done externally, so that would be an extra cost.

We briefly looked around at what was in the market, but with my past experience with ARIS, the choice was quickly made to use this tool. It might be a bit more expensive, but it has a lot of possibilities, so we didn't spend very long searching for other tools.

If you start working with ARIS, first investigate very well what you want to achieve. You can use it for different kinds of goals. You need to know what you have and what you want to achieve. Then you have to create a setup. So the requirements are quite important to the design, before you start working with the tool. That's the most important thing you need to do.

The tool functions quite well and you can put every process in it, but it's also important to look at your organization and make sure that people are willing to work with processes. That means you have to do some educating, in addition to the technical solution ARIS provides. Be sure that all the management positions participate in describing their processes and that managers encourage their teams to work in and use ARIS, and to do their work in the way things are described. There are these kinds of change-management issues to be aware of.

The fact that ARIS has the largest BPM community worldwide is not that important to me, because I don't use it very much. I only use it to pose some technical questions. I have used some other frameworks, such as the eTOM APQC Frameworks. So I generally get my knowledge from other sources, rather than from the ARIS community.

When I came into the company, I immediately started to implement ARIS, so I don't have a clear view of how things were done before. But everybody in our organization is more and more aware that we should use ARIS and that we are benefiting from it, although I can't clearly define the benefit compared to how things used to be.

I'm very happy with the ARIS solution. The ARIS Advanced product we have would work quite well for most of the companies. A very big company, like a multinational, might want to have something that is on-premises, and to customize it a little bit, but for most companies, what we have is good enough.

We use the solution to collect information, design, publish, and validate the process. We can implement the process according to the improvements that can be retrieved. We monitor the process before the four phases of discovery, design, publishing, and implementation.

BPA is used to represent reality. We need to find and implement potential improvements from a workshop presentation and then monitor the results. We are not implementing these tools to plan and organize artifacts. This tool covers everything except implementation because that is not the purpose of a BPA tool. However, this tool can interface with implementation tools, and after implementation, you can use APIs and other interfaces to get information back from reality. In terms of improvement, the app could use some small details and functionalities. However, I need more time to sync to get more specific suggestions. We already have interfaces for these four tools, and it is possible to develop interfaces for the other four tools. 

Inside the product, we can have a developer environment where we can create new scripts using APIs or STPI. This is the environment that we use to help interface the tools. In the past, we had many packages of interfaces. The suppliers of the provider preferred to have these package interfaces. We like to open the code, at least part of the code, with APIs and other things like this so that the consultants can create the interfaces with the specific tools. We use APIs and other search tools for this.

I have been using ARIS BPA for more than 30 years.

The technical support is good.

Positive

The product is expensive. People who don't understand BPA or only understand a little bit about it often compare tools with videos and things like this, which are not comparable. They may have a lot of models and artifacts, but nothing is aligned or consistent. Customers prefer to start with fizzes and things like this, and later on, they come back and prefer to use a more professional tool.

The solution is not easy to use. People at the operational level don't have the abstraction level needed for this proposal. When they get information from business people, they immediately decide on the other model. They come with additional information from other business departments and do the same. To do things properly, you need to think about a proper structure based on components. Then, when you get new information from previous areas, for example, IT, you should frame this further information or these recent changes in the structure you previously found. Otherwise, you're constantly reacting, doing a lot of ad hoc models. You'll have a lot of content without alignment, sense, or semantics. 

The first step is to contact the customer. The next step is to present the customer with some proposals because when you present the proposal to them, they may accept or reject it. If they leave it, what will you do? This flexibility allows you to generate different views of the process for different stakeholders. For example, someone in top management might want to see a view from the customer contact until the proposal. Another person might want to see everything. You can take all of the components that you have designed before and create a specific view for them. It’s only about how to design business processes. It depends on the other two. One of the primary and critical requirements is to create business processes based on specific components that are well-linked and aligned together, in order to avoid ad hoc models. Ad hoc models are not very good. They do not work in the future. Usually, people start doing this because it is easier. This is closer to how ordinary people think. 

Still, in the middle and long term, you will realize that it is not manageable because you have to prepare models, a visualization of things, and different models of the same reality. You will not know what the source of truth is at a certain point in time because you have many different presentations of the same fact. For me, this structure is crucial. This is where it should start: defining the system, how you will model it, and the methodology. What are the pros and cons of the method? How will you capture, model, validate, implement, and monitor the information? You must define this beforehand, at the beginning of any project. Otherwise, forget about it, regardless of your tool, because it is more about the concepts. If you don't have the right concepts, then forget about it. Overall, I rate the solution an eight out of ten.

We are modeling different processes and documenting all of them using the solution.

It's a really nice and user-friendly tool, and we can extract different reports from it. We have had different processes modeling and everything done with the solution. With the solution, we were using it for documenting, and then now we are updating all of these. So it's been great software for everyone.

We would have appreciated it if the company who has sold the software could show us how we can create our own reports, apart from showing us how to extract different SOPs and run our own scripts. So that would have been helpful for us.

An area where it lacks and can be considered for improvement in the future is if we can somehow automate or learn how we can automate different processes. So, it's like The processes in which we initiate a request, and we can follow where the request is and how the workflow management is being done in different software. So if you can somehow learn how we can do it, it will be great.

I have been using ARIS BPA for two years. I am a user of the solution. I don't remember the version.

It is a scalable solution. Scalability-wise, I rate the solution a ten out of ten.

It is a scalable solution. Scalability-wise, I rate the solution a nine to ten out of ten.

My designers are very few in number, but there are a lot of users. Also, we have a lot of viewers. We have around 10 designers and more than 2,000 viewers. We frequently use the solution in our company.

The support for the solution is good. I rate the support a ten out of ten.

Positive

Previously, I used Microsoft Visio for process mapping.

The solution is easy to install. It wasn't hours but maybe days to do the deployment, but it was done swiftly. It wasn't an issue.

I don't remember how many days it took to deploy. But currently, we have multiple designer licenses. So now the deployment doesn't take long. We can use it. Also, I wasn't involved in the installation process.

If we get stuck with the installation part, we request the provider company to let us know how to proceed.

I can't speak about pricing because I was not involved during the installation days.

It's a great system for viewing, modeling, and everything, extracting different kinds of reports. So the only thing is that the users must understand how different reports can be extracted. What are the different attributes or the fields, what is their purpose, and learn how analysis can be done. So we need to do the aforementioned things, and overall it is great software.

On a scale from one to ten, one is worse, and ten is the best, I rate the overall solution a ten.

Our customers have generators on their facilities, and we manage those generators to provide services to the grid and reduce their costs. It involves peak shaving and that sort of stuff. We use ARIS BPM to essentially automate the communication to the grid and the generator and then update all of the account information regarding those transactions.

The ease of use is the most valuable. I have tried a number of BPMN packages, and I find the user interface of ARIS BPM easier and more intuitive than others. If your team is knowledgeable on BPMN, it is really pretty easy to figure out on your own because it adheres to the standards extremely well. I have tried Bizagi, BizFlow, and a variety of such solutions, and I just liked ARIS BPM better.

I use it strictly for developing the business process model. I don't use it for the actual automation. I do that with Vtenext. I have standardized on Vtenext, and I don't use ARIS BPM anymore. The Vtenext UI is just as good, and it is much more tightly coupled to the underlying object model. I can get more done in one session with Vtenext rather than first going to ARIS BPM, then importing, and having to edit it for tight coupling.

I have been using ARIS BPM off and on for six months.

I would not comment on this because we use it primarily just for the business process modeling and not the automation. So, I really can't comment on scaling. We have four users who are using this solution.

We never contacted them. Its user interface is good and pretty intuitive. 

The initial setup was straightforward.

We implemented it through an in-house team.

I would recommend ARIS BPM depending upon the use case. I would generally recommend Vtenext first. I found Vtenext on GitHub as I was looking through and trying out lots of BPMN and BPA stuff. I used their product, and it is a really good product. We've now partnered with them.

I would rate ARIS BPM an eight out of ten.

The whole ARIS BPM solution is a bit special, because from the very beginning it was targeted more to Business users and the Management. Its core focus was to, at the end provide a neat tool for the Management to use as get a grasp about their Business Processes, more easily determine their strategy and also sometimes do analysis and parametrization of the processes. This is all possible, as ARIS, unlike Visio for example utilizes a database system, where it's possible to model all kinds of relations with different metadata and information. If used with clear strategy, it can provide a really powerful tool to analyze the whole Enterprise, from IT, Processes and Organization.

It has improved the organization where I work currently, in a way that the processes are more transparent, then before when they were present only in documents.
Advanced modeling, structuring and visualization capabilities of ARIS made this possible.

The main "drawback" of ARIS is that it is not targeted towards the real implementation and running of certain business processes.
It does not have a real workflow engine beneath that can make things actually run. This is also due to it's different focus from the beginning. And also, this comment might be a bit subjective, as I'm more interested in this technical aspect of a BPM system.
Some improvements have been done, after Software AG acquired ARIS, but I don't believe it's still integrated with the other tool WebMethods in a perfect way.
Also, ARIS can be very hard and costly to integrate with other tools, as there is no programming API or web services exposed, except from the integrated report API which is targeted to be used for creating reports from the ARIS database. It's not targeted towards integration.

I've used the solution for more than 6-7 years, in different scenarios. Starting as a consultant implementing the solution and modeling the processes, but also as a Business & IT analyst barely using it as a common user to facilitate my work.

No. The standard system is usually very straight forward to deploy.

ARIS Business Server and the modeling tools are pretty stable in general. Some issues and challenges can occur when using it in an extremely large environment when the Business Publisher needs to serve more than 5,000 users. Then the load balancing comes in to play, and it needs some improvement in the Publisher tool.

It's probably one of the most scalable solutions in the market currently.

The effort in changing the whole architecture in versions 9 and 10 to enable this is tremendous.

The technical support is very good, and has extremely improved over the years.

ARIS is a very simple tool to set up if you are using just the basic platform: Business Server and the Designer tools. In case you are going for a more advanced approach, with additional modules, the solution can be quite expensive to set up. As the vendor consultants are not very cheap, :)

Basically, the main point is to be very clear about your expectations and why do you want to use the tool. If your focus is primarily on the business users, and making company wide business process mapping and improvement initiatives, that's pretty much where ARIS is really good. But, if your focus is the implementation of the business processes, integration with other systems, you should probably evaluate other tools, like Webmethods, IBM BPM, Bonita, Bizagi, Pega,etc.