The initial setup is not complex. The teams didn't reach out to SAP for help. 

We deployed it both on the cloud and on-premises.   

For the deployment process, we would have started with creating the business case or figuring out the value chains that needed to be impacted, then got into a little bit of data work, and finally the deployment.

The initial setup was straightforward.

The initial setup for this solution is very straightforward, especially compared to the ARIS product that we were using. Essentially, when you sign up, they give you the username and your password. You can set up the end users in one day.

The difficulty in setup is not on the Signavio Process Manager side. Rather, it is a question of whether the process architecture has been properly defined for how you want to document the business process. Obviously, that has nothing to do with the product, but you need to have a process architect who is able to set up the process governance framework prior to the process mapping.

There was a period of change management because of our switch from the ARIS solution, so there was training involved, but it was a fairly easy transition.

During deployment, we had one person doing the training, who also helped us translate processes from ARIS to Signavio. We had one person to manage it, and another to help us roll it out.

The initial setup was straightforward. It was easy and fast. 

It is browser-based and cloud-hosted.

The initial setup was pretty straightforward.

The initial setup was very simple. It took us less than three weeks from signing the contract to having the first users online. We put people through training and we are onboarding users and our core value change progressively. We're only just getting to the actual the rollout at six months after completing testing.

We are working fairly closely with the vendor for integration. Right now we are only beginning to explore the capabilities for enhancing customer experience, mapping customer journey, and the mapping functionality.

In terms of just implementing it, it's very simple. My team has scaled up very quickly. We are to the point of being able to develop internal user training that I think is quite effective.

The initial setup was straightforward.

The initial setup was straightforward and efficient. I would rate it eight out of ten.

The initial setup was straightforward, and although we used Signavio's premium rapid deployment, we could've most likely done it by ourselves.

I rate the product's initial setup phase a seven to eight on a scale of one to ten, where one is difficult and ten is easy.

The time for the product's deployment phase varies, but it is an easy process if you know what to do and if you want to deploy it. On average, the deployment process can be completed in two or three days.

The solution is deployed on a public cloud.

The initial setup was straightforward. We had a few information security issues to work through, which was due to the BBCs level of security and what we require. We've gone through all of that process. Again Signavio was on board and made sure that if we had any questions they'd answer those for us. We had their engineers on any calls with our InfoSec team as well. All of that worked through fine.

The tool is cloud-based. The initial configuration takes less than a minute.

The initial setup is complex. The time taken for deployment depends on how much potential you would like to receive from the tool. If we need to get a lot out of the tool, we need training from a specialist. Sometimes, we need more than one person. We need a whole team. The specialist and the team will cost us more. The solution is cloud-based.

The initial setup was very quick and it was an easy introduction to start with the first work!

For me it sounded simple, but I don't know if the people behind it found it to be complex.

The setup seemed straightforward. When I saw it, the solution was up and running.

It did not take long to get this product up and running. I would say we did two or three really intense workshops with one of the Signavio guys going through the configuration and general settings. Then we went through it as a team and decided on this. It was really quick. It took us more to determine what the content would be and how we wanted to start. We created a process house. That was more an issue of how to start from a content perspective.

The initial setup was straightforward.

The deployment took a month. I registered for the initiative, then they provided me access. After that, I explored the environment a bit. I needed to register my separate accounts so I could have one screen from a teaching/lecturer perspective and another screen from a student perspective. This is so I can test the environment in a manner where I can then provide some guidance for students to complete their tutorials.

Straightforward initial setup, that was well prepared and all our questions could be answered.

We have one to two people involved in the product's maintenance. 

Our experience was that we used Signavio's own consulting team to do something called a rapid deployment. This was a quick and easy way to introduce Signavio into the organization. In just a few days, they came on site and talked to us to understand our context and situation. Then they could configure the entire solution. It's a very easily convertible solution anyway. Nonetheless, they walked us through it and it gave us the confidence to use the solution.

