Avolution ABACUS Alternatives: Selection Criteria

Framing the decision

Avolution, established in 2001, presents ABACUS as a tool that starts simply and supports larger programmes. An organisation that already uses it has models, assessments and roadmaps built up over time.

Looking at an alternative therefore starts from needs that have changed: hosting, the number of contributors, the place of decisions or a new regulatory obligation. Architecture tools differ less in their ability to model than in these conditions of use.

What Avolution highlights

According to the vendor, ABACUS is used to design, plan and communicate architecture, from a small team to a large programme.

• Diagrams based on prebuilt frameworks.
• Automated assessments: cost roll-ups, business and technical fit, security scoring, tracked over time.
• Roadmaps for projects, technology lifecycles and risk initiatives.
• Use in a web browser, as a hosted service or on the customer’s own servers.

Reasons to look at an alternative

The following reasons come up in evaluations; each should be checked in your own context.

• Hosting: a regulated entity may require a data region, a list of subprocessors or deployment on its own premises.
• Language: business units, compliance and auditors may need screens in French or German.
• Participation: the number of people who contribute and read depends on the licensing model.
• Governance: named owners, reasoned decisions and a log that can be consulted.
• Regulation: a DORA chain maintained from the critical function to the contract.

Starting from the cost of migration

For an organisation that already uses ABACUS, the decision depends first on the risk of change. Two questions matter more than a feature list.

• Migration: how your models, metamodel and assessments move to another tool, with the effort and losses involved.
• Ways of working: how well the other tool fits the way your architects and owners already work.

The profile ArchiLU is designed for

ArchiLU does not present itself as a broader quantitative analysis engine than ABACUS. It is designed for organisations, often regulated, that want to maintain their architecture with named owners and traceable decisions.

• One dedicated instance per organisation, hosted in the European Union; deployment on your infrastructure as an optional service, quoted separately.
• Screens, tasks and help in French, English and German.
• Unlimited users, readers included.
• The DORA chain, from the critical or important function to the provider and the contract.
• An Excel workbook to take in inventories, with one tab per object type.

Deciding

If your main need is quantitative assessment of large architectures from an existing metamodel, ABACUS meets that need according to its vendor, and a migration has to be justified. If your priorities are participation by every role, traceable decisions and the DORA chain, try ArchiLU on your own case during the free one-month trial; compare both vendors’ hosting options with your requirements.

• The modelling depth your team actually uses.
• Whether your hosting and DORA requirements are firm or preferred.
• The people who need to contribute, and the effect of the licensing model on their participation.
• How soon you need a usable, auditable repository.