When a client is looking for information on how to leverage an EA tool or how to look at the analysis that can come from an EA repository using the tool to create reports and dashboards, I can demonstrate that to them.
I can demonstrate capabilities of what EA tools should be doing and how they should be doing it.
Whether the client has a current tool in place or not, I can compare the information that needs to be gathered when you're documenting your architecture. Then I can tell the client that this is why the information is important to document. It may seem trivial or non-important at the time but it's important for later on because it allows for analysis and to do things such as project interdependencies reporting. This provides the ability to identify lags in the project delivery, where projects may depend on capabilities being in place but are not in place already. You will now have a lag for another project that is going to deliver early.
It gives you things for capability overlaps, gaps, and standards.
The most valuable feature is that it has a customizable meta-model, which is key. It has extensive uses of catalogs, which can also be called inventories or taxonomies, and that is important as an enterprise architect. A solution designer would need that.
Rather than starting from scratch, leveraging a section of the predetermined solution and then plugging it into the solution that they're trying to develop provides interoperability or greater potential for it.
One of the key things that Abacus does is that it has a 3D modeling capability that can identify multiple levels of connectivity of components through their 3D views.
An example is looking at if A is connected to B and B is connected to C and C is connected to D and so on, you can have multiple levels of connectivity which wouldn't necessarily be obvious because you don't document it. The tool makes the connection for you.
If you are going to change the tactical standard in your organization and you were going to make everything TCP/IPv6 and you are no longer going to use V4, everything has to be V6. You will want to know what the impact is going to be before you make the change. How many different solutions and how many different systems are out there that you have to change or modify.
You can do an impact assessment through Abacus. You can then model it better and you can manage your standards, and also you can manage your solutions simultaneously.
You can see which capabilities may impact where you wouldn't normally connect a standard to a business function or a business capability.
You can also do it through this nth degree of connectivity. It's making it less complex, but more aware of your business environment.
A good example would be if you were going to remodel your home and you want to know where every electrical plug-in is and what fuse it is connected to. That would be very helpful before just going in there and guessing. It's a lot more, as it will tell you if you have different levels of connectivity. For example, you want to go in and change one thing, but what is that change going to do? While you can change a fuse or a receptacle, if you don't know what it touches then you are going to shock yourself.
Another great feature is that you can create reports on the fly.
It's a role-based tool, where you can identify who can change what type of models. They have different permissions and you can manage those very easily within the tool.
One of the things I like about this tool is that you can do an "as is" and "to be" set of models and you can compare them.