Primarily, our use case is app rationalization. First, get a clear inventory of what applications we have and how they're categorized.
Secondly, identifying obsolete ones for retirement or replacement. Those were the key reasons we bought it.
Primarily, our use case is app rationalization. First, get a clear inventory of what applications we have and how they're categorized.
Secondly, identifying obsolete ones for retirement or replacement. Those were the key reasons we bought it.
When we input our inventory and components, it tells us which ones are nearing end-of-life, deprecated, or obsolete. It also categorizes them.
We've added flags, essentially tags, to mark certain things as non-strategic technologies. Using LeanIX, we made conscious decisions about which technologies are strategic and which aren't.
This allows us to generate reports highlighting applications written in non-strategic technologies, giving us a better picture of our inventory size and what needs to migrate to the cloud or our target technology.
So, it's about understanding what we have, seeing how it aligns with our strategic direction, and then driving the movement towards that direction.
The ability to import data and generate reports from it. That's where its power lies.
Report generation could be more detailed. There are some shortcomings when creating reports. We can't create tag-based reports or go beyond basic technical reports. I'd like to see more tags and more out-of-the-box column reports offered.
I have been using it for six months now. We recently upgraded to the v4 schema.
I would rate the stability a nine out of ten.
I would rate the scalability a ten out of ten.
The customer service and support are good.
Positive
The initial setup is very straightforward.
The ROI is significant. It used to take us weeks to gather data on technologies nearing end-of-support or becoming obsolete, but now it only takes minutes or hours.
The pricing is very good. We definitely get good value for the money.
We evaluated a bunch, like Alfabet and Ardoq. LeanIX just had more features and offered better pricing.
Make sure you have dedicated staff to support the tool going forward. Overall, I would rate the solution a ten out of ten.
I used it for a customer where we had to do application rationalization and portfolio optimization.
Ease of use is the most valuable feature. From an enterprise architecture perspective, it's not too cumbersome with too many functionalities, yet it has a lot of attributes for the content it covers.
So it's not too cumbersome. Its depth is good. I like that about it. It's compatible with a lot of other applications. It's catering to the area where others are not. So it's kind of complementing; instead of competing with others, it's complementing them.
Moreover, it's very customizable. So even if I want to implement a new framework, I can do it.
The solution offers ample of options. It's very flexible, with features, functionalities, and an admin console. You can customize it extensively. For example, if I need to add custom attributes for an application, I have that flexibility. It's a very flexible and customizable solution. I'm confident that my requirements will eventually be met within it.
The solution uses Gartner's time-based framework for application rationalization. One more thing that you can consider is having some add-on frameworks for the same, not just Gartner.
It covers a lot from an enterprise architecture perspective, but it's not as robust in business architecture.
I have been using this solution for six months.
I would rate the stability an eight out of ten.
I would rate the scalability an eight out of ten.
We have around 15 users are currently using LeanIX in our organization. Our current consumption is at 80%. We often get more requirements to increase its usage.
The customer service and support are good. I have heard positive feedback from my counterparts. I personally haven't had the need to contact technical support as everything I needed was available within the solution. Also, we have an in-house team to support it.
Neutral
We did consider other options like Thick Navio and Solonis, but they were getting cumbersome, especially as we were moving away from certain areas of operation. We found that LeanIX had the capabilities we needed.
In terms of pricing, it's cheap. I would rate the pricing a one out of ten, where one is cheap, and ten is expensive.
I'd suggest starting with a simpler use case and then expanding as needed.
Overall, I would rate the solution a nine out of ten.
It offers neat visualization and referencing functionality while enabling the creation of landscape maps and showing the relationship between different applications. It allows logical mapping and basic architecture design, making it similar to other tools used for creating schemas. The tool is easy to adopt and has a low barrier to entry in terms of usability. Overall, it is a user-friendly and comprehensive solution for optimizing IT landscapes.
I highly appreciate its usability and capabilities for enterprise asset management.
It would be beneficial to have additional features and capabilities to enhance mapping between applications, especially across domains where the relationships may not be direct. Adding a basic intelligence layer that could suggest connections and dependencies based on labels metadata assigned to applications in the future would save time.
I have been using the solution for a year.
We didn't face any issues regarding the performance stability.
Being mostly used as a repository, documentation and design solution, we didn't have scalability issues with the solution.
I had experience with similar tools in the past and I consider LeanIX to be one of the best alternatives on the market.
Prior to choosing LeanIX, I would suggest verifying the ability to adopt it and its features to utilize its full potential. It does require significant expertise and technical proficiency, as it is a tool primarily used by a limited number of experts in the architecture field. I would rate it eight out of ten.
I use the product primarily for architecture management purposes.
One of the product's most valuable features is its ability to configure the hardware devices and provide deployment views in the architecture. It can get an updated overview of your inventory, which is a good part.
At present, I need to integrate LeanIX with the modeling tools to automate VPN. They could include a combination of the product and some modeling extensions. It would be a great idea.
I have been using LeanIX for three months.
It is a stable solution. I rate the stability an eight or nine out of ten.
I had a good experience using the product on small and large-scale projects. It works fine.
I rate the product's initial setup process an eight out of ten.
It is overall a good tool. I rate it nine out of ten.
We are system integrators for LeanIX. LeanIX works in the petroleum industry towards the production of petroleum products, supply and demand, supply chains. The company was looking for an end-to-end view of its environment and business capabilities across the organization. LeanIX is indicative of that process. I'm a company partner.
This product has the ability to interface with downstream systems of data, whether primary or secondary. It's one of the better in the market place. It's an extremely useful system to enable visualization of your end-to-end flow and to look at future proofing. It's got great graphics and is new, modern, and completely cloud-based. It's efficient to put into production quickly.
LeanIX does a poor job of being able to allocate detailed costings to components within the network, rather using an average base, and it won't let you extend its data structure to include detailed pricing information. That is not sufficient in today's world and climate. The biggest issue we have is that the support staff are in Europe and we're in Southeast Asia so it's difficult getting support.
They need to be able to provide extensions to their metadata structure so you can create functions but you can't add metadata structure, so you actually have to get creative and start using additional add ons or add on libraries. It takes away from maximizing the use of LeanIX.
We've been using LeanIX for about three years.
The solution is highly scalable. Scalability is only limited by the license type so it's about the number of active users as opposed to the functional component.
There are difficulties with support because our company is based in Southeast Asia and the support is based in Europe.
This is an SaaS product so it's on my network and the maintenance is automatic because of that.
I recommend this solution but it's important to engage the business first and acknowledge that they're the owners of the data. Engaging the business significantly improves the return on investment. I rate this solution nine out of 10.
I like the tool’s integration and maps.
The solution’s API integration needs to improve. I would like to see a digital screen watch feature also in the solution.
I have been working with the solution for a few months.
The tool needs to include more flexible licensing options. We do not use the tool all the time. So pricing should be considered only when we use the tool.
I would rate the overall product an eight out of ten. It is always good to do a POC and validate what you are trying to achieve with a product before using it. You need to know the integration capability of LeanIX to make the choice meaningful.
The product has matured a lot over time. They've moved up into the enterprise architecture realm very well. They're still able to provide substantial value on application portfolio management (APM), and in doing that, I am able to drive cost savings to justify the purpose of the tool. From that standpoint, it's a very good tool, and then we're able to get a lot of the enterprise architecture facts from that.
The most valuable feature would be application portfolio management, which is where they came from, but over time, they have got artificial intelligence. They built up a very good repository. If I identify a system by name, from historical information, oftentimes, they can tell me that this is deployed with this number of CPUs and they can give me a really good profile of the application for me to put it into a change management database with very little effort.
They're moving forward pretty well. I'm seeing a little bit more focus on the business architecture side than they are currently focused on, but the pendulum for that is shifting back to more of a traditional enterprise architecture view, so they're probably positioned pretty well for that. Over the next eighteen months, you're going to see people starting to move back towards more of the traditional enterprise architecture view versus the MDA-type business view of the world.
In terms of focusing a little bit more on the business side, there's a short-term window. By the time they focus on it, the window would have closed, so their current trajectory is very good. Some of them are trying to position with the heavy, what I refer to as, MDA-flavor on how business architecture is being addressed, and I see the pendulum has already swung out to that area, and it's starting to come back. So, if you're building for that now, it's not going to be that significant when you get to market with it.
They're probably positioned pretty well. I hope that they would not focus that much on the business architecture, and they would focus more on the overall cloud strategy and how we can leverage multi-cloud and transition back and forth from other cloud providers. With a lot of current vendors, you get locked in with one cloud, and then you try to migrate to someone else, and it becomes very problematic. What they need to do is to look at the overall data strategy, and they probably need to amplify their data strategy, especially around multi-cloud.
I've been using it off and on for about five years.
I have not had to deal with their tech support. Most of the people who have been working with me on it have been very comfortable with it. Anytime we've had questions, they've been very helpful. It was years ago when we had to reach out to them, but they were very supportive, and normally, it was the person in the sales cycle who was supporting us. So, it was very high-touch when we reached out to them.
The actual initial time to value is about three days. I can get it installed if I have someone who knows what they're doing with it. They can import my data because normally, we have the data laying around somewhere, and I can get through and identify overlaps in my portfolio within probably three business days so that it gives me a good value.
Their go-to-market is rather interesting where you can do a pilot. In the pilot itself, you can pretty well identify enough cost savings to justify the full purchase. From that, it puts them in a very good position to then be able to save you additional components and make your enterprise architecture more robust.
I have not done any recent ones. Most of my data was from around three years ago, and I was getting a full return on investment in under six months. Normally, I'm looking for at least around eight months. That's normally what I'm expecting, but anything better than that is really surprising. With some of the more expensive tools, we're looking at a two-year ROI. They can move up their price just a little bit based on that.
There is a sweet spot of where they need to be on pricing right now. They could go up a little bit in pricing, but it has to do with the cost savings, and it has to do with the practitioners using it. I use it where I get cost savings and I can justify it, but they probably have the ability to flex a 10% up channel on their sales on that. So, they could increase their settle price, not their offering price, when they sell. They can probably hold that up a little bit higher than it is because there are cost savings that we can drive from it.
I would rate LeanIX a solid nine out of ten. I've recommended it for usage to probably seven customers, and four of them purchased it.
LeanIX is used for cloud governance from a business perspective, for example, to understand technology management, application portfolio management, data flow, and integration architecture.
LeanIX has a wide range of integrations, a data model, business architecture, and technical architecture, making it a comprehensive end-to-end solution. For example, the solution can be used for cloud use cases, Azure, and AWS components, and it imports data related to great availability and data modeling. LeanIX is user-friendly.
LeanIX has a great application information architecture. Currently, the interface application project and data objects are well organized and defined, making it easy for people to use. Additionally, the business architecture, for which I have used the business application processor, is properly aligned with the current market needs. The solution has many integrations which are easy to use.
The initial setup has room for improvement. Currently, the setup is complex.
I have been using LeanIX for one and a half months, and have found it to be one of the best tools available.
LeanIX was initially difficult to use because it is very new and there is limited knowledge available in the market. We had to read the manuals, watch videos, and search YouTube for information. The initial setup took some time.
I give the solution a seven out of ten.
We should be aware of our enterprise architecture strategy, and the governance we want to implement and use the solution accordingly. There are many different architecture layers and methods, such as content service platforms and solution architecture modeling. For example, we could use Sparx, DT, or something else. It is important to choose carefully within the strategy of what app we want to use, as there are many options. For example, there are other interfaces for unified communication, such as Slack, Microsoft Teams, or Atlassian Chat. It can be difficult to decide which is the best-unified communicator for a company if there is no report outlining which unified communication should be used for a global purpose.