The initial setup is not complex, but it has to be logical. If you want to have all the benefits of the ARIS platform, which is an integrated platform, it's essential to set up all objects properly from the very beginning. If you don't have a clear idea of your target architecture, you may face difficulties in really leveraging ARIS.

While there is a beginning to the deployment, there is no end. We can always enrich ARIS with more and more information, and we can always involve more and more and more people in the tool. The usage of ARIS is unlimited.

The implementation strategy starts with the transformation journey, and we are implementing ARIS to support that journey.

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.

For our setup of the recent migration, which we completed over an eight-week period, we found the migration of our ARIS instance into the cloud to be really smooth and well-supported by the Software AG Professional Services team.

It should take about three hours to fully deploy and configure.

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.

The initial setup was straightforward. The solution is deployed on the cloud. It took us a few days to deploy it.

The solution is deployed across the entire company, almost everyone uses it.
We currently have around 600 users, but we're planning to scale up to approximately 2,500 soon. We have around 30 people maintaining the data.

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.

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

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.

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.

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.

ARIS BPA’s initial setup was straightforward.

When you start the solution, you eliminate every useless variant that you do not need, then it is really simple. At the starting point, you need to learn how the philosophy of the solution works. You need to deal with the solution as if you are taking a normal car through the woods. You can't normally. You have to think, "Okay, what is it built for? How is this model designed?" You then need to get in contact with the design and philosophy. After that, you can do a good job. It is a big mistake to say, "No, they have to code everything around our old company stuff because we always did it that way. So, we need to stay with the old way." Then, you are lost and will never have any kind of success. 

At the start of the project, we set up some testing and development implementation. It took us one to two weeks for our IT and Software AG's IT to get it up and running. Before we were productive, we had to edit the publication database as well as all the backups, restore processes, and all that stuff in a production environment. We also had to put brain power in it. That was for part one and two of the processes (installation and implementation), which both took one to two weeks. That was net five to 10 consultant days or IT expert days to get up this step in performance and excellence. The implementation was about two days. 

The initial setup was straightforward.

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 solution’s initial setup is easy.

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.

We purchased the license for ARIS a long time ago, but the central team was dismantled. We revived it back in 2018. Deployment wasn't too easy. We didn't have a maturity roadmap in place, so we were building it step by step. I wasn't able to see the end state or the steps we needed to go through to grow more mature. I'm not blaming Software AG for that. That's just how it went. The deployment process wasn't intuitive or transparent in terms of the next steps we should take. It was also complicated by the fact that our needs as a customer changed from month to month and year to year.

The initial setup was not that complex; we could manage it with an installation guide. ARIS Connect is plug-and-play. It is a SaaS offering.

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, :)

You can start from scratch in a very easy way and after that, increase the complexity. The tool supports it.

The initial setup is straightforward. It does not require much maintenance. 

The initial setup and installation are very straightforward. The administration is a bit clunky because of the way it is set up as a Software-as-a-Service. There was not really a Single Sign-On capability for the tool. You have to maintain your login separately and that is a little archaic.  

Because it was already running, there was not really a deployment to get me going with the product. It was just a matter of adding me as a user.  

My understanding is that the initial setup was easy.

We have deployed the product on the cloud.

The solution is complex to install. The solution's configuration part is heavy and complex. The tool's setup takes one day to complete. You would need two to three people which would include, the technical lead, project manager, and developer to handle the deployment. 

The initial setup is difficult because it's that you installed the server version, and then you can run it. You have to play and run some SQL scripts out of the system for the database SQL Server if you are using and searching. But the new ones on the cloud have no installation. The deployment is quick overall. Only one engineer is enough for the deployment. Now the solution is easy to maintain because the method and the codes have changed. And less support is required.

The initial setup is straightforward for a user with ARIS BPA installation experience. There is not much that is complex, even for someone who is not experienced with ARIS and tries installation. But that person should be technically sound with installation practices.

The initial setup is still very subjective. But the installation is easy. It'll take about five to six hours to get it up and running.

Aris BPA is difficult to set up and get started with.

The initial setup was easy.

Medium complexity.

Setup was straightforward. 

Technically easy, but BPM and EA are complex and require considerable pre-planning.

The initial setup is pretty easy but in most cases of large enterprises adaptation is required based on their LDAP Integration and SSO needs. It's the first step with every customer. Software AG'' s team is always willing to help us out in any situation even in the most demanding cases where functionality customization was requested.

For the standard DBMS, things are quite straightforward. Network security and server security settings can be issued.

The setup was a bit complex compared to the previous version of the tool.

You could walk someone through it, but I would not recommend trying it on their own.

This product is rather complex to set up.

Complex.

The Aris version that I have is straightforward.   

The initial setup was a complex affair for us. We had to engage in six months of training, in-house, with a trainer. A group of people were trained and then finally started process modeling on ARIS.

Over the six months, it was easy, step by step, where we had to follow one thing at a time and there was a lot of time to practice.

We used a consultant for the deployment.

When I got the ARIS BPM introduction, we were already using the platform.

Straightforward, it is a simple wizard to install.

It is quite easy.

We were involved in the initial setup. My experience is positive, but regarding usability and learning of the system, those elements can be more difficult and complicated.

Initial setup was straightforward.