ARIS BPA Reviews

We have three main use cases. One is process management and the second is ICS (internal control system). Our third use case is very important for us: to evaluate the operational risk situation of our company, not only of the company itself but of the whole group. It was one of our requirements to find a system that could, on the one hand, evaluate risks for each company in the group, and on the other hand, conglomerate these risk situations for the whole group.

We use ARIS Risk & Compliance Manager (ARCM) for our ICS. There are different people who have to evaluate the risks and actualize the processes. We have a workflow implemented so that there is a reminder for the people who have to evaluate the risks and the controls, once a year. We also have a workflow for the process owners to assign a process model.

For our ICS, we used to have an Excel- and Word-based solution. It was very complicated and it was not really digital. Now, it's very simple for the people who have to evaluate the risks. They get a reminder from Outlook that a certain risk needs to be evaluated and they can evaluate it and send it to the risk owner. It's a more digital process and has improved things.

With our ICS we didn't have control of the controls, and this is something we are now working on. It is very easy in ARIS to model it and evaluate it. This was something we learned about and a capability we didn't have before.

The browser-based modeling tool is very awesome. It's very easy for the people who use it. One of our aims was and is to use ARIS in a decentralized way. That means we want our business departments to be able to publish their processes and to evaluate risk and controls. For that purpose, we have ARIS BPA and ARCM, which are connected. We model the risks and controls on the process diagrams, and the evaluation of risks and controls take place in ARCM.

ARIS BPA provides very good visibility and control of processes because we have a concurrent license system. As a result, every person in our company and group is able to look at the published processes. We have also built a tree from a process map so that people can navigate through different steps to the process model itself. That works quite well.

The intuitiveness of ARIS when it comes to business process management and modeling is not quite there. We have invested a lot of time and money in building a very usable system. The modeling part is very intuitive, but there are so many possible elements you can use. We had to invest a lot of time to reduce the elements to those we want people to use. If you take all the elements and all the modeling types that ARIS has, it is not possible to model in an equal way.

Also, we are part of a community that has one or two events per year where we can talk about our experiences with the solution. From these meetings, my impression is that a lot of customers do not use the current release. Migration to the next release is very tricky. You can't do it without support from ARIS or from a software kit. And it takes a lot of time and a lot of money to migrate. My impression is that a lot of companies do not migrate regularly because of that issue. There are always a lot of bugs, especially when you adapt the system to your needs. It's very complicated.

We have been using ARIS BPA since 2020.

The stability has been okay. We haven't had any interruptions so far and the concurrent license model works very well. We have enough licenses that people don't have any problem getting into the system.

The scalability is good because it is a modular system, and that was another factor in our decision to go with ARIS. You can buy additional modules to adapt it to your needs.

The solution enables you to start small and grow its use.

For small problems, their tech support is okay. 

For larger problems, it's more complicated to explain to their tech support what we really need. Our experience has been that it's better to buy two or three consultant-days with the consultant who knows our system, because he developed it together with us. He can identify problems very easily. With the regular tech support it takes a long time to explain what the problem is.

Neutral

Casewise – EA & BPM was the system we had before. It was a system that wasn't fit for our decentralization goals because it was very complicated. There were a few specialists in our company who could work with Casewise, but it was really a system for specialists and not for business departments.

The initial setup was complex. Ours is a complicated environment and we had complex requirements. But we had really good trainers from Software AG. They have a lot of knowledge and they were able to help adapt the solution to our needs. But it was a very long process to get the system to where we wanted it to be. It took about a year for the implementation.

We have done two migrations since we deployed the solution. One migration was during the implementation phase, and the second is being done now. As I said, the migrations are very complicated.

We looked at Signavio, in addition to Casewise, among the solutions we looked at in an intensive way.

Signavio was okay, but it didn't fit our needs when it came to risk management, and their licensing system also didn't fit our requirements.

We deployed the solution on-premises because our IT security team is very strict. We don't have any cloud solutions so far. This was one of the topics that influenced our decision to go with ARIS. Other solutions prefer the cloud or develop cloud products in a more efficient way. Our aim was to have a product that works on-premises.

We do not have a lot of experience because we implemented process management, as a strategy, in 2019. Before that, processes were not really the focus of the business departments. IT had processes in mind, of course, but they only used drawing tools that were not management tools. There is now more awareness of process management in our company, not only in IT but in the business departments as well. Still, at the moment, people see it as additional work, but I hope that will get better.

