Sultan Haitham City, Oman
Smart city technology strategy and infrastructure engineering for a 1,570-hectare greenfield city.
Led the smart city infrastructure engineering workstream for Sultan Haitham City. The 1,570-hectare greenfield development is designed as Oman's new national capital. Set the technology design for smart mobility, utilities and the ICT backbone. It also covered environmental monitoring and joined-up city services. Built the vendor evaluation framework and the baselines for buying technology. These cover the city's infrastructure systems for its whole life, from construction through to full operations.
Sultan Haitham City needed a coherent smart city technology strategy before any infrastructure could be bought. The 1,570-hectare greenfield site came with a national mandate. The technology had to cover mobility, utilities and digital links. It also had to cover environmental monitoring and city operations. Each area needed specs ready for tender and a way to choose vendors.
Led smart city systems design across the full technology stack. That covered mobility and traffic management, utility SCADA integration, and the ICT backbone and connectivity. It also covered environmental sensor networks and the integrated city operating model. Set technology baselines for each area, criteria for judging vendors, and specs for how the systems connect. Worked across engineering disciplines so the technology plan kept pace with the civil and structural planning stages.
The smart city technology masterplan became the procurement baseline for the city's infrastructure. The client adopted the vendor evaluation frameworks to pick technology partners in each area. The integrated city operating model was lined up with the national ICT strategy. It was handed to the client's operations team before the city went into service.
- My role
- Led smart city systems design across the full technology stack, Meinhardt Group
Planning a city's technology from a blank slate is the same problem any growing business faces with its own systems. What you choose in year one decides what is possible (or impossible) in year five. The same way of judging vendors, making integration choices and modelling lifecycle cost applies to both. That holds whether you are specifying city-scale ICT or choosing your next business platform.
Smart City Technology Architecture Framework
The domain-by-domain technology architecture used for Sultan Haitham City: how to structure a multi-domain smart city technology strategy covering mobility, utilities, ICT backbone, environmental monitoring, and integrated operations. Includes the vendor evaluation framework, integration architecture principles, and the decision sequence for building procurement-ready specifications across each smart city domain.
The same diagnostic logic from deployments like this one, applied to your business in half a day.
Book the WorkshopDiscuss a similar programme- Sultan Haitham City: 1,570-hectare greenfield development designated as the future capital of the Sultanate of Oman
- Employer testimonial letter from Meinhardt SUIT Pte Ltd (Managing Director, July 2025) naming this project available to procurement teams on request; not published online
- Employer testimonial letter from Meinhardt (Singapore) Pte Ltd (Group Director, December 2022) naming this project available to procurement teams on request; not published online
Other projects
Operations & SecuritySultan Haitham City IOCC, Oman
City-scale integrated operations control for a new urban development.
Read case study →
Enterprise AIAI-Enabled Enterprise Operations Platform
One ERP that brings project management, finance, HR and real-time BI into a single system.
Read case study →
InfrastructureDIFC Enterprise Campus Network Design Review
Independent peer review that set the technical baseline for DIFC 2.0 network infrastructure.
Read case study →
Bare desert doesn't hand you an existing city's systems to borrow from. Building a national capital there means arguing every choice on mobility, utilities and connectivity from first principles. Engineers from half a dozen disciplines sat in the same room. The vendor evaluation sessions ran late more than once, because nobody wanted to be the one who picked wrong on a fifty-year asset. That care is why the framework became the client's own procurement standard rather than staying my document.
