Digital twin GCC: from single developments to smart cities

One idea, three very different buyers

A digital twin GCC buyer might be any of three people, and they need different things from the same technology.

The building. A facility manager wants to see where assets are, what state they are in and what has been done to them. The twin is a navigable 3D model of the building connected to asset registers and, where available, the building management system.

The development or campus. A master developer or university has many buildings, many contractors and a long life. The twin is a shared picture for sales, planning and operations: which areas are live, in progress or planned, and who is responsible for each.

The city or district. An authority or operator wants a planning and coordination layer across many owners. This is the hardest scale, because the value depends on data agreements between organisations more than on the model.

Most of the regional appetite we see is for the first two. They have a clear owner, a clear question and a manageable scope. The third scale usually begins as a number of the first two that someone later wants to join up, which is a good reason to choose open, well-documented data structures from the start.

Why the Gulf is asking

National visions across the region put digital transformation, tourism and knowledge industries on the agenda, from UAE Centennial 2071 and the Dubai metaverse strategy to Qatar National Vision 2030, Kuwait Vision 2035, Bahrain Economic Vision 2030, Oman Vision 2040 and Saudi Vision 2030. We do not interpret them for clients. We note that organisations building districts, campuses and towers within such programmes need a way to see and manage many things at once, in two languages, for owners who will change over decades.

That is also why the twin is an operations question before it is a graphics question. A model that looks impressive on day one and is out of date by month six has failed. We have written about the same point for Saudi developments, and it holds everywhere: the first design question is who updates the twin and from what source.

The four layers of a working twin

1. Geometry. Surveyed or BIM-based 3D models at the level of detail the questions need. BIM integration is the natural route for new buildings; older ones may need survey.
2. Information. Asset registers, drawings, maintenance history and status data from building systems, linked to the objects in the model.
3. People. Roles, permissions and, where useful, avatars. A contractor opens one zone; an operator opens another; a guest sees only the showroom.
4. Applications. The views people actually use: a sales showroom, an operations dashboard, a planning review, a visitor guide.

Each layer has an owner. Write the owners down before any modelling begins.

Data ownership comes before the model

The questions that delay Gulf twin projects are seldom technical. Where will the data be hosted? Who may see which layer? Which systems does it touch, and which does it never touch? Who owns the model and the content when the contract ends? Organisations also care about data sovereignty, and we treat it as a design requirement rather than a footnote.

For a digital twin UAE developers commission, or a digital twin Qatar operators plan, our advice is to settle these in a scoping workshop before modelling. Give the client the model, the content and the user identities. Use role-based access. Keep the twin's connections to live systems read-only until the team has trust in the workflow. And name, in writing, who is responsible for keeping each layer current, because a twin does not update itself.

How to read a smart-city twin proposal

Smart-city language invites exaggeration, and a buyer should test every proposal with three questions. What is live? Ask which data feeds are connected today and which are planned; a rendered city with no feeds is a visualisation. What is modelled, and to what detail? A district model with block massing is useful for planning and useless for maintenance. Who keeps it current? A twin without an owner decays.

A fourth question matters in the Gulf: what happens at the boundaries between owners? Developers, operators and authorities each hold part of the data, and agreements between them often take longer than the modelling. We would rather say at the start that a city-scale programme is an agreements problem first, and start with the smallest scope that one organisation can own. If you are comparing vendors, ask each to show one twin that is live and in daily use, and to explain who maintains it.

The cost of keeping a twin alive

The modelling is a project; the twin is a service. After handover, someone updates drawings, records changes, onboards users and fixes broken links to data sources. Budget for that from the beginning. For a single building this may be a part-time responsibility inside the facilities team. For a development it becomes a small team with a named lead.

We train the client's staff and hand over the content tools so the client is not dependent on us for every change. Where a client prefers ongoing support, we can provide it remotely. Either way, the twin should be reviewed on a schedule, because the test of a good twin is whether operators reach for it on an ordinary Tuesday. Ask them what they opened last week. If the answer is nothing, fix the twin or retire it, rather than paying to keep an impressive model nobody uses.

One model, a sales life and an operations life

A twin earns its cost twice if it is planned that way. Before construction, the same model can become a virtual showroom for buyers, investors and tenants, who walk the development before it exists. During construction, it becomes a planning and coordination view. After handover it becomes the facility model. Our digital twin product page describes the delivery, and the university campus case shows a whole site modelled as a twin with students and teachers present as avatars.

The immersive views are windows on the same twin. A headset suits rehearsal and review, a phone or tablet suits the site with an augmented overlay, and a browser suits everyone else. Our article on VR, AR and mixed reality for facilities goes through them.

How a UAE or Qatar twin project starts, remotely

A digital twin UAE client and a digital twin Qatar client start the same way. We serve the GCC from Amman and Riyadh and have no office, client or installed twin in the UAE, Qatar, Kuwait, Bahrain or Oman. A project starts with a video workshop to agree the questions the twin must answer. The client shares drawings, models and photographs, and our studio builds one building or one zone first. Connections to building systems are made by the client's own integrator to an interface we agree. We review with the people who will use it daily, and then extend to the next zone.

That gives a result in one area before anyone commits to the whole site, which is how a digital twin GCC programme should start. Our digital twin services page lists the delivery, and country detail sits on our UAE and Qatar pages.