Six countries, one plan
The hard part of a regional archive project is rarely the architecture. It is customs, spares and residency.
United Arab Emirates, Saudi Arabia, Qatar, Oman, Bahrain and Kuwait each impose their own constraints on a storage deployment. Those constraints belong in the project plan, not in a change request.
The delivery and support model that applies to a given country and scope is confirmed per engagement, not assumed from a coverage map.
Vendor websites tend to show a map with six pins on it, which tells a buyer nothing. What determines whether a multi-country archive rollout lands on schedule is far more mundane: whether the optical media clears customs before the change window, whether a failed drive can be replaced without an international shipment, whether the regulator permits a copy to sit outside the country, and whether the operations team can read the runbook. This page sets out those realities plainly, and states where our capability is confirmed case by case rather than claimed in advance.
Delivery model is confirmed per engagement.
Delivery models across the GCC
We work through three generic models. Which one applies depends on the country, the scope, the site security requirements and the procurement route, and it is confirmed during scoping rather than promised on a web page.
Direct delivery. Aban Smart handles sourcing, shipping, installation and commissioning end to end, with our people on site for the integrate phase.
Partner-supported delivery. A local systems integrator or contractor performs the on-site work under our architecture and commissioning plan. This is common where site access requires a locally registered entity, a national vendor registration, or security clearance we do not hold.
Remote support. Configuration, monitoring, policy changes, migration supervision and troubleshooting delivered remotely, with physical tasks handled by your team or a local partner against written procedures.
Most regional programmes end up as a mix. A central archive may be direct, remote branches partner-supported, and ongoing operations remote. We would rather state the model per site in the project plan than describe a uniform presence we cannot evidence for every country.
Import, lead time and logistics realities
None of this hardware is manufactured in the region. Every appliance, library, drive and cartridge is imported, and that single fact drives most of the schedule risk.
Lead time is a real line item. Manufacturing lead time, freight and customs clearance are sequential, and the total is confirmed against the actual bill of materials during the Source phase described on how we work. We do not publish standard durations, because they change with configuration, route and season.
Optical and tape media need handling conditions. Cartridges and discs have temperature and humidity tolerances that a summer container port can exceed. Shipment method and storage on arrival are worth specifying, particularly for the media formats covered under optical archive systems.
Spares strategy has to be decided, not discovered. A drive failure two years in is a certainty, not a risk. The options are an on-site spares pool held by you, a manufacturer service agreement, or accepting an international replacement lead time. Each has a different cost and a different worst-case outage. This is agreed in writing during Design.
Data residency changes the architecture. Requirements differ across the six countries and by sector, and public-sector and financial data are usually treated more strictly than general corporate data. Where a copy may not leave the country, a cloud tier is not available as a design option and the offsite copy has to be solved with physical media or a second in-country site. Public-sector constraints are discussed further under government.
Documentation and handover may need two languages. Operational runbooks, acceptance test records and training may be required in English and Arabic. Confirm this early. Retrofitting bilingual documentation at handover delays sign-off.
Public procurement moves on its own calendar. Multi-year framework agreements, tender cycles and budget years mean the technical decision and the purchase order can be a long way apart. Designs written for these buyers should hold their validity across that gap, which means avoiding components at end of life and stating the assumptions the capacity model depends on.
What we will and will not state
We will tell you which delivery model we propose for your specific sites, and what evidence that proposal rests on. We will not publish claims about staff numbers, stock holdings or support hours in any individual country, because those are the details buyers should verify rather than take from a supplier's own marketing.
To scope a multi-country requirement properly we need the site list, the applicable residency rules and the procurement route. Discuss your GCC requirement with that information to hand, or start with an assessment of the largest site. Background on the company is on about Aban Smart.
Frequently asked questions
We do not make per-country claims about local presence, stock or support hours on this website. The delivery model for your project, including who performs on-site work in each country, is confirmed during scoping and written into the project plan. Ask us for that detail directly and we will answer it for your specific sites rather than in general.
Related pages
Turn your requirement into a defensible architecture
Share the workload, capacity, retention, access, and resilience requirements. Aban Smart will identify the next discovery inputs and the appropriate engagement path.