Smart Building Design for Lusail New City Development

Lusail is being built as a planned city rather than an incremental extension of Doha, which changes what "smart building" means in practice. A tower in Lusail is expected to participate in district-level infrastructure, not just run its own systems well. This guide covers integrated ELV, ICT and building management design for Lusail developments — the architecture that makes a building genuinely operable, and the decisions that quietly determine whether the smart features still work in year five.

What Actually Makes a Building Smart

Most "smart building" specifications fail for the same reason: they procure intelligent subsystems that cannot share data. The building ends up with a sophisticated BMS, a sophisticated lighting system and a sophisticated metering system, each with its own interface, none of which can answer a simple operational question like which floors are driving the evening cooling load.

A genuinely integrated design has three layers, and the design responsibility is to specify all three rather than only the first:

1. Field layer — sensors, meters, actuators, controllers. What the building can sense and act on
2. Network layer — a converged IP network carrying all of it, with appropriate segmentation. How the data moves
3. Application layer — the integration platform, analytics and dashboards. How the data becomes a decision

Converged Network Architecture

Running separate physical networks for BMS, security, AV, lighting and guest/tenant data is still common and is almost always the wrong answer for a new Lusail development. It multiplies containment, switch count, cost and maintenance burden.

The better pattern is a single converged physical network with logical separation:

BMS and Controls Design

Open Protocols, Specified Properly

Specifying "BACnet compatible" achieves very little — nearly everything claims it. The specification needs to state what must be exposed:

• BACnet/IP at the supervisory level, with a published, complete object list for every controller
• A point schedule issued as a design deliverable, naming every point, its type, units, and whether it is read-only or commandable
• Written confirmation that the client owns the point database and graphics, and can appoint a different maintenance contractor without relicensing
• No proprietary gateway as the only route to data — if the only way to read the chiller plant is through one vendor cloud, the building is locked in

Metering Strategy

Sub-metering is the foundation of every energy narrative the building will later want to tell — operational cost allocation, sustainability reporting, and any certification target. Design it in; it is disproportionately expensive to retrofit.

• Landlord and tenant electrical separation at minimum, tenant-by-tenant where leases require it
• Major plant metered individually: chilled water energy transfer, pumps, AHUs, lifts, external lighting
• Chilled water energy meters at the district cooling interface and at major branch level
• Water sub-metering by tenancy and by major use — cooling makeup, irrigation, domestic
• All meters on the converged network, polled into the integration platform, not read manually

Lighting Control and Daylight in Qatar Conditions

Qatar has abundant daylight and a strong cooling penalty for solar gain, which makes lighting and shading control a combined problem rather than two separate ones.

• DALI-2 addressable control for perimeter and open-plan zones, giving per-luminaire dimming and status reporting
• Daylight harvesting on perimeter zones — genuinely effective given Qatar light levels, provided sensors are commissioned rather than left at factory defaults
• Occupancy and vacancy sensing in cellular offices, meeting rooms, back-of-house and toilets
• Automated shading integrated with the lighting and BMS logic, so shades close against solar gain before cooling load rises rather than after occupants complain
• Scene control in shared and amenity spaces, exposed to the integration platform so scenes can be scheduled

The Integration Platform

This is the layer most often omitted from the ELV scope and then missed badly in operation. An independent supervisory platform sits above the subsystems and provides:

• A single operator interface across BMS, metering, lighting, security status and lift monitoring
• Cross-system logic — for example, a floor showing zero access-control entries after 20:00 can have its cooling set back automatically
• Trend logging with enough retention to support analysis, not just live values
• Alarm management with prioritisation and escalation, so genuine faults are not lost in nuisance alarms
• Reporting for energy, comfort complaints and asset performance

Specify it as vendor-neutral and IP-based, with the client owning the configuration. The platform outlives individual subsystem contracts.

Designing for Change

Lusail buildings are being handed over into a district that is still developing. The infrastructure decisions with the longest shadow:

• Containment capacity — design tray and riser at 40% fill, not full. Every future system needs a route
• Spare structured cabling — pre-cable roughly 30% more AP and device positions than day-one requirements
• Single-mode fibre riser — no bandwidth ceiling, upgrade by changing optics only
• Spare switch capacity and PoE budget — sized for growth, not exactly to day-one device count
• Plant room and telecom room space — leave rack positions and floor area free
• Documented, owned configuration — point lists, graphics, network diagrams and credentials handed over to the client, not retained by the installing contractor

Cyber Security for Building Systems

Converging networks makes segmentation and hygiene a design responsibility rather than an IT afterthought.

• Building systems on isolated VLANs with explicit, minimal inter-VLAN rules
• No default credentials anywhere — make credential change a documented commissioning checkpoint
• Remote vendor access through a managed, logged, time-limited path, never an open port
• A patching responsibility named in the maintenance contract; unpatched controllers are the common weak point
• Network access control on building-system switch ports so an unauthorised device cannot simply be plugged in
• Backup of controller configuration and graphics, stored by the client rather than only by the contractor

Recommended Design Sequence

1. Concept: Agree the integration ambition and which systems must share data. This drives everything downstream
2. Scheme: Network architecture and VLAN strategy, metering strategy, telecom and plant room provision
3. Detailed design: Point schedules, containment and fill calculations, device layouts, integration matrix
4. Coordination: Federated BIM clash resolution, district cooling interface confirmation, Civil Defence life-safety review
5. Tender: Open-protocol requirements, ownership clauses, commissioning and re-commissioning scope written in
6. Handover: Witnessed integration testing, tuned set points, full documentation transfer to the client

Summary

A smart building in Lusail is defined by its integration architecture, not by its device list. The decisions that matter are made early: a converged network with disciplined segmentation, life safety kept genuinely independent, open protocols with client-owned configuration, metering designed in from the start, and containment and cabling capacity left deliberately spare. Add a commissioning regime that actually tunes the control strategies, and the building will still be performing as designed when the district around it is finished.