What is our primary use case?
Our primary use case is for architecture management. Signavio has a standard integration for BPM, but everything that is related to architecture is on the LeanIX side. It's application portfolio management, project portfolio management, engine components, and technology spec. It's for typical enterprise architecture.
What is most valuable?
The usability is very high. It almost looks like a Facebook for Enterprise architecture, it's pretty nice. It's HTML5 based. The repository is very easy. It has 10 different ways of sorting the objects you have in your architecture repository. Maintaining new data or to add data to your repository is very easy.
The new feature LeanIX offers is actually that you have a so-called LeanIX store where you can download custom reports that already have been built and uploaded to the LeanIX store, partly for free. You can already download existing solutions or access new reports to your repository. You just add them. You just click add and they automatically add it.
For how long have I used the solution?
I have been using LeanIX for three years.
What do I think about the stability of the solution?
From its functionality, it is extendable at a high level, but to get your full-blown majority in Enterprise Architecture is not so easy. From a scale from zero to 10 from the maturity of Enterprise Architecture LeanIX could hold together from zero to seven but you will not get the last three points.
How are customer service and technical support?
The technical support is actually very good. It depends on your SRAs that you defined with the company. If you have a huge solution board, a huge number of fact sheets, you will have tech support within 24 hours. It depends on the number of objects you have in your repositors and the more objects you have and the bigger license you have, the faster the SRAs are defined. You have, at maximum, a 24-hour response. I received emails around two hours after my question was submitted to tech support, that was very quick.
If you press the critical button you can always get in contact almost instantly.
How was the initial setup?
The initial setup is actually straightforward. You need about 15 minutes to get used to the tool. It's very quick.
You don't need a tech person to do the deployment. Any business person could just review data and add data. They simply just need to understand the meta-model within 15 minutes.
What other advice do I have?
My recommendation would depend on the use case. We cannot go to the customer and just advise them to have one kind of tool. It depends on what they have in the architecture and what kind of solution they want to have. Some companies are just fine with a seven-point solution. Some companies want to implement very difficult workflows. Then I would tend to use Alfabet from Software AG but it really depends on the use case.
If you have a company that's setting up Enterprise Architecture and already has all the documents produced in Microsoft environments, iServer's a nice solution. It really depends.
I would rate it a nine out of ten. Not a ten because you always have that gap between complexity and easy to use. And the more complex the tool becomes, the more difficult it is to get the usability. For example, Alfabet is not bad, it looks good and it's not bad, it's easy to use. But therefore the meta-model has over 700 classes from the standard in comparison to the 10 classes in LeanIX. LeanIX is very, nice from the visibility side. This is the one point that I wouldn't give, but this was something that the gap is really hard to fill.