ADOIT Reviews

The solution describes the enterprise architecture for the company, encompassing everything from the business side to the technical aspects.

The tool allows us to track the life cycle of products and resources. When the metadata is set up correctly, we can see where things are in their life cycle and how they fit into our processes. It helps us understand which core processes are active and whether any underlying elements need renewal. We can also keep tabs on the costs.

The most beneficial feature has been reporting. Being able to track the life cycle of products and services and understand their costs has been crucial. However, I've also been exploring other features that allow us to evaluate tools from both the business and technical sides. The tool was easy to get started with. 

Some of the reporting features have been particularly useful for our company management. I've built reports showing the costs of running the company and the processes running beneath them. Additionally, I've used it for lifecycle management from a technical perspective. I discovered a feature I haven't tried yet: exporting data to HTML. This allows for neatly gathered reports in one place where you can search through them via HTML and find what you need.

The tool's data lineage could be enhanced. It would be great to see the data flow and understand where it's going within the system.

I have been working with the product for six to seven months. 

I haven't had any issues with ADOIT's stability. 

My company has only one user for ADOIT. 

I haven't communicated with the technical team yet. 

ADOIT's deployment is easy. It doesn't require any maintenance. You need to log in to the cloud and use it. 

I use ADOIT's open-source version. 

The tool is still being integrated into our enterprise architecture. It serves as a tool for gathering and providing information, but it hasn't yet directly solved a critical business issue for me.

I haven't explored the developer side much, particularly regarding pushing information about resources via the API. Since I'm using the open-source community version, I'm unfamiliar with how the API works and how it could benefit the company.

I found the product through a Google search. I would say that enterprise architecture is more cultural for a company. But if it's possible to start using the tool, I would suggest trying it, especially since you can get a trial with demo data during the initial setup. This makes it quite easy to work with before transitioning to your data.

I believe that if the product is good, then you should give it the full number. So, at this point, I'd give it a ten out of ten. Afterwards, once I know more about how the API works and what kind of data I can input via the API, I may evaluate it again on the same scale. It's working perfectly, it's a ten out of ten.

I use ADOIT as one of the enterprise architecture tools for modeling.

We use it for our ArchiMate specific modeling for language for enterprise architecture. For example, ArchiMate is a type of language. I use it for modeling the entire BDAT, business data application technology layers, for my enterprise architecture and it's a very good tool that really helps me to build all these layers. 

Starting on the business probability roadmaps, it helps me to model the entire application layer. It helps me to model the data layer and even the technology layer I can model, and there is a standard set of represented models. 

It helps me to model the architecture at an enterprise level. That's where the tool is pretty helpful.

I can also build the heat maps and current metrics out of this tool. It's an awesome tool, to be honest, and it assists me in segregating the objects and digital alignment with the enterprise master data management teams. It's a very good tool.

It's a really good modeling tool.

If you want to build the architecture using to graph ArchiMate language, this is the best tool I've seen at least.

During the first 18 months, for at least three months, we tried to get some training. We started working on the modeling part and we are still evolving in this tool. There are a few recommendations that have been put to the vendor, and we've gotten some answers and the team is evolving the tool in this space. 

I don't have anything to complain about right now, although there are a few things that we are discussing with the team who is connecting with the vendor to get that resolved. 

Specifically, we need to understand how the data could be segregated. We need to know how the enterprise-level metadata and master data could be managed in this tool. There are multiple open questions.

I've been working with the solution for at least a couple of years now. It's likely nearly 18 months or longer at this point.

It's pretty much a web-based solution for modeling purposes. The stability, as far as my understanding, is good. I've never faced any specific issues, at least in my mode of working. However, people, at some point in time, believe that this tool, being a part of the web client, requires continuously saving the data. Sometimes if you forget and start working and you spend some time modeling, and all of a sudden you, unfortunately, close the browser, et cetera, there is a chance that your data is lost or your part of the modeling, whatever you have done, is gone. 

That said, I've never faced that issue. I'm compliant and I continuously save my work. Other than that, I don't think I've seen any issues in this tool, as we just started using it 18 months ago, which is not a very long time. We have to see each and every part of the tool first. We need a bit longer with it.

There are multiple people who are working as we are end-users. It's an enterprise-level tool. 

I don't personally deal with technical support. That said, technically we do have third-party support for this particular tool, however, there's a different team who deals with it.

I'm not pretty much involved in the installation process. I'm the end-user for this particular tool. I try to model architecture diagrams using the ADOIT tool.

I'm not sure how many people are needed for maintenance. 

I'm not sure if the company used outside or in-house teams for deployment. 

We're just customers and end-users.

I'd rate the solution at an eight out of ten.

This particular product would be really helpful to model the architecture at an enterprise level. When we talk about building architecture, we try to visualize specific domains of the architecture, like business applications, technology, and data. This particular tool will help to visualize all layers, in the context of what we are trying to build. That's pretty much the beauty of the tool and this is really helpful for any.

It follows the ArchiMate principle - including the ArchiMate modeling, the language principles. That gives us the entire visibility of the overall architecture that we are trying to build. If we want to drill down at a business accountability level, we can do it at a business application level. We can do it at which particular application is using what specific data. It's a very transparent tool and we can also build data flows in it when it comes to the data layer. It's a very helpful tool when it comes to enterprise architecture.