I cannot provide feedback on my current use of ARIS Architect and Designer because I need to discuss with my boss, as she requested consultation before providing feedback. For now, there is nothing that I see as room for improvement in ARIS Architect and Designer. We are already recommending ARIS Architect and Designer to other users. When we have consultants coming in to work on process development, we ask them to partner with Software AG to work on process development through ARIS Architect and Designer. I would rate the solution overall a ten out of ten.
I would rate ARIS Architect and Designer nine out of ten, but due to customer service issues and data reliability concerns, I advised my customer to opt for another tool in recent projects. My overall rating for this solution is nine.
We have started to adopt AI slowly. I use it for architectural modeling. There are many tools available for this purpose. It's best to try several, evaluate them, and choose the one that suits your needs. Each tool has its pros and cons.
Overall, I would rate it a nine out of ten because it's the most mature tool. The other models, like Risk Management, are more recent. These core modules are very stable. Benefits of ARIS method: Users have the methodology; it is called ARIS Method. Sometimes, it's not easy to convince customers to use this methodology because it's a bit rigid, but in a good sense. When people design processes or other artifacts using tools like VISIO, they tend to do things quickly and prefer free design approach. This is good for them in the short term, but in the long term, they might create a confusing mess. That's why it's important to have a method from the beginning, and everyone should follow it. But convincing customers to use a method is not easy. Real-world examples: Normally, when designing a process, we use three or four levels of detail, starting with value-added chains and going deeper until the operational business level. Sometimes, we even go into greater detail, like when users interact with systems. This is called a "work instruction" or "procedure." It's important to know what we're designing at the top level and what we'll design at other levels because each level has its own concepts. Sometimes, it's not easy to convince customers to use this because it requires training and practice. Many people think they can just start doing things without any methodology or organization, but that's not good. For example, I started a project almost three years ago, and it was really difficult to convince the customer to use the methodology. They wanted to start without any methods and free design, but a few months later, they realized it was a nightmare. Nobody understood each other. I tried to convince them to use the methodology because it benefits everyone.
The solution is not suitable for small enterprises. It is a good choice if someone is looking for scalability and many users. It will be very expensive if we have a small amount of users. Overall, I rate the product a six out of ten.
Senior Consultant at a consultancy with 11-50 employees
Consultant
Nov 27, 2023
The product is a bit sophisticated. It needs a bit of hands-on experience to use it. It's a good tool, but it's worthless if we don't know how to use it. Overall, I rate the solution a seven to eight out of ten.
Head of Enterprise Architecture and Process Management at a financial services firm with 501-1,000 employees
Real User
Dec 14, 2021
I would rate ARIS Architect nine out of 10. The solution has gotten better in the last year. I was thinking about deducting a point because it is not easy to find someone in person through remote connections. You need to do everything via email, and it isn't easy to explain everything over email. Of course, I understand they need the basics, but sometimes it isn't too easy to connect to the system and see what's going on. Regarding the visibility and control that ARIS provides of processes throughout our organization, overall, I would say we have "half control." We have control of the processes but not which ones are executed. We only have control of the processes on paper. Of course, the audits go through the documented processes, but we also want to have control of the processes. When it comes to execution, we need to have different models of ARIS. My advice to prospective ARIS users is to first decide what to do with business processes and then buy a tool like ARIS. It's a potent tool, but it is too expensive if you only want to document your processes. It wouldn't improve the case itself, but if you want to do some real analysis of the processes, I think it is one of the best tools in the market. It provides you with a full view of the processes so you can document them. You can monitor them and improve them through simulation. So, this is a full cycle. It is powerful with different modules, but first, you need to convince yourself that you need a real process analysis.
Assistant Manager at a consultancy with 10,001+ employees
Real User
Nov 19, 2021
In my company, there are around 500 people working with Architect and around 1,000 working with Designer. I recommend this product for bigger clients. If your organization is only looking for modeling or one piece of BPM, then don't go for ARIS because you have other simplified tools. But if you are looking to fully implement a BPM cycle—starting from process discovery, modeling to monitoring, simulation, mining, everything, the full BPM suite—then go for ARIS. This is what I mean when I say bigger clients. If your project is small, don't choose ARIS. I would rate ARIS Architect and Designer an eight out of ten.
Process specialist at a financial services firm with 1,001-5,000 employees
Real User
Nov 3, 2020
I would definitely recommend ARIS. On a scale from one to ten, I would give ARIS a rating of eight. If they added a collaboration feature, I would give it a ten.
ARIS Architect and Designer offers customizable process visualization and collaboration tools designed for efficient enterprise architecture management, emphasizing compliance, governance, and strategic planning.Organizations use ARIS Architect and Designer for creating central repositories, process modeling, enterprise architecture, and business process design. Its strengths include extensive customization, process visualization, and robust model libraries. Users benefit from metadata...
The reviewer is a consultant at KAFD. We would give ARIS Architect and Designer an overall review rating of ten out of ten.
I cannot provide feedback on my current use of ARIS Architect and Designer because I need to discuss with my boss, as she requested consultation before providing feedback. For now, there is nothing that I see as room for improvement in ARIS Architect and Designer. We are already recommending ARIS Architect and Designer to other users. When we have consultants coming in to work on process development, we ask them to partner with Software AG to work on process development through ARIS Architect and Designer. I would rate the solution overall a ten out of ten.
I would rate ARIS Architect and Designer nine out of ten, but due to customer service issues and data reliability concerns, I advised my customer to opt for another tool in recent projects. My overall rating for this solution is nine.
We have started to adopt AI slowly. I use it for architectural modeling. There are many tools available for this purpose. It's best to try several, evaluate them, and choose the one that suits your needs. Each tool has its pros and cons.
Overall, I would rate it a nine out of ten because it's the most mature tool. The other models, like Risk Management, are more recent. These core modules are very stable. Benefits of ARIS method: Users have the methodology; it is called ARIS Method. Sometimes, it's not easy to convince customers to use this methodology because it's a bit rigid, but in a good sense. When people design processes or other artifacts using tools like VISIO, they tend to do things quickly and prefer free design approach. This is good for them in the short term, but in the long term, they might create a confusing mess. That's why it's important to have a method from the beginning, and everyone should follow it. But convincing customers to use a method is not easy. Real-world examples: Normally, when designing a process, we use three or four levels of detail, starting with value-added chains and going deeper until the operational business level. Sometimes, we even go into greater detail, like when users interact with systems. This is called a "work instruction" or "procedure." It's important to know what we're designing at the top level and what we'll design at other levels because each level has its own concepts. Sometimes, it's not easy to convince customers to use this because it requires training and practice. Many people think they can just start doing things without any methodology or organization, but that's not good. For example, I started a project almost three years ago, and it was really difficult to convince the customer to use the methodology. They wanted to start without any methods and free design, but a few months later, they realized it was a nightmare. Nobody understood each other. I tried to convince them to use the methodology because it benefits everyone.
The solution is not suitable for small enterprises. It is a good choice if someone is looking for scalability and many users. It will be very expensive if we have a small amount of users. Overall, I rate the product a six out of ten.
The product is a bit sophisticated. It needs a bit of hands-on experience to use it. It's a good tool, but it's worthless if we don't know how to use it. Overall, I rate the solution a seven to eight out of ten.
The solution's performance is good and I would rate it a seven out of ten.
I would rate ARIS Architect nine out of 10. The solution has gotten better in the last year. I was thinking about deducting a point because it is not easy to find someone in person through remote connections. You need to do everything via email, and it isn't easy to explain everything over email. Of course, I understand they need the basics, but sometimes it isn't too easy to connect to the system and see what's going on. Regarding the visibility and control that ARIS provides of processes throughout our organization, overall, I would say we have "half control." We have control of the processes but not which ones are executed. We only have control of the processes on paper. Of course, the audits go through the documented processes, but we also want to have control of the processes. When it comes to execution, we need to have different models of ARIS. My advice to prospective ARIS users is to first decide what to do with business processes and then buy a tool like ARIS. It's a potent tool, but it is too expensive if you only want to document your processes. It wouldn't improve the case itself, but if you want to do some real analysis of the processes, I think it is one of the best tools in the market. It provides you with a full view of the processes so you can document them. You can monitor them and improve them through simulation. So, this is a full cycle. It is powerful with different modules, but first, you need to convince yourself that you need a real process analysis.
In my company, there are around 500 people working with Architect and around 1,000 working with Designer. I recommend this product for bigger clients. If your organization is only looking for modeling or one piece of BPM, then don't go for ARIS because you have other simplified tools. But if you are looking to fully implement a BPM cycle—starting from process discovery, modeling to monitoring, simulation, mining, everything, the full BPM suite—then go for ARIS. This is what I mean when I say bigger clients. If your project is small, don't choose ARIS. I would rate ARIS Architect and Designer an eight out of ten.
I would definitely recommend ARIS. On a scale from one to ten, I would give ARIS a rating of eight. If they added a collaboration feature, I would give it a ten.