We score EA tools against your requirements, not the vendor's pitch deck. Most entities arrive with three or four tools in mind; we send back a weighted matrix, not a pre-baked pick.
The tool pulls your capabilities, services, processes, applications, and data into one repository and wires them together. The value is in the wiring, not the diagrams. When the CEO asks what breaks if we retire system X, you answer in hours, not weeks.
Sit with stakeholders, capture the entity-specific requirements (not a reused template), and agree the judging criteria.
Narrow the market to three or four tools that fit the entity context and budget envelope.
Weighted scoring across eight axes: NORA / TOGAF / ArchiMate, Arabic, in-KSA deployment, license model, analytics, integration, TCO, and local support.
PoCs with more than one vendor when the decision warrants it — on your data, not a demo dataset.
A named recommendation with the reasoning written down, plus an initial implementation plan with timeline and ballpark cost.
We recommend the tool that fits, even when it isn't ABACUS. The selection phase runs neutrally, and the comparison matrix is scored against measurable requirements — not the impression left by a sales demo.
We have implemented ABACUS at several Saudi entities and integrated against Sparx EA and BiZZdesign in past engagements. The experience comes from delivery, not slides.
A Saudi team that replies in Arabic and knows DGA and NORA from daily delivery, not from a textbook. Migration from Visio, Excel, and older tools is part of the service.
A Visio drawing gives you a picture; a repository gives you an answer. When the deputy minister asks which applications depend on a specific system, nobody is going to open Visio files one by one. A real EA tool ties capability to service to application to data to process, and gives you that list in seconds.
The six names we see on shortlists: Avolution ABACUS, BiZZdesign Horizzon, Mega HOPEX, Sparx Enterprise Architect, Software AG ARIS, and LeanIX. Each one wins in a different corner — the serious comparison is built on your requirements, not on analyst rankings.
No. We are the official Avolution ABACUS Middle East partner, and the selection phase still runs neutrally. If a different tool fits the entity better, we write that in the recommendation. It has happened — usually with smaller entities whose budget doesn't justify a platform the size of ABACUS.
Eight to start with: NORA / TOGAF / ArchiMate support, Arabic, in-KSA deployment, license model, analytics, integration with CMDB / ServiceNow / Jira, 3- and 5-year TCO, and local support. Their order and weight are set by the entity, not by us.
Yes. ABACUS deploys on-premise on entity infrastructure or on an accredited Saudi cloud. The whole repository stays inside the Kingdom, so data-residency stops being an open thread on your risk register.
Base technical rollout: 4 to 8 weeks. The full thing — repository setup, training, migration — runs 3 to 6 months for a mid-sized entity. Large entities take longer.
Yes. We import from Visio, Excel, Sparx, and Mega, preserving relationships as far as the source allows. Old Visio files always lose something — we flag that up front, not afterwards.
A one-hour discovery call, no cost, that ends with an initial requirements list before we build the matrix.
Back to all services