I have been working with ARIS across different projects in several companies, including a project where we implemented ARIS.

In my current company, we use ARIS for business process mapping, capability management, and process analysis. In some of my previous jobs, we used it as a tool for quality and compliance management, because processes are obviously the basis for audits. In this respect, ARIS always came in very handy.

It is pretty easy for users to get access to published processes. With regards to published content, I can think of one or two enhancements but overall, it's pretty easy. When you know how you need to do it, then it's a good tool.

ARIS has the largest BPM community in the world, although I don't particularly care about the size. The important part is how active it is. For example, if you have 1,000 people that form a community but nobody is saying a word, then the community is useless.

Software AG is promoting the ARIS community quite heavily, and they may have started to rebuild it with this platform. People tend to use it more frequently and I personally try to contribute to the content. Essentially, for me, the engagement of the community is more important than its size.

As a process management tool, it provides a lot of transparency when it comes to processes. This means that people have a solid basis for discussion and this is important because only when you have a process mapped, people will understand how it works. Sometimes, they will then even say that they have understood the process to be something totally different.

In general, process mapping using ARIS is a really good basis to get discussions going and also for audits to ensure or to prove to the auditor that you have good processes in place.

My gut feeling is that ARIS helps to save us time on business process analysis. However, it is difficult to confirm because we wouldn't be able to measure that. It certainly helps to create transparency when it comes to processes, and thus automatically increases their effectiveness. This suggests that it saves time.

ARIS is very user-friendly compared to other BPM tools that I have used. The user has a really modern view when they're using the ARIS Connect platform, which is the web-based part of the application.

In general, the users really like it and they can get started using it very easily.

For some people, ARIS is quite intuitive when it comes to business process management and modeling. In the time that I have spent training people, I have found that there are two mindsets. If somebody is a very organized and structured person then it will be relatively easy to get started with ARIS. However, if somebody is more creative then it tends to be quite difficult for them. That said, these people would have the same difficulty when using other process management tools. The reason is that process management is about structure. For those with that type of mindset, it's really easy to get started.

As an administrator with several years of experience with ARIS, I find that getting end-users set up is a really easy thing to do.

I really like the large variety of functionality that ARIS provides. If you look at it from a methodology perspective, you have more than 100 different diagrams or model types that you can choose from. It's really flexible in all of your modeling needs.

You can easily model process diagrams, but you can also model bowtie diagrams, UML diagrams, and more. ARIS has a really wide range of functionality. 

I really like the EPC modeling because it allows you to model not only the doer's perspective, which is often done with BPMN notation, but it also allows you to model the contributors or the people who are accountable or informed in your processes. When it comes to manual processes or semi automatic processes, this is really useful because this is where you can improve a lot.

The Risk and Compliance Management tool is rather complex. So, we customized it. Customization was done by SAG and was done fast.

The facility for sharing content should be enhanced. For example, it would be nice if you could share content with viewers who do not explicitly have access to the model. As it is now, if you share a process with somebody that does not have access to the model, then the person receives a link that simply tells them they have no access.

Particularly, when you're in the process of modeling something and you want to share it because you want to get feedback from your colleagues, I would appreciate being able to share that content. It could be valid for a period, such as 24 hours or one week. This is something that would help.

I have been using ARIS since 2009. This has been in various positions in different companies.

Stability has increased a lot since I began working with it. I remember in one of the earlier versions, perhaps version 7 or version 9, there was a lot of trouble. We would run into unexpected errors, some of which were quite severe. Since then, however, there have been some errors, but it's pretty much stable.

There are different roles depending on the employee. We have regular employees who can read or view content. They can also comment on it. We also have employees, such as team leads, with modeling privileges. There is a big variety in terms of the different roles that people have.

We have approximately 130 modelers that use ARIS. When I run training sessions, I shift licenses from one person to another.

I don't have much experience with scaling but for our current use cases, it is sufficient.

ARIS definitely enables you to start small and increase usage over time. This is very important to us because it requires you to have a process-driven mindset in the company. This mindset becomes part of the organizational culture, and culture is something that evolves over time. Importantly, developing the proper mindset is a journey so you need to start small and then grow, otherwise, it will not really work. That's the nature of cultural development.