We start with implementing the solution once we get access to its licenses. Further, we use the agile process for deploying it.

The initial setup is straightforward. You can set it up in the way that you want if you know it.

Not everyone should set it up on their own. If you have your administrators and people who know the system then they can set it up the way that you want.

Also, you have the support available from Signavio.

I was not involved in the decision to buy Signavio because I was not in the organization at that time. However, I was the project manager for the implementation. I joined the company two months after the decision to go with Signavio, and I set it up.

The setup process was complex because there are so many things you have to keep in mind. There is the configuration of the system, and not only making the tool available, but the roll-out of the processes, the training, and learning all the interfaces.

In addition to me working on the setup full-time, we had an additional person who worked on it half-time. We set up the system and configured it according to the requirements of our organization. Of course, for the BPI content and the processes, there were more people involved.

We had an old tool where we had all our processes and then we had to transfer all the processes from it to Signavio. In the beginning, we thought we would do it in less than a year, but that was not manageable. It took us more than one and a half years to go live.

It was easy enough. I liked the simplicity and usability of the program. It was not difficult for me, possibly because I am already a trained user.

The deployment did not take long. At most, it took up to half an hour.

From the technical point of view, it's very simple because as soon as you use a cloud solution, you don't have to worry about anything.

From the hands-on and from the working point of view, it might be a little bit difficult if you have never worked with BPMN. However, as soon as you get into it and based on the help Signavio or the tool provides, as soon as you start to work in it, it is pretty straightforward. If you're a motivated user it might take one to two weeks and then you are fully functional in Signavio.

Integrating with SAP source systems is notably straightforward due to the readily available connectors designed for seamless compatibility. However, establishing connections with external systems presents more challenges, especially when considering tools of other vendor invoice management solutions While Signavio incorporates a Copa in its arsenal, integrating these types of external tools proves to be more complex. In contrast, Celonis excels in ease of integration. This divergence in connection capabilities stands as a key differentiation between Signavio and Celonis.

Regarding the support aspect of the solution, yes, it is straightforward. Handling signatures is also a straightforward process. Maintenance, specifically in terms of coding, becomes a consideration. Changes in product development can be difficult. Once an alteration is made within Signavio, it has the potential to impact the front end as well. This observation holds true for Signavio.

After the system connection is established, the timeline for deployment is dependent on the specific process. Integrating the tables into Signavio is achievable within a relatively short span, typically ranging from three to four hours, and seldom exceeding that duration. Almost four people are required for the deployment.

Deployment was painless and straightforward. Signavio offered structured support. 

If you are experienced then it is really straightforward.

The initial setup was very easy. 

This is a SaaS solution and it was easy to set up.

The initial setup went well and I have never had any problems.

It takes a few days to set up. We have a central department that manage the licenses.

I rate the tool's installation a nine out of ten. It takes eight months to complete. One to two resources is enough to handle its maintenance. 

The initial setup was straightforward for the people who did the deployment. We had an idea of what we wanted to do, but they really helped us put it together.

The initial setup was simple.

The solution's initial setup is easy. I rate the process a ten. It requires three administrators for deployment and takes a month to complete. It includes setting up the software and installing it in each department.

I wasn't involved in the set up of Signavio in the first place, but I think it was fairly quickly done. What I was involved in was the migration of the files from our previous solution to Signavio. That was fairly easy. It was just a migration and a renovation of all the diagrams migrated. We had to do a manual brush up of the diagrams and then we were good to go.

Because we are using Software as a Service, there are no issues with installation, setup, or upgrades. Just open Internet Explorer, Chrome, or another browser and use it.

We are using it as SaaS so there isn't much deployment. You just have to use the URL and the password. The deployment doesn't require much help from IT, but what IT did help us with was the security aspect. But IT's involvement was very minimal.

The deployment didn't take more than a day or two.

The initial setup is very easy. You have to configure the software, the rules, and the rights for the objects. All of this is easy to do. 

The initial setup is straightforward and not complex.

The initial setup was very straightforward.