A forty-storey tower is not a low-rise building with more floors. Height changes the ICT problem qualitatively: the service entry becomes a single point of dependency, riser space competes with every other service, telecom rooms must stack vertically or the backbone dog-legs, mobile coverage fails without deliberate in-building infrastructure, and multi-tenant occupancy demands distribution that can be subdivided without rework. This guide covers ICT infrastructure design at building scale for Doha and Lusail high-rise projects — the architecture decisions made before anyone selects a cable category.
Quick Answer
High-rise ICT design in Qatar is governed by four building-scale decisions: where the service provider enters and whether that entry has diversity; how the vertical backbone is routed and how many risers exist; whether telecom rooms stack vertically floor-to-floor; and how in-building mobile coverage is delivered. Each must be fixed at concept, because all four are constrained by the core layout and none can be changed economically afterwards.
Contents
- Why height changes the problem
- Service provider entry and diversity
- Vertical backbone and riser strategy
- Telecom room stacking
- Floor distribution and the 90 m envelope
- In-building mobile coverage
- Multi-tenant distribution
- Life-safety systems in the riser
- Coordination sequence
- Design checklist
- Common design mistakes
- FAQs
Why Height Changes the Problem
| Factor | Low-rise | High-rise consequence |
|---|---|---|
| Service entry | One entry, short route | Single point of failure for the whole tower; diversity becomes a real question |
| Backbone | Short, often horizontal | Long vertical runs; riser space contested by every discipline |
| Telecom rooms | One or two | One per floor or more; alignment across floors becomes critical |
| Mobile coverage | Usually adequate from macro network | Upper floors and core areas typically need in-building infrastructure |
| Occupancy | Single or few tenants | Multi-tenant subdivision over the building's life |
| Life safety | Simple | Phased evacuation, riser survivability, pressurisation interfaces |
Service Provider Entry and Diversity
The building entrance facility is where external network becomes building infrastructure — and in a tower it is a concentration of risk.
What must be established at concept, directly with the telecom service provider:
- Entry room dimensions and location relative to the site boundary — set by the provider, not the design team
- Number, size and route of incoming ducts from the street
- Demarcation point — where provider responsibility ends and building infrastructure begins, explicit on the drawings
- Whether diverse entry is required — two physically separated entry paths from different directions
External duct routing to the boundary must also be coordinated against Ashghal's underground utility network requirements, which govern crossings through public utility corridors.
Vertical Backbone and Riser Strategy
How many risers, and where, is the highest-consequence ICT decision in a tower.
Single versus dual riser
| Arrangement | Resilience | When appropriate |
|---|---|---|
| Single ICT riser | Any riser incident affects the whole tower | Smaller towers, single-tenant, cost-constrained |
| Dual riser, same core | Protects against local damage, not core-wide events | Common compromise |
| Dual riser, separate cores | Genuine path diversity vertically | Multi-tenant prime commercial, high-availability occupiers |
Backbone design points:
- OS2 single-mode fibre for the vertical backbone. Upgrades happen by changing transceivers rather than pulling new riser cable — decisive over a tower's service life
- Strand count sized for the building's life, not day one. Incremental strands are cheap at installation and disproportionately expensive later. Include dark fibre allowance
- Where dual risers exist, split the backbone across both — two risers carrying a single logical path deliver no resilience
- Intermediate distribution — in very tall towers, a mid-level equipment room shortens runs and provides an aggregation point, at the cost of a second conditioned space
Telecom Room Stacking
Telecom rooms should sit in the same plan position on every floor. Unstacked rooms force the riser to dog-leg horizontally at each transition — consuming ceiling void, creating clashes with mechanical services, and adding length and loss to every backbone run.
This is easy at concept and near-impossible later, because it is an architectural constraint on the core, not an ICT one. It must be raised while floor plates are still being developed.
Floor Distribution and the 90 m Envelope
Each floor's telecom room must reach every outlet within a 90 m permanent link, measured along the actual cable route.
On large Qatar floorplates — the deep plates common in West Bay and Lusail — a single central TR frequently cannot reach the far corners once routing is counted honestly. The options, in order of preference:
- Reposition the TR while the core is still fluid
- Add a second TR on affected floors, accepting the space and cooling cost
- Restrict outlet positions — rarely acceptable to the tenant
What is not an option is an out-of-standard channel. It will fail certification, and the failure surfaces at handover when remedy is most expensive.
Capacity planning per floor
- Workstation outlet density agreed with the client's workplace strategy, not assumed
- Wireless AP positions at the densities modern deployments require, with two runs per position
- Pre-cable roughly 30% more AP positions than day-one count
- Security devices — cameras, readers, intercoms — on the same infrastructure, with their PoE load included in the switch budget
- Switch PoE budget checked at the switch level, not just per port: a fully loaded switch of Type 3/4 devices can exceed total budget with no individual port over-subscribed
In-Building Mobile Coverage
Tower construction — reflective glazing, concrete cores, deep floor plates — attenuates mobile signal severely. Upper floors, basements, lift cars, stair cores and central zones commonly have inadequate coverage from the macro network alone.
This matters beyond convenience: occupants increasingly rely on mobile as primary voice, and emergency responders need coverage in exactly the areas that perform worst.
Design implications to fix at concept:
- Decide early whether in-building coverage infrastructure is required — it needs riser space, equipment room space and power, all of which compete with other services
- Coordinate with mobile operators early; their requirements shape the head-end room and the distribution approach
- Reserve riser and containment capacity even where the system is a later fit-out. Retrofitting coverage into a fully occupied tower with no reserved pathway is the expensive path
- Lift car coverage requires specific coordination with the lift contractor
Multi-Tenant Distribution
A tower's tenancy will subdivide and recombine over its life. Infrastructure that assumes a fixed demise will be rebuilt repeatedly.
- Landlord and tenant boundaries defined in the design — where base-build infrastructure ends and tenant fit-out begins
- Rack space allocation in each TR for tenant equipment, with physical security separation where leases require it
- Tenant access to the TR — an access control and operational question as much as a cabling one
- Separate pathways for tenant-specific cabling, so one tenant's fit-out does not disturb another's live services
- Riser capacity for tenant-dedicated backbone where high-demand tenants need their own fibre to the ER
Life-Safety Systems in the Riser
Fire alarm, voice alarm and emergency communication cabling share the building's vertical routes but not its rules.
- Survivability — circuits that must operate during a fire have cable type and routing requirements that ordinary data cabling does not
- Compartment penetrations — every riser penetration needs firestopping, detailed at design stage and coordinated with Civil Defence requirements
- Segregation from general data containment where required by the fire strategy
- Phased evacuation interfaces — tall buildings commonly use phased strategies, which the QCDD-approved cause-and-effect matrix must implement precisely
- Stair pressurisation and smoke control interfaces triggered from the fire alarm system
Coordination Sequence
- Concept — service entry position and diversity; riser count and position; TR stacking; in-building coverage decision. All four are architectural
- Scheme — backbone strand counts, floor densities, AP grid, equipment room sizing
- Detailed design — containment routes and fill, TR elevations, rack layouts, riser diagrams
- Coordination — clash detection against MEP in the federated model; ceiling void resolution before IFC
- Tender — specification, BOQ, labelling scheme, test regime issued together
- Construction — RFI response, shop drawing review, witnessed testing, as-built verification
High-Rise ICT Design Checklist
- ☐ Service provider engaged at concept; entry room, ducts and demarcation confirmed
- ☐ Entry diversity requirement decided while core planning is still fluid
- ☐ External duct routing coordinated against Ashghal utility corridor requirements
- ☐ Riser count and positions fixed; dual-riser split genuinely separate if resilience claimed
- ☐ Telecom rooms stacked in the same plan position on every floor
- ☐ Kahramaa electrical room approval sequenced before adjacent TR layout frozen
- ☐ 90 m envelope verified per floor on routed distance
- ☐ Backbone strand count includes dark fibre allowance
- ☐ Single-mode fibre specified for vertical backbone
- ☐ Dedicated cooling and two power circuits per TR
- ☐ In-building mobile coverage decision made; riser and room capacity reserved
- ☐ Lift car coverage coordinated with lift contractor
- ☐ Landlord/tenant boundary defined; tenant rack space allocated
- ☐ Life-safety circuit survivability and segregation coordinated with fire strategy
- ☐ Firestopping detailed at every riser penetration
- ☐ Containment at 40% fill with spare capacity for future systems
Common Design Mistakes
- Service provider engaged after the core is fixed. Their entry room requirement then forces a compromise or a redesign.
- Diversity claimed but not delivered. Two ducts in one trench, or two risers in one core, is not path diversity.
- Telecom rooms unstacked. Forces dog-legged risers, clashes and wasted containment on every floor.
- 90 m assessed as straight-line. Real routing on a deep plate is substantially longer.
- Riser sized for day-one strand count. No dark fibre, so growth means new riser cable.
- Multimode backbone in a tall riser. Caps the tower for a marginal saving.
- In-building coverage treated as a later problem. No reserved riser or room space, so retrofit is disproportionately expensive.
- Unconditioned telecom rooms. Qatar ambient plus PoE load shortens equipment life materially.
- PoE budgeted per port, not per switch. Fully loaded switches exceed total budget with no port over-subscribed.
- No landlord/tenant boundary defined. Every fit-out becomes a negotiation and a disturbance risk.
- Life-safety cabling treated as ordinary data cabling. Survivability and segregation requirements missed.
- Firestopping deferred to site. A Civil Defence coordination item, not a site detail.
- AP positions relocated on site to dodge ductwork. Devices end up outside their designed coverage cell.
- No spare containment capacity. Every future system needs a route, and there isn't one.
Need ELV & ICT Design Support for a Qatar High-Rise?
ASDV Consultant provides specialist ICT infrastructure design for architects, MEP consultants, developers and contractors on Doha and Lusail tower projects — service entry strategy, riser design, telecom room provision, floor distribution, BOQ and coordination support.
Enquire About ICT Design →Frequently Asked Questions
How many telecom rooms does a Qatar high-rise need?
At minimum one per floor, positioned so every outlet falls within a 90 m routed permanent link. Deep floor plates commonly need two. There is no fixed number — it follows from plate geometry and routing, which is why it must be checked at concept.
Is dual riser required by Qatar regulation?
No. Riser resilience is a project specification and business-continuity decision, not a Qatar authority requirement. The exception is life-safety circuits, whose routing and survivability are governed by the fire strategy and Civil Defence requirements.
When should the telecom service provider be engaged?
At concept. Their entry room dimensions, duct requirements and riser provisions are spatial constraints on the core — discovering them after the core is fixed forces compromise.
Do telecom rooms really need dedicated cooling in Qatar?
Yes, as engineering practice. Qatar ambient conditions combined with PoE switch heat load in an unventilated riser cupboard shorten equipment life significantly. This is one of the most common provisioning failures on Qatar towers.
Is in-building mobile coverage infrastructure mandatory?
Requirements depend on the building, its occupancy and the operators involved — confirm with the mobile operators and the project specification. Regardless of obligation, tower construction attenuates signal enough that coverage is usually a practical necessity, so reserve riser and room capacity even if the system is a later fit-out.
How much dark fibre should the riser carry?
Enough that growth over the building's life does not require pulling new riser cable. The exact count is a project judgement based on tenancy strategy and expected density; the principle is that strands are cheap at installation and expensive afterwards.
Can one riser carry both data and life-safety cabling?
Sometimes, but not by default. Survivability, segregation and firestopping requirements for life-safety circuits are set by the fire strategy and Civil Defence requirements, and must be confirmed rather than assumed.
What is the single most expensive high-rise ICT mistake?
Unstacked telecom rooms, or a service entry position fixed without provider input. Both are architectural, both are cheap to get right at concept, and neither can be corrected economically once the core is built.
Related Qatar Technical Guides
- Structured cabling design in Qatar — media, telecom rooms, testing and the Ashghal/Kahramaa constraints in detail
- Data center design in Qatar — where tower ICT meets facility-grade infrastructure
- Qatar Civil Defence fire alarm requirements — riser survivability and evacuation interfaces
- Qatar building code compliance and Ashghal QCS standards
References & Technical Resources
- Telecom service provider — entry room, duct entry, riser and demarcation requirements, obtained directly.
- Ashghal (Public Works Authority) — Underground Utility Network design guidelines for external duct crossings.
- Kahramaa — electrical room siting and layout approval requirements.
- Qatar Civil Defence Department — life-safety circuit, survivability and firestopping requirements.
- TIA-569 — pathways and spaces, including riser and telecom room provision. Confirm edition.
- ISO/IEC 11801 — generic cabling; confirm applicable part and edition.