Generally, as process management is something that evolves over time, we expect our usage of ARIS to grow. Some people are early adopters but for others, it happens a bit later. Right now, the speed is increasing when it comes to the adoption of process management, which means that more people are using ARIS and have been requesting modeler licenses. This is something that is quite good.

I really like the support and I would rate them an A+.

Their response times are really good. Whenever I have a question, I get an answer, or at least I know that somebody is taking care of my ticket really quickly.

They do not close tickets without asking, which I appreciate a lot. So, from time to time, I've received an email notification asking, "Hey, can we close this ticket? Did we answer your question sufficiently?" This is also something that I value a lot.

Support also asks for feedback. The head of the global support team has also checked with me whether I had any ideas for improvements. The fact that they are always seeking to become better is another thing that I really like.

Neutral

I have some experience with other BPM tools but nothing as extensively as ARIS.

One of these is Signavio, and the ARIS interface is more user-friendly. Also, when I tested Signavio a few years back, they did not have as wide a range of functionality available.

From an implementation perspective, it was rather straightforward.

My colleagues at my previous company found the technical installation documentation really difficult.

As an end-user and ARIS administrator, I knew what the different steps were in order for people to start using it. From this perspective, I found it really easy.

Leaving the technical aspect aside, because it took our IT department quite a long time to deploy it, I was able to complete my part of the implementation in less than a week.

Their license model is really difficult to understand, and licenses are quite expensive. However, with the new subscription model, it's fair that you can rent licenses for a specific time and then give them back. From that perspective, it's okay.

In general, the licensing model is not clear and the complexity is growing. In the past, I was not able to get information whether new functionalities are available for us. This situation has been communicated and should improve: For me as an administrator it is annoying when people ask me about new features and functionalities, and I tell them what is coming, only to later find out that the feature is not available for us. After some discussions you find out that you need a license. This has happened to me two or three times and it is really embarrassing.

In our test environment, we use version 16 of ARIS. However, in our production environment, we use version 15.

We are currently doing a proof of concept project for the ARIS Risk and Compliance Manager. I believe the ARIS GRC has some potential, although it's a rather complex tool, which you definitely need to customize if you want to use it. It offers so many functions and functionalities that if you haven't had a real profound training of it, you will not really understand. So, at least in the beginning, you need to reduce the complexity of the tool. This is the approach that we took with the proof of concept project.

To this point, we have not used the ARIS process mining capabilities ourselves- but did a proof of concept with SAG. The support we received was really great. We haven't used the RPA functionality (yet). We are in the pre-project implementation phase of the AI-enabled translation services.

My advice for anybody who is implementing ARIS is that from a tool perspective, limit the functionality for the end-users. I strongly recommend using filters and to start small. Only allow limited functionality and a few attributes because the more complex a system you start with, the more difficult it is for a user to really understand how it is supposed to work.

That said, if anybody does have problems then I recommend contacting support. I've never experienced a situation where support was not willing or was not able to help. To assist them, it may seem like a standard practice but I suggest adding screenshots because it facilitates communication with them.

New users should also contribute to the ARIS community because the bigger the community is, the more powerful it is. When you have, for instance, new enhancement requests or feature requests, then this community can help to push these new features into a new release.

There is room for improvement but overall, I really like working with ARIS.

I would rate this solution a seven out of ten.

ARIS was used to capture current business processes in ARIS EPC through a series of workshops. Level 1-3 VACD, Level 4 EPC (Event-driven Process Chain) and FAD (Function Allocation Diagram), Activities, Roles, Metrics, Risk and Control, RACI, etc.

It was used to operationalize new business processes and also in preparation for a case management system migration to Salesforce. The management, team leader, and staff were trained to read the EPC process model and taught how to navigate ARIS in the production environment. 

The selection criteria for ARIS as the preferred BPM was questionable in my opinion.

The main reason it was chosen is that it was on the government "approved" product list.

The solution was too complex/advanced for the organization's requirements and a big team was hired to manage the administration of ARIS and maintain it.

The choice to model the business process in EPC instead of BPMN was made by the organization and no fault of ARIS; ARIS is most certainly capable of modeling in BPMN. There's a lot of time and effort spent to help staff get their head around how to read an EPC in ARIS.

The EPC modeling is very detailed, the semantic check is helpful, and auto-layout simplifies the formatting.

The process interface is valuable for identifying the upstream and downstream processes.

The approval process for the ARIS EPC from the design, staging, and production environment is pretty good. You can obtain feedback on the process model; however, this functionality seems a bit limited by today's standard as some other BPM allows you to comment on the objects within the process model, which makes gathering feedback and making changes easier.

ARIS EPC & FAD features and functionality does not feel like they are not designed for business users. Instead, it feels like they are geared for Process Modelers and Technology users who are focused on System Interface, User Interface, Risk and Control, etc.

Trying to read an EPC in a screen Top-Down while dragging the screen is next to impossible. 

The model graphics can be exported in PDF, but the model is too small to read.

In my experience, once the organization creates the process model in ARIS EPC, it will take approximately two years before most organizations ditch any effort to update it. It takes more effort to maintain it than the value that an organization gets out of it.

The requirements for events after the rules, whilst accurate, simply take up too much space and makes the process model difficult to read.

Connecting the upstream and downstream process interface is a pain.

The auto-layout is a great feature but does not work as expected all of the time, as lines appear to overlap and can be confusing to read unless you click on the line to highlight it.

We have been using ARIS BPM for two years.

It's pretty stable, at 95% in my experience. There was the odd occasion when the system was down and it took 48 hours to resolve the issue.

More licenses can be added as the demand grows, it just costs more.

Visio was used initially prior to ARIS. Visio lacked the BPM functionality.

It was implemented through an ARIS vendor and the level of expertise was good.

I would suggest trying at least three vendors and obtain written quotes.

The setup cost and pricing depend on the license (Modeler, Viewer, Administrator).

ARIS was the only government "approved" software that the organization was "allowed" to purchase. This was a questionable decision.

My advice is to try different BPM providers and download the demo for 30/90 days to see if it meets your organization's needs. A basic tool means that you will outgrow it quickly, whereas top-end solutions may be too costly and difficult to implement.

We use ARIS BPA for process modeling and the repository of our processes.

ARIS BPA has the kind of database structure to report from across all the models, roles, and systems. The solution provides integrations to ServiceNow and other systems, flexibility of connectivity, and reporting.

Sometimes, ARIS BPA breaks down, and its stability can be improved.

We had ARIS BPA in our organization for ten years, but it was never really leveraged. We have been using it more heavily for a year now.

Around 500 users are using ARIS BPA in our organization.

The solution’s initial setup seems to be a bit difficult.

I would recommend ARIS BPA to other users.

Overall, I rate ARIS BPA an eight out of ten.

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.

ARIS has many modules starting right from strategy to dashboarding. However, the primary focus of using ARIS is for Business Process Modeling/Analysis - although it is not just limited to process but can cover the entire enterprise architecture for an organization.

We have used ARIS for multiple projects with different objectives, including E2E process modeling, managing IT application landscape, support for eTOM frameworks, managing risk/compliance, rules modeling, et cetera. 

We have leveraged it for multiple client engagements with different objectives of the program, including digital transformation journeys, IT landscape rationalization, process transformation, process improvement, process automation, S4/HANA Migration, process rationalization, legacy modernization, and much more.

ARIS provides the basic foundation for any digital transformation an organization decides to take. 

Firstly, it helps to create the business blueprint for any organization. With clear and complete documentation of the processes, different departments and people involved can build a common understanding of processes. It helps in reducing duplication since there is only one single source of truth across the organization. 

It greatly reduces the modeling effort of the processes since it is based on a relational DB which supports the concept of library objects. For example, you can create a central repository of applications, risks, data, products, capabilities, services, interfaces, technical infrastructure et cetera. You can create them once and reuse them multiple times as required along with your processes. This helps the multiple dimensional analysis of your processes. 

ARIS provides many functionalities and capabilities, including:

1. E2E visibility of the processes which are typically cross-functional

2. Multiple hierarchies of the process provides a different level of abstraction

3. Multi-dimensional view of the process can be created to further support analysis from the system, data, capability, product, interface, infrastructure et cetera.

4. Provides a single source of truth for a process consumed by different departments/functions

6. Strong governance and release cycle management with a built-in workflow

7. Process simulation capabilities to perform what-if analysis

8. Seamless collaboration using built-in mini workflows 

9. Out-of-the-box connectivity with SAP

Although ARIS is already a leading tool in the BPA space for years, in my opinion, there are a few areas that can be made even better, For example:

1. The reporting capabilities and the ability to create custom reports need to be simplified and made easy so that people even with a good functional understanding of the tool can leverage it to create their own custom report. Since, at the end of such BPA/BPM implementations, higher management typically wants to see the value coming out of ARIS and all the modeling effort and this would make it more adaptable for our customers as they would see the value coming out of the tool.

2. As the world is going the way of low code/no code, they should also think of modernizing the report creation in a similar fashion.

3. The integration capabilities with other COTS products should be better. Since every organization uses many applications/systems for day-to-day operations, the easy integration with such systems like SNOW, SFDC, et cetera, will make the adoption easy for the client rather than seeing ARIS as a standalone system with separate license and maintenance costs.

I've used the solution for 12+ years.

The ARIS SaaS offerings are very stable and secure since they are hosted on Azure and AWS platforms which provide state-of-the-art hosting. 

With the SaaS offering, organizations can start exploring the basic functionalities with a subscription-based license. The license can be upgraded and the adoption of the tool can be increased within the organization as needed.

They offer excellent support and customer service. 

Positive

We have used many tools, including Signavio, Bizagi, Visio, Nimbus, Mega, et cetera.

I personally found the modeling very easy to start and adopt even for a beginer as ARIS provides a very clean and simple interface to work with. 

The kind of versatility and flexibility that ARIS provides is unmatched by any other tool in the market.

The initial setup is quite straightforward since the Software AG teams take care of the provisioning and intial setup of the SaaS instance based on the requirements. 

Organizations do not need to get involved and invest time and energy in figuring out the infrastructure, security, and access-related issues.

The SaaS offering was handled by the Software AG team itself.

Although not quoting a number, ARIS brings huge value for Organizations that have implemented it. For example, it's bringing E2E transparency of how the business process works in a department/unit since they are typlical cross functional in nature.

Different stakeholders can talk and understand the same language since ARIS provides a single source of truth for processes across the organization. 

Although the largest customer base for ARIS is in large enterprises, the SaaS offering from Software AG starts right from free trial to basic, advanced, and Enterprise versions. Organizations can start small and rapidly scale as required.

We looked at many tools, including Signavio, Bizagi, Visio, Nimbus, MEGA, et cetera.

Since there is a free 30-day trial, I certainly urge anyone looking to invest in process modeling or analysis tools to try out ARIS.

The primary use for the solution is as an enterprise architect tool, but in the start it was about processing; modeling all kind of business processes. And that was before I even mention BPMN. Today, we have switched to using BPMN to do all the different kinds of business process modeling.

This product is supporting it very well.

I'm now working as an independent consultant, but in the past, when I was using it we could really quickly get a picture of what kind of business processes were being used across the entire organization, and which could be reused, and be sure that no one else is doing it another way. 

For example, the HR part, in that organization there were about 20,000 people working there. From an HR point of view, they had to do everything the same way, when they were hiring people, or when they were paying money, etc. There, we had a strong opportunity to define, describe, so that everybody could go in and see, "Okay, that's the way you have to do it. We have to follow these rules."

We could also create a good connection between the description of what we were doing the application. In this part, it was primarily SAP - and ARIS was coming from the SAP world in 1992, I think it was around then. They started as an independent firm, so they could do these things. That's why it's a very strong part, from when it started, but it has been developed now as an enterprise architect too.

The good thing about using this tool is the repository that gives us the opportunity: If you want to do modeling with the old notation form, ours was EPC, you can use the same object in the BPMN because the database is built in a way that you can use both things. So you only have to define it once, and if the notation form is BPMN and those kind of activities, you can use the same EPCs, so there is a connection between them. That is why it's a very flexible tool.

Furthermore, you can use this tool as an enterprise architect tool. So from an architectural point of view, when you're looking at the business area, you can find all the information you have to use as an architect.

The most important part of it, from my point of view - the way I work with it - is from an architect point of view. What I'm using it to handle, from the top-level management part, is where we talk about the strategy, then down to the business part, down to the information part, down to the application part, and to the technology part. So I use everything in the tool.

But, if you have to see it from a BPMN prospect, it will be the BPMN part of it. 

Also, the UML parts have been improved very much in the last two years. And it's very powerful now to combine the BPMN and UML parts in the product, because you can make a connection between them, so that you have the right interoperability between them. So if you're doing data modeling, you can use your class diagram and bind that to the BPMN part. That's a very strong part of it too. Had now implementet the Danish public ad on "Plusprofil" to the UML packed.

I have been talking with developers for many years, and it was before using your UML class diagram and those things for defining data. One of the issues is, when you are defining databases, the way they use entities and relationship diagrams, the way we can define data, like data models, there is still a part they could improve. By using the UML part, you would use that instead of the old fashioned way of an entity and relationships diagram. But there they have a still point where they could improve.

It is a very stable product. In all these years, I think once or twice in the beginning it gave me trouble, but never with stability. It's a very stable product. There are a very few bugs. When you find a bug, just give them a call or write to them and they will fix it. Today they are coming out with two major releases every year. They are really fast to go in and say, "Here is the update for that." So the stability is very good. 

It's also very good at scalability. If you follow what they are saying, how many users you should put on, etc., no problem.

The biggest challenge today is that people will not pay to have the right technology installation. For example, is there enough room for you at the network level to work with this product? In the new version where we can switch between the heavy one or the light one, the browser, there is no problem. It works. No problem.

The level of technical support is very high. Very good.

No, I didn't use a previous solution. If you ask me, if I have to choose between different kinds of solutions, I would prefer to use this. It is the most flexible and most user friendly product you can get. I would not switch. But, of course, when you are consulting, you also have to use other tools. Now, today, I'm also working with one of other tools, like HOPEX from MEGA. It's also one of the biggest tools that you can use. If I have to choose, I will choose ARIS instead of MEGA.

Of course, there are different things they can do, but I would still prefer to use ARIS. For the moment.

Every tool, like these - with so many different things you can do with these tools - you need, of course, education about the tools, and you have to make choices. What part of it will you use? It is always like that. When you work with it during one or two days' education, I think you will be very capable of using it in the area that you would like to work in.

For example, if you are using it in BPMN, one day of education and you will already be one of the best people to model BPMN with this tool. Still, BPMN is a big area to go into. Start small but think big.

You will never get a fixed price for this product because they will go in and ask you what kind of environment would you like to set up? How many people will you work with? How big is your organization? 

Today, they have a fixed price to say, "Okay, just to start the business area, buy two licenses for modeling and eight people that can look into the product." They have this kind of fixed price. It's 50,000 Danish Krone. If you divided that by about six, then you get the pricing in dollars.

From my point of view, no, it is not cheap, but it is not too expensive because you get this big organization behind it, technical support, and all those things. It's not so expensive to use. It's a Rolls Royce in this field, I know that. Even for small organizations, they can get so much effect from using this tool, in a very fast way, so the money will be back in the customer's pocket very fast. 

Still, when you are going out, negotiate and find the right price. You will never get a fixed price: "It costs this and, if you take ten of these, seven of these and eight of these, and then it costs this." No, you negotiate every time.

At that time, in 2002, it had to be connected to the SAP environment. The ARIS tool set at that time was one of the biggest in this area, and that's why we were choosing it. There was something else, but it was not as good. Not stable for the SAP environment. I think it was because of the SAP environment that we choose this product, not others.

Today, I would say, from an architectural point of view, it was a good choice. You will see that in the EU, they also use it in the customer area for defining BPMN processes and data. So, they are using this in the EU now as the main product for these areas.

It is not a challenge to implement the product, not even from a technical point of view, because if you have rights to do things, it takes less than two hours to implement the whole package. Download the product and then just run it.

You have to go to the top-level people and talk to them and say, "Okay, what is your strategy to get a good view of your business?" If they say, "We would like to have something help us to manage, what kind of strategy that we have, what kind of rules, principles that we have to follow, that can give us a picture from the top-level and then traceability down to business areas." 

For example, here in Europe, we have a new law called GDPR, data protection. That's coming in here in May, in the EU. This product can help you to be sure that you will not get in trouble when they come and ask you, "Have you completely made all these different kinds of process descriptions that show us where you are using, how you are using the data, etc?" Here you have a product that can support that.

If you want to have the full picture, also from an architectural point of view, then you should buy a product like this or something similar to this. You have to go up and find the best. ARIS is among the top in industry reviews, and I would recommend it. But I am also using one of the others up there as well.

Again: Where do you need it? That's a very important question to ask. Where do you want to put in? If it's in the BPMN area, use ARIS. It's a very easy way to use it.

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.