Acknowledgements

Dubai Design District (d3) would like to express its heartfelt gratitude and appreciation to all
entities and individuals who have contributed to this study. A lot of diligent work and concerted
efforts has gone into developing this document, and making a list of all contributors is virtually
impossible. However, we would like to specifically mention the following:

 Smart Dubai Government, for granting d3 the privilege of being a Strategic Partner to
them and for supporting the outcome of this study.
 Tecom Group Senior Management Team for their forward-looking understanding of what
this document aims to achieve, and for promptly sanctioning the study and supporting
the initiative at critical times.
 Cisco Consultancy Services Dubai for bringing their expertise and knowledge to this
comprehensive document.

© Dubai Design District, All rights reserved. Page 1 of 291

 Overview
Dubai Design District (d3) has worked closely with Cisco to create a comprehensive set of
guidelines for the development of a Smart City-wide technology infrastructure and network
architecture. A first-of-its-kind effort developed in the United Arab Emirates, this document
provides guidelines for building Smart City ICT infrastructure. This offers a new approach and a
blueprint for Smart Cities to support the promise of smart urban technologies and solutions that
fuel sustainable development and a high quality of life with wise management of a city’s assets.
Although the document is specific to d3 Smart City development, the stated principles can be
applied to any new development which aspires to be a Smart City. Likewise, references to Data
Virtualization are very specific to d3 and other technical solutions for a data platform can be
applied equally well. Setting a new precedent for the development of Smart Cities, these
guidelines ensure that ICT infrastructure is considered a top priority in the early stages of planning
a city or urban community.
These guidelines factor in urban planning and development considerations for the integration of
smart urban technologies and their possible implications in shaping the environment to produce
prosperous and sustainable urban futures. Ensuring that the infrastructure developed for Dubai
meets the metrics and objectives outlined by Smart Dubai’s Vision, the guidelines serve as a
governance model which developers are able to practically apply on the ground. Beyond
facilitating design and construction work, this document also factors in the critical role of
technology in creating people-centred cities that offer innovative engagement and participatory
mechanisms, which lead to happier, more prosperous urban communities.
These guidelines help avoid the common pitfall of multiple parties working in silos, which results
in independent, unconnected and un-converged ICT infrastructures. This document can be used
as addendum to standard developer guidelines that the construction industry is accustomed to
using to ensure alignment and assist in working towards a common vision. From master planners,
consultants and contractors to systems integrators, vendors and telecom & utility service
providers – a wide array of stakeholders are involved in the development of a Smart City and
stand to benefit greatly from these guidelines. The aim is to ensure that the City and its building
infrastructure are Smart enough to deploy new and innovative services with ease, speed and
minimal disruption.

Feedback and suggestions related to this document can be emailed to:

smartcity@[Link]

Version: 2.1 – Public Release

Copyright: Dubai Design District, 2016

© Dubai Design District, All rights reserved. Page 2 of 291

 Table of Content
1 Background ...................................................................................................................... 15
1.1 Dubai Design District ........................................................................................... 15
1.2 Project Objectives ................................................................................................ 15
2 Introduction ....................................................................................................................... 17
2.1 Purpose of the Document .................................................................................... 17
2.2 Methodology and Assumptions ............................................................................ 17
2.2.1 Methodology ..................................................................................................... 17
2.2.2 Assumptions..................................................................................................... 20
2.3 Scope of the Document........................................................................................ 20
3 Smart City Architecture ..................................................................................................... 22
3.1 Reference Smart City Architecture ....................................................................... 22
3.2 Automation: an Essential Enabler in Smart City Maturity Model ........................... 24
3.3 d3 Smart City Functional Framework ................................................................... 25
3.3.1 Foundational Layer ........................................................................................... 26
3.3.2 Convergence Layer .......................................................................................... 26
3.3.3 Business / Transformational Layer ................................................................... 33
3.3.4 Operations and Security Layer ......................................................................... 33
3.4 d3 ICT Review ..................................................................................................... 34
4 ICT Guidelines for Building Systems in d3 ........................................................................ 35
4.1 Inside Plant Best Practices .................................................................................. 35
4.1.1 Assumptions and Caveats ................................................................................ 36
4.1.2 Telecommunication Spaces.............................................................................. 36
4.1.3 Structured Cabling ............................................................................................ 50
4.1.4 ISP No Objection Certificate Requirements ...................................................... 69
4.2 Connected Real Estate Basis of Design ............................................................... 71
4.2.1 HVAC Control ................................................................................................... 71
4.2.2 Lighting Control ................................................................................................ 76
4.2.3 Smart Metering ................................................................................................. 80
4.2.4 Access Control ................................................................................................. 83
4.2.5 Video Surveillance ............................................................................................ 89
4.2.6 Car Parking ...................................................................................................... 95
4.2.7 Digital Signage ............................................................................................... 100
4.2.8 Audio/Video .................................................................................................... 106
4.2.9 Life Safety ...................................................................................................... 113
4.2.10 Elevators and Escalators ................................................................................ 113
4.2.11 Public Address/Background Music (PA/BGM) ................................................ 114

© Dubai Design District, All rights reserved. Page 3 of 291

 4.2.12 Solar Panels ................................................................................................... 115
4.2.13 Smart home.................................................................................................... 117
4.2.14 Point of Sale ................................................................................................... 119
4.2.15 Potable Water Tank Quality Control ............................................................... 119
5 ICT guidelines for Municipal Systems in d3 ..................................................................... 120
5.1 City-Wet Utilities................................................................................................. 120
5.1.1 Potable Water Network................................................................................... 120
5.1.2 Sewage Waste Network ................................................................................. 123
5.1.3 Storm Drainage Network ................................................................................ 125
5.1.4 Fire Fighting Network ..................................................................................... 127
5.1.5 Irrigation Water Network ................................................................................. 129
5.2 City-Dry Utilities ................................................................................................. 131
5.2.1 Electrical......................................................................................................... 131
5.2.2 Street Lighting ................................................................................................ 132
5.2.3 Telecom: Outside Plant Passive Infrastructure guidelines for d3 .................... 133
5.2.4 Telecom: ISP guidelines for DC and PoPs in d3 ............................................. 149
5.3 Other City Systems ............................................................................................ 172
5.3.1 Traffic Lights ................................................................................................... 172
5.3.2 Outdoor Sensors ............................................................................................ 173
5.3.3 Weather Station.............................................................................................. 175
5.3.4 Connected Bus ............................................................................................... 176
5.3.5 Connected Garbage Bins ............................................................................... 178
5.3.6 Vehicle Tracking ............................................................................................. 180
5.3.7 Electric Vehicle Charging Stations (EVCS) ..................................................... 182
5.3.8 Bus Shelter..................................................................................................... 185
5.3.9 Advanced Parking Management..................................................................... 186
5.3.10 Miscellaneous Services .................................................................................. 188
6 ICT Network Infrastructure guidelines for d3 ................................................................... 189
6.1 Hierarchical Design guideline ............................................................................. 189
6.1.1 Design Considerations for d3 Network ........................................................... 190
6.1.2 Functions of the Access Layer........................................................................ 197
6.1.3 Function of the Distribution Layer ................................................................... 199
6.1.4 Function of the Core Layer ............................................................................. 201
6.1.5 d3 Smart City Data Centre concept design ..................................................... 203
6.1.6 Wireless Network ........................................................................................... 206
6.2 IP Network Management.................................................................................... 209
6.2.1 The ONM Motivators ...................................................................................... 209
6.2.2 ONM Blueprint Design Goals.......................................................................... 209

© Dubai Design District, All rights reserved. Page 4 of 291

 6.2.3 The ONM Functional Architecture .................................................................. 209
6.2.4 NMS Components, Features and Functions ................................................... 210
6.3 IP Network Security ........................................................................................... 214
6.3.1 Developing a Strong Security Policy ............................................................... 214
6.3.2 Network Based Service Concepts .................................................................. 215
6.3.3 Internet Block ................................................................................................. 216
6.3.4 VPN Service ................................................................................................... 217
6.3.5 Email Security ................................................................................................ 218
6.3.6 Intrusion Prevention System ........................................................................... 218
6.3.7 Access and Distribution .................................................................................. 218
6.3.8 Security Management..................................................................................... 219
7 Green ICT Guideline ....................................................................................................... 220
7.1 Purpose ............................................................................................................. 220
7.2 Scope ................................................................................................................ 220
7.3 Design Overview ................................................................................................ 220
7.4 Topological Overview ......................................................................................... 221
7.5 Energy Metrics ................................................................................................... 223
7.6 ICT Assets ......................................................................................................... 225
7.7 Communication Protocols .................................................................................. 225
7.8 Data Aggregation ............................................................................................... 226
7.9 Energy Domains ................................................................................................ 227
7.9.1 Parent, Child and Entity Hierarchy .................................................................. 228
7.9.2 Availability Awareness .................................................................................... 228
7.9.3 Domain Association ........................................................................................ 228
7.10 Dependency Mapping ........................................................................................ 229
7.11 Control Policies .................................................................................................. 230
7.12 Reporting ........................................................................................................... 231
7.13 Utilization Management...................................................................................... 232
7.14 Architectural Modelling ....................................................................................... 233
7.15 Building Management System Interface ............................................................. 234
7.16 User Interface .................................................................................................... 234
8 Leading Building and Energy Certifications ..................................................................... 236
8.1 LEED ................................................................................................................. 236
8.1.1 The benefits of LEED certification .................................................................. 236
8.1.2 Process to achieve LEED certification ............................................................ 237
8.1.3 Tips for Getting LEED Certified: ..................................................................... 237
8.2 Green Globes .................................................................................................... 238
8.2.1 Benefits of Green Globes ............................................................................... 238

© Dubai Design District, All rights reserved. Page 5 of 291

 8.2.2 Process to achieve certification ...................................................................... 239
8.3 Estidama ............................................................................................................ 239
8.3.1 Steps to achieve certification .......................................................................... 240
8.4 Emirates Energy Star ......................................................................................... 240
8.4.1 Steps to achieve certification .......................................................................... 241
8.5 WCCD ISO ........................................................................................................ 242
8.5.1 WCCD ISO 37120 Certification Levels ........................................................... 242
8.5.2 Benefits of WCCD ISO 37120Certification ...................................................... 243
9 Gap and Impact Analysis ................................................................................................ 244
9.1 In building Systems ............................................................................................ 244
9.1.1 ICT Inside Plant .............................................................................................. 244
9.1.2 Building Systems ............................................................................................ 245
9.2 Municipal Systems ............................................................................................. 245
9.2.1 City Wet Utilities ............................................................................................. 245
9.2.2 City Dry Utilities .............................................................................................. 246
9.2.3 Outside Plant Network .................................................................................... 246
9.2.4 Other City Systems ........................................................................................ 247
9.3 Smart City ICT Network ..................................................................................... 247
10 DGD Action Plan ............................................................................................................. 250
10.1 Relevant Sections .............................................................................................. 250
10.2 Smart City No Objection Certificate .................................................................... 251
10.2.1 Design and Construction NOC ....................................................................... 251
10.2.2 Material NOC ................................................................................................. 251
10.2.3 NOC Validity ................................................................................................... 251
10.2.4 Site Inspections .............................................................................................. 251
10.2.5 Handover and Acceptance ............................................................................. 252
10.2.6 Sub-Contracting ............................................................................................. 252
11 Appendix–A Smart City Case Studies ............................................................................. 253
11.1 Summary of Smart Cities ................................................................................... 253
11.2 Barcelona, Spain................................................................................................ 253
11.2.1 Challenge ....................................................................................................... 253
11.2.2 Solution .......................................................................................................... 254
11.2.3 Results ........................................................................................................... 254
11.2.4 Technical Implementation ............................................................................... 256
11.3 Mississauga, Canada ......................................................................................... 257
11.3.1 Challenges: .................................................................................................... 257
11.3.2 Solutions: ....................................................................................................... 257
11.3.3 Results ........................................................................................................... 258

© Dubai Design District, All rights reserved. Page 6 of 291

 11.4 Rivas, Spain....................................................................................................... 259
11.4.1 The Rivas Digital City Project ......................................................................... 259
11.4.2 Benefits .......................................................................................................... 261
11.5 Songdo, South Korea......................................................................................... 263
11.5.1 Business Need ............................................................................................... 263
11.5.2 Solution .......................................................................................................... 263
11.5.3 Benefits .......................................................................................................... 263
11.6 Amsterdam ........................................................................................................ 264
11.6.1 Challenges ..................................................................................................... 264
11.6.2 Solution .......................................................................................................... 264
11.6.3 Benefits .......................................................................................................... 264
11.7 Guldborgsund .................................................................................................... 265
11.7.1 Challenges ..................................................................................................... 265
11.7.2 Solution .......................................................................................................... 265
11.7.3 Benefits .......................................................................................................... 265
11.8 City of Nice ........................................................................................................ 266
11.8.1 Challenges ..................................................................................................... 266
11.8.2 Solution .......................................................................................................... 266
11.8.3 Benefits .......................................................................................................... 266
11.9 Delhi Mumbai Industrial Corridor ........................................................................ 267
11.9.1 Challenges ..................................................................................................... 267
11.9.2 Solution .......................................................................................................... 267
11.9.3 Benefits .......................................................................................................... 267
11.10 King Abdullah Economic City (KAEC) ................................................................ 268
11.10.1 Challenges ..................................................................................................... 268
11.10.2 Solution .......................................................................................................... 268
11.10.3 Benefits .......................................................................................................... 268
12 Case Study with quantitative analysis ............................................................................. 269
12.1 Executive Summary ........................................................................................... 269
12.1.1 Building Highlights .......................................................................................... 269
12.1.2 Challenge ....................................................................................................... 269
12.1.3 Solution .......................................................................................................... 270
12.1.4 Results ........................................................................................................... 270
12.2 Background........................................................................................................ 270
12.3 Common Characteristics .................................................................................... 271
12.4 Risks .................................................................................................................. 271
12.5 Solution .............................................................................................................. 271
12.6 Results............................................................................................................... 272

© Dubai Design District, All rights reserved. Page 7 of 291

 12.6.1 Vendor Impact ................................................................................................ 272
12.6.2 Operational Impact ......................................................................................... 273
12.6.3 Financial Impact ............................................................................................. 273
12.7 Cisco Bangalore Building 14 (Banyan) ............................................................... 276
12.7.1 Background .................................................................................................... 276
12.7.2 Banyan - S+CC Pilot Implementation ............................................................. 276
12.7.3 Economic Benefits.......................................................................................... 276
12.7.4 Environmental Benefits................................................................................... 278
12.7.5 Social Benefits................................................................................................ 278
12.7.6 In Conclusion ................................................................................................. 279
13 Smart Services Mapping To Endpoints Systems............................................................. 280
14 Glossary ......................................................................................................................... 289

© Dubai Design District, All rights reserved. Page 8 of 291

 List of Figures
Figure 3-1: Smart Services Enterprise Architecture .................................................................. 22
Figure 3-2: Smart City Maturity Model ...................................................................................... 24
Figure 3-3: d3 Smart City Functional Framework ...................................................................... 25
Figure 3-4: Data Virtualization .................................................................................................. 28
Figure 3-5: Virtual View Layered Architecture ........................................................................... 29
Figure 3-6: Integration Platform ................................................................................................ 30
Figure 3-7: API Management Platform...................................................................................... 31
Figure 3-8: Benefits of API Management .................................................................................. 31
Figure 3-9: Benefits of API Management .................................................................................. 32
Figure 3-10: Creating a Value Chain and Ecosystem ............................................................... 32
Figure 4-1: Entrance box representation ................................................................................... 38
Figure 4-2: Typical Fire Stop Representation............................................................................ 49
Figure 4-3: Conduit Usable Area and Factors Affecting It ......................................................... 52
Figure 4-4: Typical Horizontal Pathways and Containment Systems ........................................ 54
Figure 4-5: Pictorial Representation – Conduits ........................................................................ 55
Figure 4-6: Pin/Pair Assignment ............................................................................................... 59
Figure 4-7: Typical Sleeve and Slot Installations....................................................................... 61
Figure 4-8: FTTx Architecture for a typical group of Towers...................................................... 62
Figure 4-9: Tight Buffered Fibre Optic Cable ............................................................................ 66
Figure 4-10: Scope of Standard 607 for Telecom Grounding .................................................... 67
Figure 4-11: Example of Bonding as Per ANSI/TIA-607-B ........................................................ 68
Figure 4-12: Example of Bonding as Per ANSI/TIA-607-B ........................................................ 69
Figure 4-13: HVAC Control Single Line Diagram ...................................................................... 75
Figure 4-14: Lighting Control Single Line Diagram.................................................................... 79
Figure 4-15: Metering Single Line Diagram............................................................................... 82
Figure 4-16: Access Control System Schematic ....................................................................... 84
Figure 4-17: Access Card Technologies ................................................................................... 85
Figure 4-18: Access Control Single Line Diagram..................................................................... 88
Figure 4-19: IP Video Surveillance System ............................................................................... 90
Figure 4-20: IP Network Centric Video Surveillance System ..................................................... 92
Figure 4-21: Video Surveillance Single Line Diagram ............................................................... 94
Figure 4-22: Car Parking System .............................................................................................. 96
Figure 4-23: Car Parking Single Line Diagram .......................................................................... 99
Figure 4-24: Single Encoder ................................................................................................... 101

© Dubai Design District, All rights reserved. Page 9 of 291

 Figure 4-25: Multi-Channel Encoder ....................................................................................... 102
Figure 4-26 Digital Signage Manager Hardware ..................................................................... 102
Figure 4-27 Digital Media Player ............................................................................................. 102
Figure 4-28: Typical Digital Signage Network Topology .......................................................... 103
Figure 4-29 Cables and Connectors ....................................................................................... 104
Figure 4-30: Digital Signage Single Line Diagram................................................................... 105
Figure 4-31: Audio Video Systems ......................................................................................... 107
Figure 4-32: Fixed Screen ...................................................................................................... 108
Figure 4-33: Transparent Screen ............................................................................................ 108
Figure 4-34: Projector ............................................................................................................. 108
Figure 4-35: Smart Whiteboard............................................................................................... 109
Figure 4-36: Touch Panel ....................................................................................................... 110
Figure 4-37: Audio Video Single Line Diagram ....................................................................... 112
Figure 4-38: Fire Alarm Logical Architecture ........................................................................... 113
Figure 4-39: Elevator Logical Architecture .............................................................................. 114
Figure 4-40: Background Music Logical Architecture .............................................................. 114
Figure 5-1: Potable Water Network Logical Architecture ......................................................... 121
Figure 5-2: Sewage Network Logical Architecture .................................................................. 123
Figure 5-3: Storm Drainage Network Logical Architecture ...................................................... 125
Figure 5-4: Fire Fighting Network Logical Architecture ........................................................... 127
Figure 5-5: Irrigation Water Network Logical Architecture ....................................................... 129
Figure 5-6: Street Lighting Logical Architecture ...................................................................... 132
Figure 5-7: A sample view of a 12 Way Duct Bank ................................................................. 138
Figure 5-8: Elevation view of a typical manhole ...................................................................... 138
Figure 5-9: Graph of Signal Loss against Wavelength for Multiple Fibre Types ...................... 142
Figure 5-10: High Density Fibre Splice Patch Panel ............................................................... 145
Figure 5-11: Spice Wallet ....................................................................................................... 145
Figure 5-12: Low Profile, High Density Fibre Patch Panel ....................................................... 147
Figure 5-13: Example of a LC/APC Connector ....................................................................... 148
Figure 5-14: LC/APC Connector Performance Chart .............................................................. 148
Figure 5-15: Power Separation Guidelines - 1 ........................................................................ 151
Figure 5-16: Power Separation Guidelines - 2 ........................................................................ 152
Figure 5-17: Hierarchy Design Overview ................................................................................ 159
Figure 5-18: Layout of a typical Data Centre........................................................................... 160
Figure 5-19: Example MDA .................................................................................................... 161
Figure 5-20: Example HDA ..................................................................................................... 162

© Dubai Design District, All rights reserved. Page 10 of 291

 Figure 5-21: Example SAN ..................................................................................................... 163
Figure 5-22: Weather Station Logical Architecture .................................................................. 175
Figure 5-23: Connected Bus Logical Architecture ................................................................... 177
Figure 5-24: Connected Garbage Bins Logical Architecture ................................................... 178
Figure 5-25: Vehicle Tracking Logical Architecture ................................................................. 181
Figure 5-26: EVCS Logical Architecture ................................................................................. 182
Figure 5-27: Bus Shelter Logical Architecture ......................................................................... 185
Figure 5-28: Advanced Parking Management Logical Architecture ......................................... 187
Figure 6-1: Hierarchical Design Model .................................................................................... 189
Figure 6-2: Functional Segmentation of the Converged Network ............................................ 192
Figure 6-3: Uplink Connectivity for a 10/100/1000 port connected to the end point ................. 193
Figure 6-4: Uplink connectivity for the Data Centre Device Connectivity ................................. 193
Figure 6-5: Traffic Patterns expected on the network .............................................................. 195
Figure 6-6: Marking Strategy .................................................................................................. 196
Figure 6-7: 1P3Q8T Queue Structure ..................................................................................... 196
Figure 6-8: 1P7Q4T Queue Structure ..................................................................................... 197
Figure 6-9: Access Layer of Hierarchical Design Model .......................................................... 198
Figure 6-10: Distribution Layer of Hierarchical Design Model.................................................. 199
Figure 6-11 Block Aggregation method of connecting access to distribution switches ............ 200
Figure 6-12: Building Aggregation method of connecting access to distribution switches ....... 201
Figure 6-13: Core Layer of Hierarchical Design Mode ............................................................ 202
Figure 6-14: d3 Data Centre Functional Segmentation ........................................................... 203
Figure 6-15: A Logical View of the Data Centre Network Infrastructure .................................. 204
Figure 6-16: d3 High Level Network Design............................................................................ 205
Figure 6-17: Mobility High Level Architecture.......................................................................... 206
Figure 6-18: ONM Functional Blueprint ................................................................................... 210
Figure 6-19: Security Process Wheel...................................................................................... 214
Figure 6-20: Security to be implemented on each Level ......................................................... 216
Figure 6-21: DMZ block overview ........................................................................................... 217
Figure 7-1: Central monitoring and control of ICT asset energy usage ................................... 222
Figure 7-2: Energy Management System discovery capabilities ............................................. 223
Figure 7-3: Metrics for measuring and reporting energy efficiency of ICT Systems ................. 224
Figure 7-4: Cooling metrics example for ICT energy management ......................................... 224
Figure 7-5: Data aggregation hierarchy for energy management data .................................... 227
Figure 7-6: Energy domains; asset criticality and domain association..................................... 229
Figure 7-7: Typical ICT asset types and support model for energy management .................... 230

© Dubai Design District, All rights reserved. Page 11 of 291

 Figure 7-8: Reporting example for digital signage and departmental reporting ....................... 232
Figure 7-9: Systems and electrical utilization monitoring......................................................... 233
Figure 7-10 Architectural modelling and comparison considering energy cost ........................ 234
Figure 7-11: Sample of an enterprise energy management system GUI ................................. 235
Figure 8-1: Process for Estidama Rating ................................................................................ 240
Figure 8-2: Performance of Emirates Energy Star .................................................................. 242
Figure 8-3: ISO 37120 Certification Levels ............................................................................. 243
Figure 8-4: Benefits of ISO 37120 Certification ....................................................................... 243
Figure 9-1: In-Building ICT Gaps ............................................................................................ 244
Figure 9-2: Building Systems Gaps ........................................................................................ 245
Figure 9-3: City Wet Utilities Gaps .......................................................................................... 245
Figure 9-4: City Dry Utilities Gaps ........................................................................................... 246
Figure 9-5: City Outside Plant Network Gaps ......................................................................... 247
Figure 9-6: City Other Systems Gaps ..................................................................................... 247
Figure 9-7: Smart City ICT Gaps ............................................................................................ 247
Figure 9-8: Smart Services Gaps ............................................................................................ 249
Figure 12-1: Summary of Construction Budget ....................................................................... 274
Figure 12-2: Total Cost Savings ............................................................................................. 275
Figure 12-3: Connected Real Estate Break Even.................................................................... 277
Figure 12-4: Typical Cost Reduction by using Convergence ................................................... 278
Figure 12-5: Comparative view of validated savings ............................................................... 279

© Dubai Design District, All rights reserved. Page 12 of 291

 List of Tables
Table 2-1: Identified List of Services ......................................................................................... 19
Table 2-2: Smart Services Platforms ........................................................................................ 20
Table 3-1: Typical Smart City Architectural Framework ............................................................ 24
Table 4-1: Entrance Facility Requirements per Building Type ................................................... 37
Table 4-2: MTR Minimum Size Requirement ............................................................................ 40
Table 4-3: Minimum TR Sizes................................................................................................... 41
Table 4-4: Cable tray sizes ....................................................................................................... 42
Table 4-5: Smart City FTR Recommended Size ....................................................................... 43
Table 4-6: TER Sizing Requirements........................................................................................ 46
Table 4-7: Cable tray size requirements ................................................................................... 46
Table 4-8: TER Contaminant Thresholds .................................................................................. 48
Table 4-9: Maximum Capacity Containment- U/UTP Cat6 Cables ............................................ 52
Table 4-10: Maximum Capacity Tray Containment- U/UTP Cat6A/Class EA Cables ................ 52
Table 4-11: Maximum Capacity Trunking Containment- U/U/UTP Cat6A/Class EA Cables ...... 53
Table 4-12: Conduit Trade Sizes .............................................................................................. 56
Table 4-13: Cable Types for Horizontal Cabling ....................................................................... 56
Table 4-14: Specifications of Cat6 cable ................................................................................... 57
Table 4-15: Specification of Cat6A Cable ................................................................................. 58
Table 4-16: Specs for Multilayer Cable Trays for Vertical Risers with 40% Fill Ratio ................ 63
Table 4-17: Minimum Separation Distance from Power Source ................................................ 63
Table 4-18: Fibre Backbone specifications ............................................................................... 64
Table 4-19: Smart Dubai KPI's for HVAC Control ..................................................................... 76
Table 4-20: Smart Dubai KPI's For Lighting Control.................................................................. 80
Table 4-21: Smart Dubai KPI's for Smart Meters ...................................................................... 83
Table 4-22: Smart Dubai KPI's for Access Control .................................................................... 89
Table 4-23: Smart Dubai KPI's for Video Surveillance .............................................................. 95
Table 4-24: Smart Dubai KPI's for Car Parking ....................................................................... 100
Table 4-25: Smart Dubai KPI's for Digital Signage .................................................................. 106
Table 4-26: Smart Dubai KPI’s for Solar Panels ..................................................................... 116
Table 4-27: Smart Dubai KPI's for Smart Home...................................................................... 119
Table 5-1: Potable Water KPI Interpretation ........................................................................... 123
Table 5-2: Sewage Network KPI Interpretation ....................................................................... 125
Table 5-3: Storm Draining KPI Interpretation .......................................................................... 127
Table 5-4: Fire Fighting KPI Interpretation .............................................................................. 129

© Dubai Design District, All rights reserved. Page 13 of 291

 Table 5-5: Irrigation Water KPI Interpretation .......................................................................... 131
Table 5-6: Electrical KPI Interpretation ................................................................................... 131
Table 5-7: Street Lighting KPI Interpretation ........................................................................... 133
Table 5-8: Proposed Sizes of Tertiary POPs .......................................................................... 136
Table 5-9: Service Corridor Recommendations for Smart Services ........................................ 139
Table 5-10: Last Mile Fibre Core Recommendation ................................................................ 141
Table 5-11: Typical Fibre Colour Code for Splicing ................................................................. 146
Table 5-12: Power Separation Distances ................................................................................ 150
Table 5-13: Tray Size Capacities ............................................................................................ 153
Table 5-14: Tray Size Capacities ............................................................................................ 154
Table 5-15: Equipment Room Sizes ....................................................................................... 154
Table 5-16: Example Data Centre Power Requirements......................................................... 167
Table 5-17: Example Primary POP Power Requirements ....................................................... 169
Table 5-18: Example Secondary POP Power Requirements .................................................. 171
Table 5-19: Traffic Lights (signal) KPI Interpretation ............................................................... 172
Table 5-20: Smart Dubai KPI's for Outdoor Sensors ............................................................... 175
Table 5-21: EVCS KPI Interpretation ...................................................................................... 184
Table 5-22: Smart Dubai KPI's for Advanced Parking Management ....................................... 188
Table 7-1: Typical ICT asset types managed by an ICT energy management system ............ 225
Table 7-2: Typical energy protocols by asset class ................................................................. 226
Table 7-3: Typical energy protocols by asset class ................................................................. 231
Table 7-4: Energy data aligned to ICT system utilization ........................................................ 232
Table 11-1: Smart City Alignment against d3 focus area ........................................................ 253
Table 13-1: List of Smart Services; their categorization and integration map .......................... 288

© Dubai Design District, All rights reserved. Page 14 of 291

 1 Background
1.1 Dubai Design District
Dubai Design District, better known as d3, is dedicated to fostering the growth of the United Arab
Emirate's design, fashion and luxury industry. It offers businesses, entrepreneurs and individuals
a creative community that will be at the very heart of the region's design scene.
d3 is one of the newest projects of TECOM Group which is a member of Dubai Holding, a real
estate master developer and operator of Dubai’s leading business parks. d3 is a free-zone
business park with 11 buildings currently completed as part of Phase 1 of the development. The
other phases of d3 are currently under development and on completion of these phases, d3 will
represent a purpose-built environment catering to the full value chain of the design, art, fashion
and luxury industries - and all with a vision of creating a world-class creative community that
engages, nurtures and promotes local, regional and global design talent. The 3 phases are:

 Phase-1: Design Quarter, comprising of offices and retail (completed in 2015)

 Phase-2: Creative Community (to be completed in 2019)
 Phase-3: Waterfront promenade (to be completed in 2021)

d3's facilities will range from cutting-edge design institutes to residential, hospitality, retail and
office spaces. The District will be characterized by distinct public areas, unique street furniture
and shaded walkways. The development will include a Creek-side esplanade with international
and boutique hotels and a “pop-up shop” area.
In addition to being the hub of design activities, d3 is also being developed as a Smart City which
mirrors the aspirations of Smart Dubai, and which serves as a pilot for Smart City design and
development activities. These guidelines are designed to fulfil this aspiration

1.2 Project Objectives

d3 has selected a list of smart initiatives which are in various stages of implementation. d3
understands the complexity of the environment and the necessity for an infrastructure plan that
can be shared with all stakeholders (developers, consultants and contractors) to create a Smart
City and which can be replicated in other developments. An essential part of any Smart City is
the data produced by the connected devices and sensors in the City which can be analysed for
actionable intelligence in a central location which is the Command and Control Centre (CCC) in
d3’s case. d3 will also make this data available in an open format to application developers for
creating new applications and use cases. The data platform that is implemented in d3 is Cisco’s
Data Virtualization platform that gathers data from all sources within the city and presents one
view of the data in near-real time as a virtualized data lake.
As part of the ICT Master Plan project scope, the following activities were carried out:
 Review the smart initiatives selected by d3 and prepare a service catalogue.
 Create a building guideline for the connectivity of the building systems
 Share the best practices for passive infrastructure, containment and telecom rooms
 Perform a gap analysis of the existing infrastructure in d3 prior to the framing of these
Guidelines and suggest solutions.
 Build a high-level integration plan for integrating the required data sources with the data
hub. In the case of d3, these were
o ESRI, Geospatial reference platform
o Yardi, Property Management System

© Dubai Design District, All rights reserved. Page 15 of 291

 o Desigo, Building Management System
o Reflection, Facility Management
o Oracle, ERP Database
o Salesforce, CRM System
 Implement the Data Virtualization Platform
 Expose the data coming from the above six data sources
 Develop the Command and Control Centre visual content that will allow situational
awareness of the implemented systems

© Dubai Design District, All rights reserved. Page 16 of 291

 2 Introduction
In order to achieve the Smart City Vision set forth by Smart Dubai in general and d3 in particular,
it is important to emphasise that any master planner, consultant, contractor or vendor must adhere
to the automation and convergence guidelines defined in this document. This document can be
used as a reference guide by such stakeholders to ensure that their designs match or exceed the
functional requirement set forth to achieve the automation objectives.

2.1 Purpose of the Document

This document is a multi-purpose document and the intent is to provide high-level design
guidelines and recommendations to planners, consultants and contractors engaged in the
development of the various phases of d3 to ensure that foundation Smart City converged network
provides interconnection of all data sources to a data hub for analytics.
This document can be used by different entities and user types. The following are some of the
entities or user types that shall use the document:

 d3 Smart Services team for reference

 Master Planners and Consultants for creating Smart City ICT Master Plans, Concept
and Detailed Designs
 Contractors for reference, tendering, and procurement
 Systems Integrators for understanding the integration needs and ensuring proper
configuration of Smart Services
 Vendors for supplying hardware, software and licenses
 Telecom and Utility Service Providers for understand connectivity, integration and data
sharing

The object of writing this document is to facilitate the design and construction work for different
stakeholders within d3 who are responsible for their respective disciplines. This document shall
ensure that the infrastructure developed within the district meets or exceeds the Smart Dubai’s
and d3’s Vision to deliver Smart Services within the district. Deploying such services shall ensure
that the visitors, tenants, and employees have a unique and better experience within the district.
It is important to note that the infrastructure is built such that the KPIs defined by Smart Dubai
and d3 together can be met and achieved using Smart Infrastructure with the district.
This document is written keeping in view the different guidelines published by various standard’s
bodies relevant to Smart Cities around the world, Smart Dubai recommendations. Leading
Building and Energy certifications to consider are: LEED, Green Globes, Estidama, Emirates
Energy Star and ISO.
This document can be treated as a living document and in due course of time these guidelines
will be revised and issued by d3.

2.2 Methodology and Assumptions

The methodology and the assumptions used to write this document are listed in the following sub
sections.

2.2.1 Methodology
ICT Masterplan guidelines are based on International Standards and best practices. The list
includes but is not limited to the following:

© Dubai Design District, All rights reserved. Page 17 of 291

 TOGAF®, SOA, eTOM®, ITIL®, BICSI®, ANSI/TIA, and the Uptime Institute. In addition, each
section will further highlight the specific standards it is associated with.
This Design Guideline Document takes into consideration the recommendations of the Smart
Dubai District Guidelines as well as the DCCA recommendations provided in the d3 Master Plan
Accessibility review report submitted in association with Place Dynamix on 27th May 2015.
The guidelines within this document apply to the converged ICT infrastructure necessary for
ensuring connectivity to the list of service defined in the services catalogue as shown below:

Ref Service
1 Advanced Parking Management
2 Visitor Management
3 Traffic Management
4 Smart roads, bridges and tunnels infrastructure
5 Intelligent Transport System
6 BIM based facility management
7 Energy Analytic System Optimization
8 Personal Dashboard
9 Extended Privileges
10 Operation and Maintenance Enhancement
11 Technology Experience Showcase
12 Integrated Tenant On Boarding System
13 Digital Credential
14 Electric Vehicle Power and Charging
15 Network Enabled Utility Metering
16 Incentivized Recycling Program
17 Smart Irrigation Water
18 Sewage Water
19 Storm Water Management
20 Waste Management
21 Smart Lighting Pole
22 Role Based Energy Management
23 Water Management
24 BIM/GIS based integrated digital experience
25 Consolidated Personal Control
26 Community Information Services and Portal
27 Security Service Integration
28 Integrated Building Management System
29 Visual Communication (digital signs)
30 Smart Home
31 Interactive Services (kiosks)
32 Way finding mobile app
33 Wi-Fi Connect

© Dubai Design District, All rights reserved. Page 18 of 291

 34 Location Analytics (People Counting)
35 Shared Resources
36 Digital Wallet/Cashless Payment
37 Targeted Advertising
38 Loyalty program
39 d3 Augmented Reality Tour
40 Building Information Modelling
41 Solar Roofs
42 Connected Bus
43 Smart Bus Shelter
44 Autonomous Cars
45 Smart Working Spaces
Table 2-1: Identified List of Services
It is important to note that these services are of two distinct types. One that has end points or
sensors and a backend system necessary to provide the intelligence, business logic,
management and security specific to the service. Other that can be provided as soft services only
using a d3 portal over the Internet and can be used either using a PC, smart phone or a tablet.
The services listed above can be provided by a set of Applications and or Platforms categorized
as listed in the Table 2-2 below. This document shall provide the guidelines only for the following
platforms to help d3 Smart Services Team and the consultant and contractors to specify and
procure.

S. No: Smart Services Platforms Type

1 HVAC Control In-Building Systems
2 Lighting Control
3 Smart Metering
4 Access Control
5 Video Surveillance
6 Digital Signage and Kiosks
7 Car Parking System
8 Audio/Video
9 Solar Panels
10 Smart Home
11 Point of Sale
12 Water System City Wet Utilities
13 Irrigation
14 Storm Water
15 Sewage
16 Lighting Pole City Others System
17 Traffic Light
18 Multi-Function Sensors
19 Weather Station

© Dubai Design District, All rights reserved. Page 19 of 291

 20 Connected Bus
21 Connected Garbage Bins
22 Vehicle Tracking
23 Electric Vehicle Charging Station
24 Smart Bus Shelter
Table 2-2: Smart Services Platforms
For understanding the link between the Service and the Platform, refer to the Table 13-1 in the
Appendices section of this document.

2.2.2 Assumptions
The assumptions used in this document are as follows:

 d3 is capable of meeting or exceeding the Smart Dubai Vision of making Dubai the
happiest place on earth.
 d3 is going to be the first district within Dubai that will build its infrastructure to ensure it
has the capability to monitor and meet the necessary KPIs defined by Smart Dubai.
 ICT technology is leveraged wherever necessary to ensure that different system within
the buildings and outside the buildings within the district are able to communicate and
share data among each other.
 The data sharing is necessary for creating informative dashboards within the d3 CCC
and also monitoring and meeting the Smart Dubai KPIs
 It is assumed that different systems within d3 that are within the buildings or outside are
able to communicate with each other using once common IP Network Infrastructure so
that new and unique Smart Services can be quickly developed and deployed within the
district.
 The guidelines included in this document will adhere to the “Smart Dubai District
Guidelines, Ver. draft 1.4” where the applicable law or regulation permits.

2.3 Scope of the Document

This document shall provide ICT guidelines for the Applications or Platforms specific to Smart
Services as listed in Table 2-2 above. The scope of this document is to provide the functional
requirements that are detailed enough to allow the Consultants and or Contractors to specify and
tender the procurement of such applications, systems or Platforms.
The scope of this document is as follows:

 Define the d3 Smart City Functional Framework that is based on a Smart City Reference
Architecture. This shall provide a block level view of the different elements that are
necessary to materialize the Smart City Vision.
 Develop the ICT guidelines for the building systems that are necessary for building a
Smart and Connected building. The building systems covered in this document are as
follows:
o ICT Guidelines for Building Systems in d3
o Connected Real Estate Basis of Design
 Inside Plant Infrastructure
 HVAC Control
 Lighting Control
 Smart Metering
 Access Control

© Dubai Design District, All rights reserved. Page 20 of 291

  Video Surveillance
 Car Parking
 Digital signage
 Audio/Video
 Solar Panels
 Smart Home
 Point of Sale
 Life Safety
 Elevators and Escalators
 Public Address/ Background Music
 Develop a set of technology guidelines for the Municipal Systems that are necessary for
building a Smart and Connected Community. The Municipal systems covered in this
document are as follows:
o City – Wet Utilities
 Potable Water Network
 Sewage Waste Water Network
 Storm Drainage Network
 Fire Fighting Network
 Irrigation Water Network
o City – Dry Utilities
 Electrical
 Street Lighting
 Telecommunications
 Outside Plant Passive Infrastructure
o City – Others
 Traffic Lights
 Multifunction Sensors
 Weather Station
 Connected Bus
 Connected Garbage Bins
 Vehicle Tracking
 Electric Vehicle Charging Stations
 Bus Shelter
 Develop the ICT Network Infrastructure guideline for d3. This includes the converged
wired and wireless IP Network.
 Green ICT Guidelines that provide a set of guidelines on implementing technology
based solutions that will enable monitoring and efficient use of energy.
 Provide guidance on building sustainable and efficient buildings as defined by some of
the leading Building and Energy Certifications bodies.
 Provide a short description of case studies of Smart City implementations that are either
built or are under construction, utilizing the Smart City Architectures.
 Provides a list of gaps that have been identified in the ICT infrastructure on comparing
the state of the approved master plan for the district and the infrastructure built in the
following areas from Smart City perspective:
o Public areas
o Inside the buildings
o Smart City Services or Initiatives

© Dubai Design District, All rights reserved. Page 21 of 291

 3 Smart City Architecture
3.1 Reference Smart City Architecture
The recommended architecture for d3 is a derivative of the Architectural approach defined by
TOGAF. ICT Infrastructure guidelines are based on International Standards and best practices.
The list includes but is not limited to the following:
TOGAF, SOA, eTOM, ITIL, BICSI, ANSI/TIA, Uptime Institute.
The guidelines are also taking into consideration the recommendations made by Smart Dubai
District Guidelines.
In order to fulfil the vision of a technologically advanced and Connected Community and Creative
Design facility, d3 must deploy their ICT infrastructure in a layered architecture mentioned within
this section. It is important to highlight that any ICT, Communications and building system will
need to ensure information sharing and hence service delivery to end-users. This can
successfully be achieved with a layered Technical Architecture model as shown in Figure 3-1
below:

Figure 3-1: Smart Services Enterprise Architecture

© Dubai Design District, All rights reserved. Page 22 of 291

 The architecture can be presented in a model that comprises of eight (8) distinct layers. This
architecture is a combination of architectures defined in TOGAF© and eTOM©.
Figure 3-1 shows the recommended enterprise architecture to provide Smart Services to its end
users. While this architecture needs to be defined in detail, especially in the context of IoT, this
document will however, briefly explain the functionality of each layer. This will ensure that the five
Smart Services Groups defined in the earlier phases of the project work seamlessly.
Layered Description Reference Example
Technology
Business Layer Provides a business model describing the Business needs and
Architecture government services and relationships to requirements
internal and external entities. The model
will represent business functions,
workflows, data, events, organization
and governance models
Access and Serves as container for local tools and Web Browser, email client,
Presentation applications, enables end user access to desktop application, mobile
Layer the infrastructure, and provide mechanics application
Architecture to access applications running on the
servers
Application Provides the realization of business Business Applications: CRM,
Layer needs and requirements as software KM, HR, Finance,
Architecture solutions. Major enabler of service Collaboration System
oriented architecture approach applications: Web server,
application server, database
server, and infrastructure

Data Layer Defines the data and information that Meta data, data model and
Architecture support program and business line structure for business
operations applications, i.e. for HR
applications personnel data

Integration Enables integration of the business HR web services, finance web

Layer applications and access to the required services, authentication and
Architecture data throughout the service oriented authorization web services
infrastructure
Infrastructure Provides a target (logical) environment Network, network devices like
Layer and describes the technical infrastructure routers and multiplexers, and
Architecture required to deliver integrated services computers

Operations Provides a model to support the Business transactions

Layer deployment and delivery management of between entities such as help
Architecture modern smart and connected services desk, configuration
that integrate business processes across management, program
multiple entities, requiring an evolution of management, software
traditional approaches to operations and development
service management

© Dubai Design District, All rights reserved. Page 23 of 291

 Security Layer Enables Aspire to build a consistent and Single sign on, authentication,
effective security environment. The SSL, authorizations,
Security Architecture contains service provisions
definitions that are driven by business
objectives and accordingly enabled by
applications and the underlying technical
infrastructure
Table 3-1: Typical Smart City Architectural Framework

3.2 Automation: an Essential Enabler in Smart City

Maturity Model
According to IDC, Smart Cities integrate information and operation within and between city
systems to create a new platform for service delivery and sustainable economic development.
Navigating the transformative change required to become a Smart City is a long-term and
complex process. To work toward this goal, cities will progress through common phases as they
create a Smart City system. The IDC Smart City model identifies and describes five stages to
maturity and key attributes of each phase:

Figure 3-2: Smart City Maturity Model

Automation, which consists of the digitization of the city systems and processes, is essential in
moving from the ad-hoc state to the managed and optimized stages.
More specifically, automation is the process by which the systems are able to provide information
or data to the Data Virtualization platform by use of sensors or probes that enable the city
management to issue instruction to react to a situation or take proactive actions to avoid a certain
situation.

© Dubai Design District, All rights reserved. Page 24 of 291

 Automation can also be applied to a process, system or an end point by employing electronic
systems, electro mechanical systems and computerized systems. The automation has to ensure
that data coming from the end point or the system can be transported on a converged IP Network
and eventually to the Data Virtualization Platform.

3.3 d3 Smart City Functional Framework

Any consultant, developer or contractors who are involved in any construction activity within d3
must always keep the following guiding principles of d3:

 Six Dimensions: Which originated from Smart Dubai for achieving the Smart City vision
o Smart Economy
o Smart Governance
o Smart People
o Smart Living
o Smart Environment
o Smart Mobility
 d3 3Cs Framework: This framework provides a quick view of how d3 intends achieving
the Smart City Objectives
o Cover
o Connect
o Crunch

The d3 Smart City Functional Framework (Figure 3-3) results from the combination of the Smart
City Architectural Framework as defined in Section 3.1, the Smart City maturity model as
described in section 3.2 and on understanding of d3’s environment.

Figure 3-3: d3 Smart City Functional Framework

As described in the Smart City maturity model, the d3 Smart City Framework is based on
automation as the essential enabler for smart cities: the digitization of processes and systems in
every aspect of the city including: people, living, governance, .
The d3 Smart City functional framework is based on three main layers: Foundation, Convergence
and Transformation. The functional framework is also based on two horizontal layers: policies
and regulations as well as Management and security.

© Dubai Design District, All rights reserved. Page 25 of 291

 The sections below describe in more detail each layer of the functional framework.

3.3.1 Foundational Layer

This layer focus on the basic infrastructure that is necessary for providing Smart Services within
the City. This includes mainly the Passive and the Active Network within the district. In addition,
it also includes functionalities like the CCC, Contact Centre to deliver the Smart Services.
The d3 CCC, the Contact Centre as well as the Data Centre sit on top of the Open Data Platform.
The CCC enables the monitoring and control of dynamic activities involving high-resolution image
processing, real-time video feeds, data integration, and various data and alert signals. The CCC
gives city operators access to management tools to work with the information generated on a
daily basis. The contact centre will provide a unique number to support 24/7 the tenants and
visitors of d3. The data centre will host the servers of d3 Smart Services.
The d3 IP network consists of passive and active components. The passive components are the
ducts, conduits and cables. The active components consist of the routers, switches and access
points and other sensors. The d3 IP network will be designed for all buildings in d3 and will extend
to the public spaces outside the buildings. The d3 IP Network is a converged network that will
enable all systems, sensors and devices in d3. The d3 IP network will be used to deliver all smart
services. The regulated services will still be provided by du using the du network.

3.3.2 Convergence Layer

The convergence layer focuses on the functions of service creation, integration and data sharing.
The d3 IP network consists of passive and active components. The passive components are the
ducts, conduits and cables.
The Open Data Layer provides an integrated, holistic, view of operation and asset data to optimize
upstream business. It is a layer on which one single version of the truth for all enterprise data are
stored and are consumed. Open Data Policies will be implemented to govern database schemas,
provide data access, data assurance, as well as data security. The Open Data Layer will be
administered and governed by d3 for the benefit of the district with requisite security and
anonymity in place.
The data generated by the applications and dashboards in d3 is intended to be shared with The
Government (Smart Dubai), management and operations, private companies, associations and
individuals. The API management layer enables d3 to build new APIs, design new interfaces for
existing APIs and more efficiently manage all APIs using a single platform to rapidly expose d3
data to mobile devices, web apps and connected things in a secure and controlled way.
The Service Enablement layer consists of the services that are common in more than one smart
initiative. In order to build the smart services in an intelligent way, it is important to identify these
overlaps and implement them with the first stage of smart services.
For d3, the service enablement layer consists of the following services: Digital credential, Single
Sign-On, Authentication, Trust, Payment Gateway, Application Platform, Web platform, Database
platform, Scheduling Platform and Data Exchange.
The integration of the building systems and communication brings many benefits to the
intelligent building. The major benefits of the convergence are:

 Adding value
 Saving operating costs
 Enhancing productivity
 Positive factor in higher real estate and rental prices

© Dubai Design District, All rights reserved. Page 26 of 291

 The benefits of the convergence differ depending on the stakeholder (building owner, tenant,
operator, worker, visitor…). The information below lists those benefits relative to each
stakeholder. Experience indicates that the convergence benefits are functionally desirable
and can be cost effective. Cost effectiveness benefits primarily the
developer/owner/operator, whereas the functional enhancements are mainly enjoyed by the
occupants/tenants. In the case of d3, the value will be perceived by its employees, its tenants,
residents and visitors.
The S+CC convergence provides the following advantages for the following stakeholders:

 Building/Developer
o Advanced functionality at modest cost
o Higher building value and leasing potential
o Ability to offer customized building functionality for specific occupants/tenants
o Increased rentable space by reducing the infrastructure space needs, e.g., fewer
conduits, control systems and control locations
o Offer improved services and environment to the tenant
 Owner/Operator
o Reduced operating and maintenance costs
o More effective and responsive building management
o Provision of a single interface for the integrated building services
o Allow the owner/operator to transfer some building control to the occupant/tenant
o Improve telephone services and accessibility for the end user
o Facilitate security management
o Provide owners/operators with greater operational flexibility, e.g., the ability to
operate several buildings from one control centre, improving effectiveness while
reducing cost
o Increased operational staff capabilities to monitor conditions and
resolve problems effectively e.g., fixtures can be re-lamped based on actual
utilization, not on elapsed time
 Occupants/Tenants
o Access to state of the art technologies that differentiate premium office
accommodation from commodity
o Premium features by enjoying a more comfortable environment (HVAC, lighting,
access and security)
o Premium features by having access to services that will improve efficiency and
effectiveness, e.g., reliable, ubiquitous, flexible and highly featured broadband
communications, and the ability to reconfigure office space quickly, easily and
cheaply, independent of the owner/operator
o Ability to relocate employees within the building, without reference to the
owner/operator, thus reducing the time, cost and disruption
 Design Engineers
o Provides enhanced functionality
o Facilitate commissioning
o Reduce dependency on proprietary vendors
o Provide design engineers with better control of site construction, because
of fewer subcontractors
o Ensure consistent infrastructure options and implementation.
 Contractors
o Allow interchange of vendors and manufacturers
o Better availability and more competitive prices of products
o Ensure control of construction costs
o Make testing and commissioning easier

© Dubai Design District, All rights reserved. Page 27 of 291

 o Allow for building completion in stages
 Manufacturers
o New business opportunities for technology developers
o Co-operation among vendors promoted by the development of standards
o Applicability of technologies initially developed for other markets in the
construction sector
o Offer marketing opportunities through vendor interoperability
o Decreased costs and increased reliability through the sharing of a common
communications infrastructure.

[Link] Data Virtualization

Data Virtualization (DV) focuses on the paradigm of data integration to make data available for
consumption across various applications (both analytic and operational) while data stays at its
source of occurrence. DV's goal is to provide one single version of the truth platform for all
underlying data irrespective of their sources of occurrence and complexity in data types, data
availability, source data format etc. DV can shield all consumers from any change in underlying
data infrastructure, availability, format and movement.
DV has native connectors to various industry standard data sources (traditional RDBMS, NoSQL
databases, Web Services, JMS messaging etc.). As DV is a Java-based platform, it can connect
with almost any standard database allowing JDBC connectivity. Some data sources are only open
to web services connectivity for security or other reasons (e.g. protecting performance of
underlying platform).

Figure 3-4: Data Virtualization

The DV utilizes a layered architecture of virtual views built on top of source data layers to make
data available for consumption. The design and development time in DV is significantly less than
a traditional data delivery timeline as data is exposed in a virtual manner.
In a classical deployment, views are created for physical data sources at the bottom most layer
and designed to represent canonical data format at the higher layers for ease of consumption.

© Dubai Design District, All rights reserved. Page 28 of 291

 Figure 3-5: Virtual View Layered Architecture
At d3, seven operational applications are part of scope for data virtualization are as follows:

 Oracle ERP (Scope may include exposure of very limited set of data)
 Salesforce (Lead to Lease process)
 YARDI Property Management System
 Siemens Desigo BMS
 Facilities Management Reflections System
 ESRI GIS Platform
 Smart Meters (Energy and Chilled Water)

These applications will be integrated within the initial scope of the project. Future application and
solution providers will need to comply with the following guidelines:

 Secure connectivity to the d3 network

 Open ports to the Data Virtualization Sever
 As DV is a Java-based platform, it can connect with almost any standard Data Base,
structured or unstructured:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc.

© Dubai Design District, All rights reserved. Page 29 of 291

 [Link] API Management
The API Management layer may be provided by The Integration Platform (CIP) which can
accelerate the delivery of business outcomes by quickly connecting and automating processes
that span on premise and cloud based applications, data and infrastructure through a light weight
service bus and end-to-end API management. CIP comprises two core products:

 Integration Bus: a lightweight, open-standards-based integration platform, and the

 API Manager: which provides full API lifecycle management with governance and
security.

SAAS Application Social Data Cloud Data Devices Partner Data

Integration Platform
Integration Bus API Manager

Customer Data Enterprise App’s Custom Apps Infrastructure Enterprise Data Network Data Location Data

Figure 3-6: Integration Platform

The Integration Platform accelerates the delivery of desired business outcomes. It quickly
connects and automates processes that span on premise and cloud-based data, applications,
and things through a lightweight service bus and end-to-end API management.

© Dubai Design District, All rights reserved. Page 30 of 291

 Figure 3-7: API Management Platform

The platform promotes faster deployments:

 Get over 150 prebuilt connectors, graphical design tools, and mixed-model deployment
support to integrate any application or deploy a service as an API
 Cut costs and save time with the build-once, deploy-anywhere design
 Boost operational efficiency by up to 50 percent through automated tasks
 Promotes data and system monetization

Figure 3-8: Benefits of API Management

Other benefits include increased agility:

 Rapidly adapt to new business models

 Gain scalability without complexity while integrating new systems, people, processes,
data, and things
 Build next-generation integration connectivity through this multitenant, elastic, and self-
provisioning platform

© Dubai Design District, All rights reserved. Page 31 of 291

 Ecosystem Partners Partner Data SAAS Application Customers Social Data Cloud Data Devices

API API API API

Integration Bus
Visual Flows Prebuilt Connectors Transport Transform Mediate Manage Data Services Process Events

API API

Enterprise App’s Custom Apps Enterprise Services Employees Processes Devices Infrastructure Data

Figure 3-9: Benefits of API Management

Process Integration:
 Break down integration barriers, take control of business processes, and improve
process efficiency.
 Take advantage of legacy and new applications, resulting in process simplification and
automation.
 Use The Integration Platform for process innovation with Internet of Everything (IoE) and
mobility solutions.

Production Consumption

Platform API Catalogue App Market

Administration
Place
Service
Tenant
Administration App
API
APP Exchange

User Community

API Owner

APP Developer APPs App Store

API Management
API Developer APIs
Platform

Figure 3-10: Creating a Value Chain and Ecosystem

At d3, the API Management is not in the initial scope, but this layer will be designed and built at
a later stage in order to create an automated integration platform for process innovation with
Internet of Things (IoT) and mobility solutions.

© Dubai Design District, All rights reserved. Page 32 of 291

 Any future smart services and solutions providers will need to comply with the following
guidelines:

 Secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.

3.3.3 Business / Transformational Layer

This layer is primarily the list of applications and platforms that run as a service on the foundational
layer making use of infrastructure in the convergence layer to provide Smart Services.
d3 currently has 6 existing applications/platforms: ESRI (GIS), Salesforce (CRM), Oracle (ERP),
Yardi (Property Management), Desigo (Building Management System), and Reflection (Facility
Management). The data from these applications will be exposed for reporting purposes using the
data virtualization layer. Different methods can be used to share the data from these sources.
Since most of them are cloud based solutions and the rest are shared services from TECOM
Group, security needs to be taken into consideration.
This layer also contains all smart services that d3 offers its tenants, visitors and operators. Unlike
the rest of the layers, this list of services can be used in the marketing material to attract tenants
and visitors and show the differentiation of d3 in the Smart City space as well as in the design,
fashion and luxury space.
The smart services will rely on all other layers defined above. They will use the network to connect
their sensors, connect to the DV platform to expose the data, use the service enablement layer
whenever applicable, and host its server in the DC, share data to the CCC level to ensure proper
operation by city staff.

3.3.4 Operations and Security Layer

This functional layer ensures safe and secure operations of the Smart Services Infrastructure.
The operational layer spans across all other functional layers.
The operational layer focuses on the following key requirements specific to Smart Services.

 Domain Management
 Configuration Management
 Performance Management
 Service Control

For further details refer to Section 6.1.6 of this document.

The Security Layer focuses on the following key requirement specific to the Smart Services
infrastructure that include the infrastructure, applications and data.

 Security Policy Definition, implementation and Management

 Authentication
 Authorization
 Accounting

© Dubai Design District, All rights reserved. Page 33 of 291

 For further details refer to Section 6.3 of this document.

3.4 d3 ICT Review

After conducting the As-Is assessment and defining the d3 Smart City ICT Framework and design
guidelines the following high-level gaps were identified:

 No Smart City Architectural framework has been defined so far. One such Architecture
needs to be developed in detail to ensure smooth deployment of Smart Services and
easy interaction with other utility and services providers.
 None of the key elements of the Smart City Infrastructure that is the deployment of
Converged IP Network Infrastructure is available in the district. This convergence will
ensure that different city services’ providers relevant to energy, water, telecom, security,
transport and district cooling are able to communicate with each other.
 An integration platform that is necessary for sharing information and data is between
different utility providers with d3 and the different building systems, security systems and
ICT/Telecom systems is not available as of date. The Data Virtualization Platform will
fulfil this need
 Different service and utility providers within d3 showed concerns or were not eager to
share the common network or data with each other at the present moment. This
necessitated d3 to deploy its own converged IP Network for connectivity and build a
Data Virtualization platform to share information and better manage the city operations.
 The existing eleven (11) buildings within Phase-I of d3 have no Smart City Network to
provide the Smart Services that have been defined within the Services Catalogue for
deployment within d3. This will be built.
 The Phase-2 development for Creative Community that is currently in the design phase
will incorporate the Guidelines to ensure that no change orders or changes in the design
are to be made once the contracts are awarded.

© Dubai Design District, All rights reserved. Page 34 of 291

 4 ICT Guidelines for Building Systems in
d3
d3 aims at integrating and analysing massive amounts of data to anticipate, mitigate, and even
prevent many problems at the building level. This data will be leveraged, for example, to operate
the building efficiently, identify equipment malfunction and target resources for energy
consumption reduction.
In order to achieve the above, all stakeholders responsible for the building infrastructure and
systems need to follow the technical guidelines provided in this section.
It is also important for the designers to show leadership by providing designs that align with these
following guiding principles:

 The Network as the platform (Section 3.3.1)

 Convergence of the systems (Section 3.3.2)
 Transformation/ Service Delivery (Section 3.3.3)
 Automation of processes and systems (Section 3.2)
 Easy Accessibility While convergence and automation is the way forward for any Smart
City, due to Dubai’s specific regulations, it may not be possible for d3 to converge all the
systems particularly the Telecommunications network, Security network, DEWA (Dubai
Electricity and Water Authority) network and Empower network. All these providers are
not yet ready to share and use one common network to carry their data to their
respective data centres. Keeping these limitations in view it has become mandatory for
d3 to have its own communications network within d3 to cater to deliver Smart Services
within the district.

This section provides the best practices to build a communications network as well as specific
recommendations for d3 wherever necessary. This section also lists all the connectivity
requirements of the building systems to easily converge on this network and be open for future
integration.

4.1 Inside Plant Best Practices

This section is aimed at providing guidelines for various stakeholders to address d3’s new
development with regards to inside structured cabling design enabling the medium for d3 to
provide Smart Services with the district.
The proposed inside plant structured cabling standards for buildings are designed in accordance
with the latest industry standards.
This document is intended to provide a guideline to the building contractors and ICT professionals
to build inside plant infrastructure within the buildings in order to fulfil d3’s Smart and Connected
Campus vision.
The information herein is intended to be passed on by d3 to the parties who shall review the
architectural, structural, and electrical drawings or designs of each building from a structured
cabling subsystem (SCS) and inside plant cabling specification perspective. The specifications
shall also provide a comprehensive source of information and guidance for those involved with
low-voltage cabling and thus needs to be shared with such specialist contractors.

© Dubai Design District, All rights reserved. Page 35 of 291

 The recommendations presented in this document are based on design recommendations of
standards organizations such as BICSI & ANSI/TIA. In addition, this document has also provided
recommendations based on significant knowledge and experience gained in past engagements.
The recommendations in this document are divided into three main sections, as listed below:

 Telecommunications Spaces
 Structured Cabling Systems
 No Objection Certificate Requirements

4.1.1 Assumptions and Caveats

 The reader has familiarity with:
o Inside plant infrastructure fundamentals
o IP networking basics
o FTTx (fibre to the home, office, building, etc.) architecture
 Presumed that the structured cabling shall be done by the building developer based on
industry and local standards
 Copper cabling shall be used horizontally to provide connectivity to building automation
and common area services if required
 Each building shall have one main telecom room and at least one floor telecom room per
floor in order to provide ICT services and telecom consolidation points within the office
premises

4.1.2 Telecommunication Spaces

Telecommunications spaces are meant to house telecommunications cabling infrastructure
blocks and any related telecommunications hardware and systems. The
telecommunications systems will be required throughout the d3 campus in different areas.
The size of each will vary based on requirements. The different types of telecommunication
rooms required by buildings are as follows:

 Telecom Entrance Facilities (TEF)

 Main Telecom Room (MTR)
 Floor Telecom Room (FTR)
 Telecom Enclosure (TE) or Telecom Closet (TC)
 Consolidation Point (CP)
 Telecom Equipment Room (TER)

[Link] Telecom Entrance Facilities

Telecommunications infrastructure from the local services provider will need to enter the
commercial building via the TEF. It is strongly recommended to have enough provisions in the
TEFs to accommodate multiple service providers.

[Link].1 Entrance Facility Requirement

The entrance facility for the buildings shall need to have the following considerations while
constructing the entrance facility:

 The required service entrances of telecom service providers

 Right of way easements and permits

© Dubai Design District, All rights reserved. Page 36 of 291

  Locating other utility facilities
 Loop diversity
 Dual entrances
 Entrance cable guidelines
 Sizing of underground conduits, placing of inner-ducts and sharing conduits
 Choosing pull points
 Determining cover depth
 Preparing for tie-in connections and designing termination points
 Sealing conduits and shoring requirements
 Bonding and grounding
 Inside space requirements
 Demarcation points

[Link].2 Entry Boxes or Hand holes/Maintenance holes

Depending on the building type, service requirements vary, and accordingly cabling ducting
requirements vary. As per ANSI/TIA- 569-C standard, the following recommendation applies to
d3’s new headquarters.

 Minimum two 100 millimetres (mm) ducts with 1 spare (100 mm size) should be
considered for each entrance point
 The entry box maintenance holes (MH) should be located in the level with the ground
level, leading directly into the main telecom rooms located on the ground level

Building Type Quantity of Entry Facilities Qty of Ducts per Entry

High-Rise Commercial 2 x JRC-14 3 x 100 mm

Buildings
(Primary and Redundant)
Hotels 2 x JRC-14 3 x 100 mm
(Primary and Redundant)
Utility and Services 2 x JRC-14 2 x 100 mm
(Primary and Redundant)
Table 4-1: Entrance Facility Requirements per Building Type

 Full route diversity is possible only when telecom routes are 100% physically separated,
so that damage to the first route cannot affect the second. Therefore, as highlighted in
the table above, there should be a minimum of six 100 mm conduits entering the
commercial building from at least two physically diverse points of entry (three conduits
per entry). Each set of conduits should terminate in a different primary MH outside the
building as depicted in the figure below.

© Dubai Design District, All rights reserved. Page 37 of 291

 Figure 4-1: Entrance box representation

 An entry box HH or a MH in the ground that the technician can open to access the
network are required for maintenance, connecting additional drop cables, or
troubleshooting.
 The specifications of the MH or the HH are generally provided by the service provider
providing the services. Other design points are mentioned below.
 Two MHs should be on two opposite sides of the building inside the plot boundary wall,
ensuring diverse paths. The MH should be of type JRC-14 or approved by service
provider.
 The entry box MH should be constructed of reinforced concrete structure with a heavy-
duty ductile iron frame and cover of rating grade” A”. The cover should be marked
“Telecom” or “Telephones”.
 The entry box MH should be constructed at least one meter inside the plot boundary wall
or demarcation line. The building contractor should be responsible for the entry box MH
construction.
 An earth rod must be provided at the entry box. The earth impedance should not be
more than five ohms (5Ω).

[Link].3 Entry Pipes (Lead-in ducts)

The entry pipes are usually uPVC ducts which should be extended from the entry box toward
building premises and the service provider line plant location. Other details are mentioned below.

 Entry pipes should be laid at a depth of at least 600 mm from the proposed finished
paving level. The entry pipe must be protected with concrete to prevent damages. Entry
conduits should be sloped away from the building.
 Entry pipes should be extended to the entry box and beyond to the nearest existing
service provider plant location, or one meter from plot limit.
 The entry box MH should have 3x100 mm ducts leading into the entrance room.
 Where optical Fibre cables will be used, consider placing three inner ducts of 38 mm
[1.5 in] inside each 103 mm (four trade size) conduit designated for this purpose to
ensure physical cable protection.
 Each inner duct should be provided pull ropes made of nylon of minimum six mm
diameter.

© Dubai Design District, All rights reserved. Page 38 of 291

  The lead-in ducts should be appropriately sealed to ensure that water, gas, and pests do
not enter the facility.
 The open ends of the entry pipe should be properly sealed, to prevent entry of sub-soil
materials and ingress of water.

[Link].4 Termination/Distribution Point in Building

Buildings larger than 10,000 square meters (100,000 square feet) must contain dedicated room(s)
for entrance facilities. If the building owner can’t provide these entrance facility rooms for a
service provider’s cable termination due to limitation of available space, it is recommended
terminating service provider cable in the MTR.
The cable termination/distribution point is usually a small cabinet where the telecom cables
coming from the entry boxes are terminated. These termination points can be inside the building
but not more than 15 meters from the building entry sleeves. The termination/distribution point
can be a space within the MTR. While constructing this facility the following guidelines should be
observed.

 A cable pull box of minimum size 600 mm (length) x 600 mm (width) x 800 mm
(diameter) must be provided.
 The maximum distance allowed for outdoor cables to go inside the building must be
limited to 15 meter (50 feet)
 A maintenance clearance of 900 mm (36 inches) is required in front of all cabling or
equipment panels

[Link] Main Telecom Room

The MTR should be a centrally located, dedicated room big enough to house telecommunications
equipment and backbone cabling terminations. This room is also referred as main cross-connect
(MC), campus distributor (CD), or main distribution frame (MDF). This is to be provided either on
the ground floor or basement for the purpose of terminating telecommunication cables for the
commercial buildings.
In case of high-rise commercial and other mission-critical buildings, two MTR’s are recommended
in the ground level to ensure equipment redundancy and high availability of the telecom services.
In all other type of buildings one room should be provided at the basement or ground floor.
Main Telecom Rooms are generally considered to be building or campus serving and they provide
connection point between backbone (vertical) and service provider cabling.

 The MTR can be co-located with the TER.

 All installation should be done in conformance with ANSI/TIA-568-C standards, local
standards, and the manufacturer’s standards.
 As stated above, a separate and dedicated room should be provided at ground floor or
basement level for the purposes of terminating telecommunications cables from
entrance facility with the rest of the structured cabling subsystems of the commercial
building.
 The minimum size for the MTR is dependent on the total net usable-able floor area of
the building as outlined in Table 4-2.

Usable Area Minimum Size of MTR

Usable area less than 1000 m2 4 x 5 x 3 (L x D x H) meter
Usable area between 1000-4500 m2 6 x 4 x 3 (L x D x H) meter

© Dubai Design District, All rights reserved. Page 39 of 291

 Usable area larger than 4500 m2 6 x 4 x 3 (L x D x H) meter
Table 4-2: MTR Minimum Size Requirement

 The MTR should be free of all safety hazards and should have no suspended ceiling.
 The MTR should be secured from unauthorized access and available to service provider
personnel and authorized commercial building staff on a 24 hour x 7 days per week x
365 days per year.
 Electronic and smart card access control solution should be employed.
 A clean class one earth should be provided in the MTR. Earth impedance is to be less
than one ohm (1 Ω).
 Depending on room usage, a raised floor of 450 mm should be provided in the MTR.
 The MTR should be provided with emergency lighting (50% of the room lights should be
on emergency backup), smoke detector and fire alarm, which should be incorporated
into the building automation system (BAS) or building management system (BMS).
 The room should be protected with a gas-based fire suppression system. An
appropriately sized automatic clean agent-based fire extinguisher (for example FM-200,
Inergen, or a similar product) is required for the room. Appendix-1 has more details on
gas-based fire suppression systems.
 Proper fire suppression should be provided for all penetrations of walls by cables, trays,
conduits, etc. by Underwriters Laboratories (UL) approved sealants.
 All telecommunication and network components shall be powered by an uninterrupted
power supply (UPS) to ensure continuous functionality for core services in the event of
power failure.

Recommendation for d3
Keeping in view the limitations detailed at the beginning of Section 4 it is necessary that physically
separate Smart City MTR with its own door and access control is built for supporting the Smart
City Network of d3.
For d3 the Smart City MTR will contain Distribution and Access fibre for the surrounding
neighbourhoods. It may also contain active equipment like the Smart City Distribution Switches
and will contain the fibre cross connect in case the room caters as the distribution point for up to
five buildings. Buildings that don’t have any distribution equipment planned in the Tertiary PoP
will only have racks that aggregate the fibre from the building Floor Telecom Rooms and the
neighbouring four buildings. This room however will contain other active equipment necessary for
building system automation, Security system and any other equipment specific to Smart Services
within the building. The size of the Tertiary PoP for d3 shall be 4 x 3m (12 sq. meters). It is
recommended to be in the ground floor of each building. Please note that this room shall not
house any equipment or fibre pertaining to the regulated services provider.

[Link] Floor Telecom Room

The FTR is required within any building to provide the link between the backbone and the
horizontal cable infrastructure. The FTR is also referred as horizontal cross-connect (HC), floor
distributor (FD), or intermediate distribution frame (IDF). The equipment within the FTRs should
be, but not limited to, the following:

 Service providers active equipment (if any)

 Active and passive racks
 Backbone and horizontal linking
 Containment system for power and telecommunications

© Dubai Design District, All rights reserved. Page 40 of 291

  Environmental controls
 Power conditioning and backup systems
 Fire detection and suppression systems

The location and the size of the FTR can be decided based on the size of the building and usable
floor space, the following design considerations should be followed by the construction contractor
when preparing this design requirement. These recommendations should apply to all the telecom
rooms.

 At least one separate and dedicated FTR should be provided on each floor of a
commercial building for the purpose of terminating telecommunications cables from the
vertical and horizontal cabling systems.
 In case the usable floor area to be served is greater than 1,000 square meters (10,000
square feet), architecting a second FTR is highly recommended. The second room may
be used by service providers or for landlord services.
 If a second FTR is required, both FTRs should be as far apart as possible - generally on
two separate edges of floor.
 The farthest distance of a work area from the FTR should not exceed 90 meters (i.e.
Patch Panel to RJ45 outlet).
 A rule-of-thumb estimate - usable floor space at 80% of total floor space.

Serving Area Minimum Size of FTR

Larger than 1000 m2 Multiple FTR required

≥ 800 m2 to ≤ 1000 m2 Minimum size of FTR 3 x 3.4 meter

≥ 500 m2 to ≤ 800 m2 Minimum size of FTR 3 x 2.7 meter

≥ 325 m2 to ≤ 500 m2 Minimum size of FTR 3 x 2.1 meter

≥ 100 m2 to ≤ 325 m2 Minimum size of FTR 2.1 x 1.5 meter

Less than 100 m2 Shallow closet that measures at least 0.6 m

deep x 0.6 m wide or approved
Telecommunications Enclosure or 12U
enclosure
Table 4-3: Minimum TR Sizes

 When there are multiple FTR’s on a single floor, it is recommended to interconnect these
rooms with at least one cable tray of 300 x 50 mm. With multiple FTR’s higher levels of
redundancy can be attained.
 It is recommended that 100% power backup in the FTR for critical ICT load.
 Consideration should be given to provide at least 50% power backup from UPS if
necessary for a critical ICT load.
 The vertical shaft opening for the riser pathways linking to the MTR and other telecom
rooms in the other floors to be in safely accessible areas and to be sized based on the
riser containment.
 For high-rise buildings, the vertical riser shafts must be big enough to accommodate two
450 x 50 mm cable trays.

© Dubai Design District, All rights reserved. Page 41 of 291

 If the containment system is being designed by others, as a guide only, the maximum number of
U/UTP cables installed on a tray should be as shown below; however this may need to be reduced
for bends etc.
Size of Tray Number of Cat6A/Class EA UTP Cables
100mm 85 UTP Cables
150mm 130 UTP Cables
300mm 255 UTP Cables
450mm 420 UTP Cables
Table 4-4: Cable tray sizes

Careful consideration must be taken when designing a containment system containing fibre
components in respect to bend radius etc.

 The FTR should be secured from unauthorized access and available to the service
provider personnel and authorized facility management staff on a 24 hour x 7 days per
week x 365 days per year basis.
 Electronic and smart card access control solution be employed.
 The FTR environmental and other requirements should be as follows:
o All high-level service to be identified and be made visible. Any type of false
ceiling is not recommended.
o A clear height of three meters should be maintained between high-level services
and floor- finished level when designing the FTR.
o Active and passive rack layout should be designed in a way to maximize
optimum used area with full accessibility for each rack from front and rear with
800 x 800 x 2,300 mm space for each rack.
o Design should consider the maximum number of racks that can fit within the FTR
and size all the environmental systems and power requirement accordingly.
o A 300 mm antistatic calcium sulphate raised floor with 8.8 kN (kilo Newton)
concentrated load per tile should be provided.
o A cable tray at high level (2.4 meter from floor-finished level) should be provided
from the room entrance up to each proposed rack location.
o Epoxy paint with a two-hour fire rating under the raised floor and a light colour for
room ceiling and walls should be provided to minimize dust and enhance room
lighting.
o 0.9x2.0 (in meters) lockable door with two-hour fire rating, fully opening outward
to provide additional usable space within TR. The door to be perfectly sealed to
prevent dust ingress to the room.
o Sufficient HVAC system required to maintain room temperature and humidity
must be provided.
o FTR must have a proper fire-fighting protection system, smoke and fire
detectors, and fire alarm system.
o Power requirements should be decided based on the room size and total number
of racks.
o The lighting system is important and must be designed in a way to allow
recognition of colours clearly, since many systems within telecommunications
rooms depend on colour coding.
o The FTR should be free of all safety hazards and should have no suspended
ceiling.
o No unrelated equipment or systems, such as water or sewage piping, ducts, or
building power distribution lines should be near or surround an FTR.

© Dubai Design District, All rights reserved. Page 42 of 291

 o The FTR should have no wet utilities, either above it or next to it.

Recommendations for d3
Keeping in view the limitations detailed at the beginning of Section 4 it is necessary that physically
separate Smart City FTR with its own door and access control be built for supporting the Smart
City Network of d3.
The Smart City FTR will house all the Smart City building fibre backbone terminations, horizontal
copper terminations from the floor. This room will also house the Smart City Active Network
Access switches and other associated hardware necessary for the operations of the floor. This
room shall contain all building system related equipment. The size recommendations for Smart
City FTR are listed in the table below:
Serving Area Minimum Size of FTR

Larger than 1000 m2 Multiple FTR required

≥ 800 m2 to ≤ 1000 m2 Minimum size of FTR 3 x 2.7 meter

≥ 500 m2 to ≤ 800 m2 Minimum size of FTR 3 x 2.1 meter

≥ 100 m2 to ≤ 500 m2 Minimum size of FTR 2.1 x 2.1 meter

Less than 100 m2 Shallow closet that measures at least

0.6 m deep x 0.6 m wide or approved
Telecommunications Enclosure or 12U
enclosure
Table 4-5: Smart City FTR Recommended Size

[Link] Telecom Enclosure

The TE is a relatively small, passive only enclosure, which caters to areas not accessible from
the FTR. TEs generally house cable terminations and cross connections. The TE can be used
when only passive components and no active equipment will be installed on the floor. Specific
details are outlined below.

 The TE should serve an area not greater than 335 square meters (3,600 square feet).
 The TE should be designed based on the size of the building and type of required
services.
 The TE is much smaller than an FTR and can be a wall-mount secured cabinet.
 The size of the TE should be based on cabling size and the type of services required;
these must be decided during the design stage.
 The TE should be a 19-inch wall-mount 9 rack units to 15 rack units high with 515 mm
depth cabinet with horizontal and vertical cable organizer, four-way rack-mount power
strip, and a fan tray for air circulation within the cabinet.
 The TE should to be located in a properly secured, environmentally suitable area, with
access limited to authorized staff only.
 The TE location should have a proper lighting minimum equivalent to 500 lux with one
dual single phase 220V 13A power socket.

© Dubai Design District, All rights reserved. Page 43 of 291

 [Link] Apartment / Villa Consolidation Point (ACP)
ACP is a wall-mounted secured cabinet to house a Home Access Gateway (HAG) device located
in each apartment within the residential or mixed used building. It terminates the apartment
horizontal cabling on patch panels/IDC modules, two or four core fibre cable from MTR/MDF,
power sockets, and UPS.
The location of the CP cabinet should be at a common point, where all of the internal conduits
meet and the structured cabling system (SCS) on a star topology can be installed. However, the
farthest wall socket shall not exceed 90 meters from the cabinet.
The ACP could be a 19-inch wall mount cabinet with 515 mm depth and horizontal and vertical
cable organizer, four-way rack-mount power strip, and fan tray for air circulation within the cabinet.
The ACP should be located in a properly secured, environmentally suitable area, and access
should be limited to authorized staff only. The CP location must have a proper lighting minimum
equivalent to 500 lux with one dual single-phase 220V/13A power socket.
Recommendations for d3
Two-core fibre cable from the Smart City MTR or 2 x Cat 6 or higher cables from FTR must be
terminated in the ACP. In case of a villa it has to be only Fibre and not Cat6 Cable for connectivity
between the ACP and the Nearest Pop. In the interest of saving space within the apartment it is
recommended that du and d3 share the same ACP. This connectivity can be used in case the
tenants want to extend or use some of the d3 Smart Services. The ACP will house the du HAG
and the Smart City HAG in case it is needed. The ACP will also have the du fibre that will be
terminated in the MTR or each building.

[Link] Office Consolidation Point (OCP)

OCP is a wall-mounted secured cabinet to house the Customer Premises Equipment (CPE)
located in each commercial unit within a commercial or mixed use building. It terminates the
Office horizontal cabling on patch panels/IDC modules, two or four core fibre cable from
MTR/MDF, power sockets, and UPS.
The location of the OCP cabinet should be at a common point, where all of the internal conduits
meet and the structured cabling system (SCS) on a star topology can be installed. However, the
farthest socket shall not exceed 90 meters from the cabinet.
The OCP could be a 19-inch wall mount cabinet with 515 mm depth and horizontal and vertical
cable organizer, four-way rack-mount power strip, and fan tray for air circulation within the cabinet.
The OCP should be located in a properly secured, environmentally suitable area, and access
should be limited to authorized staff only. The OCP location must have a proper lighting minimum
equivalent to 500 lux with one dual single-phase 220V/13A power socket.
Recommendations for d3
Four-core (Two for day one use and two for future) fibre cable from the Smart City MTR or 4 Cat
6 or higher cables from FTR must be terminated in the OCP. In the interest of saving space within
the apartment it is recommended that du and d3 share the same OCP. This connectivity can be
used in case the tenants want to extend or use some of the d3 Smart Services. The OCP will
house the du CPE and the Smart City CPE in case it is needed. The OCP will also have the du
fibre that will be terminated in the MTR or each building.

[Link] Retail Consolidation Point (RCP)

RCP is a wall-mounted secured cabinet to house the Customer Premises Equipment (CPE)
located in each commercial or mixed-use building. It terminates the Retail unit horizontal cabling

© Dubai Design District, All rights reserved. Page 44 of 291

 on patch panels/IDC modules, two or four core fibre cable from MTR/MDF, power sockets, and
UPS.
The location of the RCP cabinet should be at a common point, where all of the internal conduits
meet and the structured cabling system (SCS) on a star topology can be installed. However, the
farthest socket shall not exceed 90 meters from the cabinet.
The RCP could be a 19-inch wall mount cabinet with 515 mm depth and horizontal and vertical
cable organizer, four-way rack-mount power strip, and fan tray for air circulation within the cabinet.
The RCP should be located in a properly secured, environmentally suitable area, and access
should be limited to authorized staff only. The RCP location must have a proper lighting minimum
equivalent to 500 lux with one dual single-phase 220V/13A power socket.
Recommendations for d3
Four-core (Two for day one use and two for future) fibre cable from the Smart City MTR or 4 Cat
6 or higher cables from FTR must be terminated in the RCP. In the interest of saving space within
the apartment it is recommended that du and d3 share the same RCP. This connectivity can be
used in case the tenants want to extend or use some of the d3 Smart Services. The RCP will
house the du CPE and the Smart City CPE in case it is needed. The RCP will also have the du
fibre that will be terminated in the MTR or each building.

[Link] Telecom Equipment Room - General Specifications and

Requirements
A TER provides space and maintains a suitable operating environment for large
telecommunications and/or computer equipment. It is recommended that the buildings should
have space for TER to cater for ICT equipment, security, and BMS. The following points should
be noted:

 Business-critical buildings are recommended to have two TERs (primary and backup) to
house external telecommunications connections (entrance facility), core networking
equipment and backbone cabling terminations (from Telecom Rooms (TRs), TCs and
server room)
 All other buildings should have single TER at the ground floor or basement
 In case of residential and other small commercial buildings, the TER can be collocated
with MTR/MDF

[Link].1 General Fit out Design Considerations

Some of the design considerations for some of the most common fit out areas are mentioned
below.

 The TER should be located away from sources of high voltage and not be in close
proximity to any garbage rooms
 The TER must meet the space requirements specified by the equipment provider(s)
 If the TER will contain equipment servicing different telecommunications applications
(e.g., voice and data), each application’s space and layout requirements must be taken
into account

When the size and quantity of all ICT equipment is not known, the amount of floor space that the
room will serve is used to determine the minimum size of the TER. The following steps can be
used to determine the minimum size of a TER.

© Dubai Design District, All rights reserved. Page 45 of 291

 S No. Area Calculation
#1 Usable Area Total Area x 0.8
#2 Size of Work Area (WA) #1 / 10
#3 Size of BAS Area #1 / 23
#4 ER Size for WA #2 x 0.07
#5 ER Size for BAS #3 x 0.02
#6 Total ER Size (Sq. Meter) #4 + #5
Table 4-6: TER Sizing Requirements

[Link].2 Raised Floor Specifications

Specific raised-floor specifications are mentioned below.

 The raised-floor system must be provided for all type of telecom rooms.
 An anti-static floor – pedestals must be earthed throughout with minimum 450 mm
height from concrete base ready to accommodate a tile size of 600 mm x 600 mm.
 Tiles must be fire resistant, using calcium sulphate coating or any other fire retardant
material. The conductivity resistance from the slab surface should be in the range
1.5x105 to 2.0x110 ohms.
 The minimum raised floor load rating (distributed load) must be 4.8 kPa (102 lb/ft2) and
the rating for concentrated loading must be greater than 8.8 kilo Newton (KN) (2000 lbf)
in areas that will support telecommunications equipment.
 The entry points for external cables (i.e., routing to site duct system) should be managed
in cable raceways or HDGI cable trays mounted below a raised floor in parallel to the
equipment cabinet rows.
 The basket/tray is to be sized at 450 x 50 mm to accommodate large volume of copper
and Fibre cables.

If the containment system is being designed, by others, as a guide only, the maximum number of
U/UTP cables installed on a tray should be as shown below; however this may need to be reduced
for bends etc.
Size of Tray Number of Cat6A/Class EA UTP Cables
100mm 85 UTP Cables
150mm 130 UTP Cables
300mm 255 UTP Cables
450mm 420 UTP Cables
Table 4-7: Cable tray size requirements

Careful consideration must be taken when designing a containment system containing fibre
components in respect to bend radius etc. Copper and fibre cables should be installed on
independent trays or segregated by a barrier. Note Cat6A has been referenced as based on
outside diameter.
The layout of the cable containment and cable basket/tray work will be based on the room layout.

© Dubai Design District, All rights reserved. Page 46 of 291

 [Link].3 Door Requirements
Specific door requirements are mentioned below.

 The door must open outward.

 The entry must be ramped at equal height of raised floor with anti-dust coating, entry
keypad / card reader to be linked to the access control system.
 The TER entry door must be of steel construction and fire retardant with a minimum
rating of two hours.
 An auto door closer is to be provided on the door be it single panel or dual panel door.
 The minimum required door dimension (clear opening) is 1.8 meter (W) x 2.3 meter (H)
with no centre post or doorsill.

[Link].4 Civil Services

Specific civil services are mentioned below.

 The TER is to be completely free of utility piping carrying any form of liquid.
 No location above the room should have any sanitary equipment.
 If a wet area exists above the TER, an attic slab will be required (note requirement for
three-meter clear height) and waterproofing membrane must be provided and tested.
 Any services pipes or utilities other than main equipment cables and links should not
pass through the TER.
 Avoid placement of the TER close to garbage areas or wet utilities.
 The TER should be free of all safety hazards and should have no suspended ceiling.
 If a TER is proposed in the basement, an automatic pump draining system must be
provided to handle water seepages.
 The pipes leading to the air-conditioning units, Closed Control Air Conditioning Units
(CCU) or Fan Control Units (FCU) must be well clear of the rack locations.
 The air-conditioning units, CCUs, or FCUs must not be located directly over the rack
areas.

[Link].5 Electrical Power

Specific electric power requirements are mentioned below.

 The electrical system must comply with the local water/electricity authority and
international standards.
 A separate supply circuit serving the TER should be provided and terminated in its own
electrical panel.
 If a standby power source is available in the building, the TER panel should be
connected to the standby supply.
 The standby generator should feed UPS load, rectifiers, 50% of standard lighting, and
standby A/C units.
 All telecommunication and network components shall be powered by a UPS to ensure
continuous functionality for core services in the event of power failure.

[Link].6 Environmental Requirements

Estimates suggest that for each kilowatt of power used by cabinet equipment, additional 1/3 of
kilowatt is needed for cooling. Since TERs operate continuously, the challenge for designers is
to find the right balance between space, cooling, and energy consumption. If equipment is spread

© Dubai Design District, All rights reserved. Page 47 of 291

 out over many cabinets, the cooling requirements per cabinet are reduced but the size of the
space to be cooled increases.

 The TER must be air-conditioned and temperature must be maintained at 20° ±3°
Celsius.
 The room should be air conditioned with a minimum of one air change per hour.
 Primary and assistant CCU to be fitted and interlocked with each other.
 Relative humidity (non-condensing) must be maintained at 50 ± 10 %.
 The TER must contain a manual / automatic controlled air conditioning switch and must
digitally display temperature for operators.
 The ambient temperature and humidity should be measured at distance of 1.5 meter
(five feet) above the floor level, after the equipment is in operation, at any point along an
equipment aisle centreline. Sample TER containment thresholds are noted below.

Contaminant Concentration
Chlorine 0.01 ppm
Dust 100 µg/m³/24h
Hydrocarbons 4 µg/m³/24h
Hydrogen Sulphide 0.05 ppm
Nitrogen oxides 0.1 ppm
Subpart dioxide 0.3 ppm
Table 4-8: TER Contaminant Thresholds

[Link].7 Electromagnetic Interference

Specific electromagnetic interference points are mentioned below.

 The room should be located away from sources of electromagnetic interference.

 Main voltage electrical cables must not be routed through the TER.
 Special attention should be given to electric power supply transformers, motors and
generators, c-ray equipment, radio or radar transmitters, and induction sealing devices.

[Link].8 Lighting Requirements

Specific electromagnetic interference points are mentioned below.

 Average illumination level of 500 lux measured one meter above the finished floor is
required in the TER. Lighting should be minimum of 500 lux (50 foot candles), measured
at one meter (three feet) above the finished floor in middle of all aisles between
cabinets.
 Lighting should be controlled by one or more switches located near the entrance doors
to the room.
 Light controls should be able to interface with the BMS.
 The lighting fixtures should not be powered from the same electrical distribution panel as
the telecommunications equipment in the TER.
 Dimmer switches should not be used.
 Thirty minute emergency lighting and signs should be properly placed such that an
absence of light will not hamper emergency exit.

© Dubai Design District, All rights reserved. Page 48 of 291

 [Link].9 Fire Suppression System
A specific fire suppression system is required for the TER. Details are mentioned below.

 An automatic fire suppression system using clean agent inert gas (such as FM-200 or
Inergen) based on local standards/regulations is required at ceiling height and below the
raised floor.
 Gas integrity testing must be carried out on the room.
 A local civil defence certificate (or similar government agency) will be required for the
TER.
 The type of firefighting system needs to be decided based on the TER size and active
equipment planned to be located inside it.
 An appropriately sized automatic fire extinguisher (dry powder type) can be used and
should be fixed to the ceiling in an appropriate location.
 Fire stops are mentioned in Annex A of the standard ANSI/TIA-569-C.

It is strongly recommended that the contractors and consultants look into the National Codes for
fire and safety.

Figure 4-2: Typical Fire Stop Representation

[Link].10 CCTV/Monitoring System

Specific CCTV/Monitoring system points are mentioned below.

 Minimum of one camera/monitoring point is required.

 Camera/monitoring system placement will allow for recognition and identification of all
incoming personnel to the room.
 An allowance is to be made for one 13A socket at 2200 mm above finished floor for the
camera/environmental monitoring system.
 It is strongly recommended that an IP camera, which can be powered by a Power-over-
Ethernet (PoE) switch is placed.
 In case a PoE switch is not available, the CCTV/monitoring system must be powered by
a UPS power source.

[Link].11 Uninterrupted Power Supply

Specific UPS points are mentioned below.

© Dubai Design District, All rights reserved. Page 49 of 291

  Consideration should be given to provide 100% power backup from UPS/Generator to
critical ICT load.
 Space should be considered to allocate UPS; size depends on the TER usage and
areas that will be served by the TER.
 In cases where a room’s size can’t accommodate UPS, or the UPS load is higher than
the loading capacity of TER floor, the designers should consider a separate room for the
UPS based on UPS type, capacity, and the backup time required.

[Link].12 Acoustic Noise

Specific acoustic noise points are mentioned below.

 Noisy equipment should be located outside of the TER.

 Specify sound barriers if sources of unacceptable noise cannot be located outside the
TER.
 Typically noise sources in TERs are faulty fans of servers or racks, air conditioning units,
UPS, and power generators.

4.1.3 Structured Cabling

Within any building, a structured cabling subsystem (SCS) contains two basic parts:

 Horizontal Distribution System

 Backbone Distribution System

The SCS should support the following applications on a converged IP platform:

 Data, video, digital, and analogue voice applications

 Building automation systems
 Other building signalling systems, including: fire, physical safety and security, HVAC &
car park system

Flexibility, future changes, simplicity, and ease of maintenance are the main factors which should
be considered when designing the SCS.
Each part of the SCS has to be properly labelled, including all telecommunications infrastructure
and equipment components. Other reasons for labelling are mentioned below.

 Labelling prevents confusion with similar components.

 Labelling must be legible and permanent enough to last the life of the component.

In some systems the components can have a 20- to 30-year life or more. Pathways in a building
normally have the same life as the building, which can approach or exceed 25 years.
The following infrastructure and equipment components should be labelled:

 Telecommunications spaces
 Telecommunications pathways
 Telecommunications cables
 Connecting hardware
 Grounding system
 Telecommunication equipment

© Dubai Design District, All rights reserved. Page 50 of 291

 Telecommunications spaces are to facilitate SCS termination, cross connection, and interlinking
between horizontal cabling system and backbone distribution system, in addition to housing active
equipment.

[Link] Horizontal Distribution System

[Link].1 Horizontal Pathways and Cable Containment Capacities
Horizontal pathways extend between the telecommunications room and the work area. Additional
details are listed below.

 Types of horizontal pathways include the following:

o Under Floor System

o Flush Ducting System
o Surface Raceway System
o Raised Flooring
o Ceiling Distribution System
o Conduit System

 The containment system must be designed to take into account the 90-meter maximum
horizontal cable length from patch panel to RJ45 outlet at the work area.
 In suspended ceiling and raised floor areas where duct, cable trays, or conduit are not
available, flush ducts or cable trays must be installed and bundle (50 or less) horizontal
cabling with cable ties snug, but not deforming the cable geometry.
 Plenum-rated or LSZH cables and cable ties should be used in all appropriate areas.
 Velcro ties are highly recommended.
 Cables should not be attached to lift out ceiling grid supports or laid directly on the
ceiling grid.
 Care should be taken to ensure that the cable trays are smooth and no sharp edges
exist at joints, ends, or other section of the tray.
 Cables should not be attached to, or supported by, fire sprinkler heads or delivery
systems or any environmental sensor located in the ceiling air space.
 Very careful consideration must be taken when designing a containment system
containing fibre components in respect to bend radius.
o Refer to subsequent subsections for minimum bend radius requirement for fibre optic
cables.
 Duct usable area is the calculation of the internal area that can be occupied by wires or
cables.
 The usable area (UA) is affected by the cross-sectional dimension of duct, diameter of
cables, space between the cables, straightness of the cables, and bending radius.
o Considering these factors, the usable duct area is equal to an average of 90% of the
nominal area, or (W x H) x .90.

© Dubai Design District, All rights reserved. Page 51 of 291

 Figure 4-3: Conduit Usable Area and Factors Affecting It

 It is strongly advised not to use shared cable trays to distribute telecommunications and
electrical power cables.
 The capacity of the containment system should be determined from the standard tables
shown below. This specification must be followed as a guideline when deciding upon the
size of trunking/cable tray to be installed. No trunking or cable tray should be more than
60% on initial installation or launch, leaving the remaining 40% for expansion. Please
note that these capacities are based on cable diameters of 5.893 mouse of larger-
diameter cables will result in larger containment systems requirements. It is the
responsibility of the design consultant to ensure that the containment system will
accommodate the requirements of the SCS.

Cable Tray Size Trunking Size (mm) Number of Unshielded Twisted

(mm) Pair (UTP) Cables
50 x 50 50 x 50 55
75 x 50 50 x 75 82
100 x 50 50 x 100 110
100 x 50 75 x 75 110 - 123
150 x 50 75 x 100 165
200 x 50 100 x 100 220
300 x 50 150 x 150 330
450 x 50 150 x 150 495
600 x 50 - 660
900 x 50 - 990
Table 4-9: Maximum Capacity Containment- U/UTP Cat6 Cables

Size of Tray Number of Cat6A/Class EA UTP Cables

100mm 85 UTP Cables
150mm 130 UTP Cables
300mm 255 UTP Cables
450mm 420 UTP Cables
Table 4-10: Maximum Capacity Tray Containment- U/UTP Cat6A/Class EA Cables

© Dubai Design District, All rights reserved. Page 52 of 291

  The wiring capacity of trunking shall be determined from the standard tables as shown
below. The specification is a guideline that must be followed when deciding upon the
size of trunking to be installed. It is based on the formula that for each 25mm x 25mm
cross section, 10 cables can be accommodated and the stipulation that no trunking
should be more than 40% full on installation.

Size of Trunking Number of Cat6A/Class EA cables

50mm x 50mm 25 U/UTP Cables
50mm x 75mm 38 U/UTP Cables
50mm x 100mm 51 U/UTP Cables
75mm x 75mm 57 U/UTP Cables
75mm x 100mm 76 U/UTP Cables
100mm x 100mm 102 U/UTP Cables
150mm x 150mm 230 U/UTP Cables
Table 4-11: Maximum Capacity Trunking Containment- U/U/UTP Cat6A/Class EA Cables

 Additional horizontal pathways and cable containment approaches are highlighted

below. They include flush ducting, surface raceway, raised flooring pathways, ceiling
distribution, and overhead pathways.

© Dubai Design District, All rights reserved. Page 53 of 291

 Figure 4-4: Typical Horizontal Pathways and Containment Systems

[Link].2 Horizontal Conduits and Spacing

The use of conduits as a horizontal raceway system should only be considered when:

 Outlet locations are permanent

© Dubai Design District, All rights reserved. Page 54 of 291

  Device densities are low
 Flexibility is not required
 The minimum size of a conduit pipe used as a horizontal pathway from the distribution
box to the telecommunications outlet should be 25 mm (one inch)

Figure 4-5: Pictorial Representation – Conduits

 If the conduit is 51 mm (2") then bend radius can be six times the internal diameter. If
above 51 mm, then bend radius should be 10 times the internal diameter.
 A minimum of one nylon draw wire must be installed in a conduit.
 Pull boxes should be located such that they are readily accessible at all times. They
should be spaced at a maximum of 15 meters apart to minimize cable stress during
installation and to provide serviceability in the future.
 Conduits must be free from sharp edges, to prevent cable damage during and
subsequent to pulling.
 Conduits protruding through a floor should be terminated at a minimum of 50 mm from
the floor to prevent water or other liquids from flowing into the conduits.
 Maximum fulfilment of duct or pathway should be 40%, but should never go above 60%.
 Conduit capacity is critical to the successful installation of a SCS
 It is essential that conduit is adequately sized to allow placement and removal of cables.
 The minimum recommended conduit trade size is 21 mm (¾”).
o The table below highlights conduit sizing details.
o Capacities are based on cable diameters of 5.893 mm.
o Use of larger diameter cables will result in larger conduit systems being required.
 It is the responsibility of the contractor based on the site conditions to ensure that the
containment system will accommodate the requirements of the SCS.

Conduit Trade Size Internal Diameter Fill Area (mm2) # of Cat 6 cables
(mm)
¾” / 21 mm 19.30 292.5 3
1” / 27 mm 25.40 202.6 6
1¼” / 35 mm 34.04 363.8 10
1½ “/ 41 mm 39.88 499.3 15
2” / 53 mm 51.31 826.6 20

© Dubai Design District, All rights reserved. Page 55 of 291

 Table 4-12: Conduit Trade Sizes

[Link].3 Horizontal Cabling

The guidelines in this section are aligned with the horizontal cabling requirements as specified in
the following sites:

 BICSI manual
 ANSI/TIA-568-C-1
 Commercial Building Telecommunications Cabling Standard Part 1: General
Requirements

Horizontal cabling must be designed to accommodate diverse user applications, including:

 Data /voice and video communications

 Wireless access points (WAPs)
 BMS (including HVAC, lighting control, energy management, elevator control, and
pumps)
 Other building signalling systems, including fire alarm and physical safety and security
 Avoiding electromagnetic interference

Consideration should be given to incorporating building information systems (e.g., community

antenna television [CATV], alarms, security, audio, or other telecommunications systems) when
selecting and designing horizontal cabling.
The horizontal cabling system includes:

 Work area telecommunications outlets

 Horizontal cables
 Patch panels at TR and MTR
 Patch cords
 Racks to house SCS patch panels.

Horizontal cables must be installed in star topology. Loops, splices, and joints are not acceptable.
Horizontal cable must be installed applying best practices to avoid cable damage during cable
laying process.
Cable Type Maximum Horizontal Length

4 pair 100 Ohms U/UTP cable 90 meters

2 or more strand of LOMM OM4 90 meters
50/125 micron Fibre Multimode
Cable
Table 4-13: Cable Types for Horizontal Cabling

When designing horizontal cabling subsystems, the following should be considered:

 If the interior build out of an office space is the tenant’s responsibility, then horizontal
cabling installation will be carried out by the tenant itself. The building owner will provide
backbone connectivity to the network.

© Dubai Design District, All rights reserved. Page 56 of 291

  The CAT6 cabling system shall be CMP or LSZH listed, 100 ohms, 24 AWG, 4 Pair,
unshielded twisted pair of 4+0 FEP construction, compliant with ANSI/TIA-568-C-2, ISO
class E performance with swept frequency to at least 250 MHz.
 Cat6 UTP cable shall be used as horizontal cables to connect each telecommunications
outlet in the work area to the backbone subsystem on the same floor located in the floor
telecommunication room.
 The length of cable permanent link between the farthest telecommunications outlet and
the distribution box should not exceed 90 meters (295 feet).
 In addition to the 90 meters of horizontal cable, a total of 10 meters is allowed for work
area and telecommunications room patch cords, cross connects, and jumper cables to
make a channel.
 Consolidation point, cross connects, or multi-user telecommunication outlet assembly
can be considered when the design requires more flexibility, but it should not increase
the horizontal total cable length to more than 90 meters.
 A 10 meter length for patch cords from equipment and work area side is maximum
acceptable in a channel length.
 All SCS cables are to be properly labelled and terminated on both sides, and follow
ANSI/TIA-606-B standard, in the RJ45 sockets located in in-patch panel or in CAT 6-
compliant IDC modules.
 Station cables and tie cables installed within ceiling spaces should be routed through
these spaces at right angles to electrical power circuits.
 The building owner is responsible for replacement of in-building cables and other fixtures
if they become faulty after the one-year maintenance period.
 Cable diagrams including floor layouts, room layouts, rack elevations, schematics, and
detailed drawings must be for approval at the design stage.
 All installation should follow only after "approved for construction" drawings are made,
submitted by the contractor, approved by the consultants. Once the work is completed
as-built detail drawings should be submitted before the signoff of the project.
 Completed SCS will be subject to acceptance.
 Design and performance of the SCS system is the responsibility of the installer.
 Any upgrade required to in the in–building facility or telecommunication cables, due to
either enhanced demand, change in building status, or damage should be provided by
building owner.

The supply and termination of UTP cables on patch panels or IDC modules and sockets locations
should be the responsibility of the installers/owners.
Specification Category 6
Frequency Range 1 - 250 MHz
Attenuation at 100 MHz 19.8 dB
NEXT at 100 MHz 44.3 Db
Power sum NEXT at 100 MHz 42.3 dB
Power sum ACR 15.4 dB
ELFEXT at 100 MHz 27.8 dB
Power sum ELFEXT 24.8 dB
Return Loss 20.1 dB
Table 4-14: Specifications of Cat6 cable

© Dubai Design District, All rights reserved. Page 57 of 291

 Table 4-15: Specification of Cat6A Cable

 All conductors in each cable should be connected to a single RJ45 socket at the work
area outlets and patch panel.
 The 4 pair UTP cable should be UL listed type MPR, MPP, CMR, or CMP.
 Each cable should be terminated to maintain the twists in each pair up to within 5 mm of
the termination.
 Proper strain relief should be provided for the cable at the outlets and patch panel,
avoiding strain on the conductors.
 The contractor should adhere to the cable manufacturers’ requirements for bending
radius and pulling tension of all data and voice cables.
 Numbering and colouring of the pairs should be as defined as per ANSI/TIA-568
EN50173 and ISO11801 Edition 2.2 Generic Cabling Standards and is required for a
Category 6 or Class E link.
 Horizontal cable must be designed in star topology.

[Link].4 Patch Panels

Horizontal cables must not connect directly to telecommunications equipment. Instead, use
suitable connecting hardware and equipment cable to make the connection. It is important to
locate patch panels and cross-connect blocks so that the combined length of cables and cords
used to connect equipment in the work area and TR plus the patch cable does not exceed 10
meters. Additional details are mentioned below.

 Terminate all Cat6 cables from the work area to standardized Cat6 patch panels located
at TCP or floor telecom rooms.
 Properly label the cables and patch ports.
 Terminate all fibre cable on SC or small form factor LC connectors.
 The terminated SC or LC connectors will then be installed into couplers mounted in the
patch panels and outlet plates.
 All terminations should be installed into a 1U-fiber or fibre termination shelves or any
other high-density optic-patch shelf.
 These shelves can accommodate a maximum of 48 or 144 with a typical fibre optic SC
or LC connector.
 Make the most of the space available by using high-density solutions like angled patch
panels and vertical cable management with matched fingers, which will fit more
connections into a smaller footprint.

© Dubai Design District, All rights reserved. Page 58 of 291

  Patch panel connectors should match CAT6 or beyond ANSI/TIA standards, to maintain
the CAT6 or beyond channel performance.
 Modular RJ45 CAT6 or beyond patch panel is recommended when number of UTP
cable terminations is less than 48.
 IDC CAT6 or beyond patch panel is recommended in the TR and MTR, especially when
the total number of UTP cable terminations is more than 48.

[Link].5 Work Area

The work area (WA) includes those spaces in a building where occupants normally work and
interact with their telecommunications equipment. These work areas need telecommunications
services that can be made available from the FTR via the cabling system. Other work area details
are mentioned below.

 Typically, for an office floor, the recommended WA is based on international standards

of 10 square meters (100 square feet) in size and should have at least two (2) Cat-6
UTP outlets.
 Recommended WA size for retail space is 47 square meters.
 A minimum of two connection sockets should be provided in every outlet.
 Each of these connections has a separate cable run to the telecommunication distributor
with no splices or joints, and no looping to second or subsequent socket
 Each cable shall have a one-meter slack at the telecommunication distributor.
 For the BAS application in the office space, the average work space is 25 square
meters, with one port each for lighting control, camera, and HVAC.
 Consider other services to have access at higher levels (or even in the ceiling) such as
WAP, CCTV, alarms, sensors, and other IP-connected devices
 Proper labelling system shall be applied on all sockets, outlets, and both ends of all
cables.

Figure 4-6: Pin/Pair Assignment

 All terminations for the horizontal cables have to follow 568B assignment, following the
ANSI/TIA-568-C standard as mentioned below.
 Work area outlet connectors should be mounted in two, four, six, or eight gang utility
outlet boxes either with angled or flush port faceplates.
 Faceplates should be dual white PVC plated.

© Dubai Design District, All rights reserved. Page 59 of 291

  The use of any special faceplate, such as brass finish, should be approved by the
architectural consultant.
 Floor boxes should be used where wall partitioning is not available.
 The WA telecommunications outlet box should be located near an electrical outlet (e.g.,
within 1 m [3 ft.]) and installed at the same height if appropriate.
 The WA telecom outlet distribution should be closely coordinated with furniture layout.
 Sufficient space must be provided in the telecommunications outlet box or equivalent
space, so that minimum cable bend radius requirements are not exceeded.
 The location, mounting, or strain relief of the telecommunications outlet/connector shall
allow pathway covers and trim to be removed without disturbing the cable termination.
An example of this is presented in the figure below.
 10% of total outlets are proposed to be above false ceiling for the connection of WAPs,
IP cameras, and IP-based sensors.
 Fire smoke sensors, occupancy sensors, lighting controls, and HVAC controls are
generally connected to their respective controllers by RS-485 communication bus.
 BMS field devices are not required to connect to the IP network.
 Digital logic controllers that are IP based, such as Mediator, are required to connect to
the IP network.
 For BAS, the respective devices could be installed at any level including roof, wall, floor,
doors, or windows.
 Final layout of the cables shall be done once the devices and respective solution are
identified.

[Link] Backbone Cabling System

A backbone distribution system is the part of an SCS system that provides connection between
TRs, MTRs, and TEFs.
A backbone system includes:

 Intra-building connections between floors in multi-floored buildings

 Inter-building connections in campus-like environments

[Link].1 Risers from Main Telecom Room to Individual Floors

Risers are required in multiple-floored buildings for the installation of telecom fibre optic cables
and copper backbone cables from MTR to other floors. Specific details are mentioned below.

 Each building should provide access to cable risers with unrestricted flow between each
basement-level MTR room and the FTR on each floor of the building.
 The risers should provide a minimum internal clearance width of 1,000 mm and a
minimum depth of 500 mm, and allow no co-location of other utilities or power cabling to
avoid damage to the planned optical fibre runs.
 Galvanized slotted iron cable trays (minimum one300 mm x 50 mm Heavy Duty, Return
Flange, or HDRF) should be provided from the MTR to each FTR, and extended up to
the RTR.
 Galvanized slotted iron cable trays (minimum one600 mm x 50 mm HDRF should be
provided between primary and redundant MTR (if any).
 The risers to each floor must be symmetrical and vertically in line with the MTR and
TER.
 A 300 x 50 mm cable tray should have four 100 mm sleeve through floor, or one floor
slot 350 mm wide.

© Dubai Design District, All rights reserved. Page 60 of 291

  Cable sleeves or slots should be positioned adjacent to a wall on which the backbone
cables can be supported. Sleeves or slots must not obstruct wall terminating space.
 Ensure that proper fire suppression is maintained in the floor openings.

Figure 4-7: Typical Sleeve and Slot Installations

 Open cable shafts should be used when available and where large quantities of cables
are required on a floor that is distant from the main MTR.
 Do not locate backbone cable pathways in elevator shafts.
 Where the TER, MTR, FTR, and RTR are not to be located one below the other in a
vertical line, continuous cable trays/conduits must be provided with pull boxes/access
panels at every turning point and at interval of 15 meters each up to the TER.
 Right angle or sharp bends are to be avoided.
 The telecom cable trays should have adequate separation from electrical cable trays.
 Electrical cable trays should not cross the telecom cable trays.
 If for any reason they have to cross, maintain a 90 degree angle.
 In every case diverse routing is required; therefore the contractor shall build secondary
vertical risers along with proper cable containment systems as specified above.

[Link].2 Backbone Cable General Consideration

To ensure the backbone cabling can accommodate data, voice and video transmission and other
building applications, the following should be considered:

 Length of the backbone segments

 Type of media used
 Voice and data networking equipment needs

Additional backbone details are documented below.

 Fibre optics will be used as a major type of backbone cable.

 A separate dedicated cable tray should be provided for fibre optic cables.
 Since fibre optic cable is delicate in nature, it requires separate containment for pulling
and future maintenance.
 The minimum bend radius of a vertical cable tray should be based on the minimum bend
radius of the cable that will be installed in the conduit, providing that the cable
information is available (150 mm x 50 mm).

© Dubai Design District, All rights reserved. Page 61 of 291

  A unique identifier should be assigned to each backbone cable and should be marked
on each end.
 Intra-building backbone cables are one-level hierarchical star or two-level hierarchical
star.
o Both approaches provide some level of path diversity for vertical cabling.
o The exact selection would be based on the layout and the usable area of the
commercial building.

Figure 4-8: FTTx Architecture for a typical group of Towers

 Backbone systems must comply with building, electrical, fire rating, and all other
applicable codes.
 All pathways should be protected by a fire suppression system.

Please note FTTx requires end-to-end connectivity on fibre optic cable. This would ensure 1
Gbps connectivity to each user. However, Cat6 UTP could be considered in building from MTR
to each office, designated healthcare area, or retail outlet, provided the distance doesn’t exceed
90 meters. Fibre optic (SM or MM) cable is highly recommended in a multi-floored building
environment.
Fibre 12-Core Cable Cable Tray Size for Indoor Cable (mm)
(Outside diameter 5.8 – 6.0 mm)
5 cable 75 x 50
7 cable 100 x 50
10 cable 150 x 50

© Dubai Design District, All rights reserved. Page 62 of 291

 20-25 cable 300 x 50
30-35 cable 450 x 50
40-45 cable 600 x 50
Table 4-16: Specs for Multilayer Cable Trays for Vertical Risers with 40% Fill Ratio

[Link].3 Cable Containment, Routing and Installation

During the design stages of the building, segregation of power and the SCS must meet the
requirements of power separation guidelines by the IEEE regulations, based on a suitable design
of a cable containment system by the MEP consultant or others.

 Copper data cables should not be installed near sources of electromagnetism.

 The standard ANSI/TIA-569 specifies these distances for structured data cabling
systems and cabling pathways standard are mentioned in the table below.

Minimum Separation Distance from Power Source as Per Standard ANSI/TIA- 569
Minimum Separation Distance from Power Source <480V
Condition <2 kVA 2-5 kVA >5 kVA
Unshielded power lines or electrical equipment in 130 mm 300 mm 600 mm
proximity to open or non-metal pathways
Unshielded power lines or electrical equipment in 65 mm 150 mm 300 mm
proximity to grounded metal conduit pathway
Power lines enclosed in a grounded metal conduit 50 mm 150 mm 300 mm
(or equivalent shielding) in proximity to grounded
metal conduit pathway
Transformers and electric motors 1000 mm 1000 mm 1000 mm
Fluorescent lighting 300 mm 300 mm 300 mm
Table 4-17: Minimum Separation Distance from Power Source

 ANSI/TIA-569-C (which superseded ANSI/TIA-569-B) provides design specifications and

guidance for all building facilities relating to telecommunications cabling systems and
components.
 The vertical backbone risers and cables trays must be designed using the shortest
routes possible from the main TER to the respective FTR.
 Interlink backbone cables linking adjacent communication rooms or closets will again
take the shortest routes for both primary and secondary routes.
 Adjacent telecom rooms are defined as being on the same level, or as agreed upon
during design meetings.

[Link].4 Vertical Backbone Cable Type

Backbone cables need to be chosen based on variety of requirement and trade-offs, because
there is a wide range of services and site sizes accommodated by backbone cabling system.
The following are recognized backbone cables by ANSI/TIA-569-C and ISO/IEC 11801 Ed.2.2:
2010:

© Dubai Design District, All rights reserved. Page 63 of 291

  50/125 and 62.5/125 µm multimode optical cable
 Single mode optical cable

Each recognized cable has individual characteristics that make it useful in a variety of situations.
In some situations, a single cable type may not satisfy all the user requirements. In these cases,
more than one medium in the backbone cabling must be used. The different media should use
the same facility architecture with the same locations for cross-connects, mechanical
terminations, inter building TERs, and other facilities.

Application Wavelength Maximum Supported Distance ( Meters )

62.5/125 µm 50/125 µm 50/125 µm SM
OM3/4
Campus 1300 2000 2000 Not a
Backbone of Standard
155 Mbps
(megabytes
per second)
Campus 1300 550 5000
Backbone of
1 Gbps
(gigabytes
per second)
Building 300 300 Not a
Backbone of Standard
1 Gbps
Building 850 300/550 Not a
Backbone of Standard
10 Gbps
Table 4-18: Fibre Backbone specifications

The right type of fibre cables will be selected once the active equipment for the building would get
finalized but in this section a brief introduction to fibre cabling media. Performance depends not
only on the fibre selected but also on the type of laser that is used.
The common transmitters for fibre optics can fit into three simplified categories:

 Light-emitting diodes (LED’s) - LED’s are low-cost, but they are limited to lower bit rates
that fall well below 1 Gb/s
 Long wavelength lasers- Long wavelength lasers operate at the 1310 nm (newton
meter) and 1550 nm wavelengths with much higher speeds and much higher cost
 Short wavelength lasers- Short wavelength lasers operate at the 850 nm wavelength.
Vertical Cavity Surface Emitting Laser (VCSEL) technology was developed as a means
to manufacture a low cost laser in an affordable package. VCSELs for 10 Gbps are
currently classified as short wavelength.

The three fibre categories mentioned above, when combined with short and long wavelength
laser technology, gives several choices that have trade-offs between distance and cost. Tight
buffered cable should be used inside commercial buildings for vertical fibre optic backbone
cabling.

© Dubai Design District, All rights reserved. Page 64 of 291

 [Link].5 Fibre Backbone Infrastructure Design Criteria
The backbone will consist of industry standard 8.3/125 μm, single mode fibre, 62.5/125 μm, or
50/125 μm (OM3) fibre cables. This document recommends installing standard fibre optic cable
using the quantity of cores to be calculated during network capacity planning. All fibre cores
should be terminated on industry standard small form factor (SFF) LC connectors. All
terminations should be installed into a 1U-fiber or fibre termination shelves or any other approved
optic patch shelf. These shelves can accommodate a maximum of 48 or 144 with a typical fibre
optic LC connector.
Multimode fibre should be considered whenever the distance between TERs is less than 300
meters. SM (single mode) fibre has to be used when the distance between TERs is more than
300 meters. In some cases it can be considered even if the distance is less than 300 meters.
Tight-buffered cables are desirable because of the features below:

 Increased physical flexibility

 Smaller bend radius for low fibre count cables
 Easier handling characteristics in low fibre counts
 Fibre backbone cabling should be terminated using star topology.
 Fibre optic cable should be indoor/outdoor type, buffered and grouped in 6-fiber
subunits.
 Optical fibre backbone cable listed as Optical Fibre Nonconductive Plenum (OFNP) only
should be deemed acceptable...
 The cable’s minimum bend radius must not be exceeded. Bending cable tighter than the
minimum bend radius may result in increased optical fibre attenuation or optical fibre
breakage. Indoor backbone optical fibre cables should have a minimum bend radius of
10 times the cable’s outside diameter when under no load and 15 times the cables
outside diameter when being pulled.
 All fibre cores should be terminated on industry standard SC or SFF LC connectors
 Fibre cores should be terminated on to the SC/LC connector using the fusion splicing
method or direct epoxy and polish method to the fixed fibre cores.
 The terminated SC or LC connectors will then be installed into couplers mounted in the
patch panels.

[Link].6 OM4 LOMMF

Parallel transmission solutions employing multiple multimode fibres especially in Data Centres
and in backbone applications are the most cost-efficient fibre solution available for data rates that
exceed the modulation capability of today's 850-nm lasers, such as 40 Gbps and 100 Gbps, which
is why IEEE 802.3 selected this technique for next-generation Ethernet. Deploying a multimode
cabling infrastructure that offers a migration path to parallel transmission, with the option to use
either multiple fibres or multiple wavelengths, prepares the network for these higher data rates at
the lowest total cost.
Multimode LOMMF Cable- OM4: Supports 550 Meter Channel @ 10 Gbps OM3: Supports 300
Meter Channel @ 10 Gbps.
The cable shall support current and next-generation LAN, SAN, and WAN applications via laser-
optimized 50/125-µm optical Fibres.
The cable shall extend the distance of low-cost 850-nm VCSEL-based electronics, supporting
1100 m at 1 Gbps and 550 m at 10 Gbps.
The application suite shall include Ethernet from 10 Mbps to 10 Gbps, Fibre Channel from 1 Gbps
to 10 Gbps, and ATM/SONET/SDH from OC-1 to OC-192.

© Dubai Design District, All rights reserved. Page 65 of 291

 [Link].7 Multimode Fibre Variants
Multimode fibre has enabled longer distances at higher speeds within the data centre such as:

 100BASE-FX – 100Mb/s up to 2 kilometres

 1000BASE-SX – 1Gb/s up to 550 meters
 10GBASE-SR – 10Gb/s up to 550 meters
 40GBASE-SR4 – 40Gb/s up to 100 meters of OM3
 100GBASE-SR10 – 100Gb/s up to 100 meters of OM3
 40GBASE-SR4 – 40Gb/s up to 150 meters of OM4
 100GBASE-SR10 – 100Gb/s up to 150 meters of OM4
 40GBASE-SR4 – 40Gb/s up to 150 meters of OM4
 100GBASE-SR10 – 100Gb/s up to 150 meters of OM4

Figure 4-9: Tight Buffered Fibre Optic Cable

[Link].8 Grounding and Electrical Protection

Standard ANSI/TIA-607-B should be followed for all earthing and bonding requirements. The
designer must consider the following:

 Lighting
 Ground potential rise
 Contact with electrical power circuits
 Electromagnetic interference

A telecommunications main grounding bus bar (TMGB) serves as a dedicated extension of the
building grounding electrode system for the telecommunications infrastructure. It also acts as the
central connection point for telecommunication bounding bus bar (TBB) and equipment.

 One TMGB should be used per building.

 Telecommunications bonding backbone interconnecting bonding conductor (TBBIBC)
should be used to interconnect TBBs.
 Telecommunications grounding bus bar (TGBs) located in a telecommunications room
or equipment room should serve as a common central point of connection for
telecommunications systems and equipment in the area served by that TR or equipment
room.
 All telecom rooms should have a TBB and be connected to the TMGB.
 The TGB must be located so that it is accessible to telecommunications personnel.

© Dubai Design District, All rights reserved. Page 66 of 291

  The TGB can be located in the entrance room or the main TER with the location chosen
to minimize the bonding conductor length for telecommunication connections.
 The TMGB must be a pre-drilled copper bus bar with standard National Electronic
Manufactures Association (NEMA) bolt hole sizing and spacing for the type and size of
conductor being used, a minimum of 6 mm (0.23 inch) in thickness, 100 mm (4 in.) wide
and of variable lengths,
 Ensure the size of the bar allows for future growth.
 Keep one foot additional length for future connections.
 Additional detailed about grounding are mentioned in the figure below referencing an
industry standard.

Figure 4-10: Scope of Standard 607 for Telecom Grounding

 TGB should be pre-drilled copper bus bar provided with standard NEMA bolt hole sizing
and spacing for type of connectors to be used with minimum size 6 mm (0.23 in.) thick
by 50 mm (2 in.) wide and of variable lengths.
 TBBs and other TGBs located in same space must be bonded to the TMGB.
 Bonding conductors used between a TMGB, TBB, and TGB must be continuous and
routed in the shortest straight-line path possible.
 The TGB must be installed as close as practical to the panel board.
 When a panel board for telecommunications is located in the same room as the TGB,
the panel boards or the enclosure to the TGB should be bonded.
 Bonding to the metal frame of a building shall be done in those buildings where metal
frames (structural steel) are effectively grounded, bond each TGB to the metal frame
within the room using a No. 6 AWG conductor,
 If the metal frame is external to the room but readily accessible, bond the TGB to the
metal frame using a No. 6 AWG conductor,
 Two separate Class 1 earth bar to be supplied for AC and DC active equipment and
these should be entirely separate from the building earth.
 Grounding should also include any raised floor installations,

© Dubai Design District, All rights reserved. Page 67 of 291

  The clean earth to be provided in each TER, properly sized, based on room size and
active equipment plan,
 Earth impedance must to be less than 1 ohm.
 All metallic pathways are to be bonded and grounded, such as cable trays, raised floor
pedestals, GI conduit, and racks.
 A schematic drawing of the earthing is to be provided by the contractor before
commencement of project
 An example of bonding as per the ANSI/TIA-607-B industry standard is mentioned in the
figure below.

Figure 4-11: Example of Bonding as Per ANSI/TIA-607-B

© Dubai Design District, All rights reserved. Page 68 of 291

 Figure 4-12: Example of Bonding as Per ANSI/TIA-607-B

4.1.4 ISP No Objection Certificate Requirements

The purpose of the no objection certificate (NOC) is to ensure that later stage contractors would
abide by the principles and methods of the initial approved design. The NOC forces new
contractors to adhere to the rules and regulations established by submitting their changes/design
for pre-approval.

[Link] Design and Construction

During the design phase of any building, a design and construction NOC must be received from
the d3. The following information and documentation is required:

 Completed design NOC application form

© Dubai Design District, All rights reserved. Page 69 of 291

  Plan drawing of affected area
 Detailed SCS building floor drawings showing equipment room positions, layouts, and
SCS containment systems
 SCS schematic drawing
 Electrical single line diagram pertaining to telecommunications
 Port map showing port distribution on a per service / per IDF / per floor basis

All of the above should be submitted in two hard copies and one up-to-date soft copy (AutoCAD
format) for the NOC to be processed. In case the drawings are initially rejected, the resubmission
should include the first five bullet points above and an updated softcopy.
Incomplete submissions should be returned to the applicant.
Any modification or changes in the approved drawing will void the NOC. The
consultant/contractor will need to resubmit for a new NOC.

[Link] Material no Objection Certificate

Prior to the installation of the SCS, a material no objection certificate must be received from d3.
The following documentation is required in order to process the material no objection certificate:

 Copy of approved design and construction drawings

 Design brief and summary sheet
 Vendor system performance warranty and 3rd party (UL or ETL) certificate of
compliance with Cat6/Cat6A component level requirements as specified in ANSI/TIA-
568-C.2: Balanced Twisted-Pair Telecommunication Cabling and Components
Standard, 2009
 Vendor system performance warranty and 3rd party (UL or ETL) certificate of
compliance with Fibre optic as per ANSI/TIA-568-C.3: Optical Fibre Cabling
Components Standard, 2010
 Certificate of authorization of installer
 Products Catalogue (technical product description)
 Compliance statement to EEC specifications
 The SCS installer will provide the telecom room layouts indicating the rack elevations
during the material NOC process

[Link] Site Inspections

d3 management reserves the right to make periodic site inspections to verify the working practices
of the installer during the installation phase.

[Link] Handover and Acceptance

After any work completion, SCS should request the following documents as part of the handover
and acceptance procedure:

 Completion certificate issued by consultant

 Copies of approved site inspection forms (if applicable)
 As-built drawings in hard and soft copy (AutoCAD) including rack elevations and
schematic diagram
 Hardcopy of all cable test results
 Copy of manufacturer’s warranty certificate

© Dubai Design District, All rights reserved. Page 70 of 291

  One master key for all the telecom rooms which may require access by d3 staff should
be made available and handed to d3

[Link] NOC Validity

The d3 NOC remains valid until any changes are proposed by the contractor.
d3 reserves the right to cancel any issued NOC in the event of any inconsistent changes to the
approved SCS or cabling containment system. In the event that an NOC is cancelled, the
consultant is required to resubmit the drawings in order for a new NOC to be issued.

4.2 Connected Real Estate Basis of Design

This section provides the connectivity and functional requirements of the building systems to be
compatible with the IP Network. It is also important to note that user interfaces and endpoint
devices that users interact with must be compliant with various forms of accessibility options
wherever necessary.

4.2.1 HVAC Control

[Link] System Description
A control system, in general, enables equipment to operate effectively and sometimes gives
the ability to change their actions as time goes on and conditions or occupancies change. Control
can be of devices used to monitor the inputs and regulate the output of systems and equipment.
The major goal of the HVAC (Heating Ventilation and Air-conditioning) system and its control
is to provide a comfortable environment suitable for the process that is occurring in the facility.
In most cases, the HVAC control system’s purpose is to provide thermal comfort for a building’s
occupants to create a more productive atmosphere (such as in an office) or to make a space
more inviting to customers (such as in a retail store). In order to regulate the environment, the
HVAC control system regulates the movement of air and water, and the staging of heating,
cooling, and humidification sources of the equipment in a building.
Here it is important to note the difference between the HVAC system and the HVAC Control
System:

The HVAC system consists of the hardware equipment provided by the MEP
(Mechanical, Electrical and Plumbing) contractor. The HVAC system is
independent from the HVAC control system.

The HVAC control system, on the other hand, also referred to as the BMS system
(Building Management System) is the hardware and software equipment
provided by the BMS contractor. The HVAC control system is adapted to the
HVAC system implemented in the building.

Another capability that is expected of modern control systems is energy management. This
means that while the HVAC control system is providing the essential HVAC functions, it should
do so in the most energy efficient manner possible. Safety is another important function of
automatic controls. Safety controls are those designed to protect the health and welfare of people
in or around HVAC equipment, or in the spaces they serve, and to prevent inadvertent damage
to the HVAC equipment itself. Examples of some safety control functions are: limits on high and

© Dubai Design District, All rights reserved. Page 71 of 291

 low temperatures (overheating, freezing); limits on high and low pressures; over current protection
(e.g. fuses); and fire and smoke detection.
In short, a properly designed HVAC Control system provides a comfortable environment for
occupants, optimize energy cost and consumption, improve employee productivity, facilitate
efficient manufacturing, control smoke in the event of fire and support the operations team with
easy to manage user interfaces with automated, distributed intelligence.
The HVAC Control System, comprises of control devices, sensors and actuators. The controllers
integrate inputs from the sensors, have local intelligence and take action according to the
programmed logic to control the connected equipment or devices connected to it. The system can
either be stand-alone for small installations, but are generally computerized and networked in
larger installations. A networked system has a central monitoring station to enable the building
operators to monitor the different parameters of the building, identify abnormality, identify
maintenance requirements, generate reports of monitored parameters and manage the entire
system from one central location. These systems typically use multiple distributed controllers
placed near the controlled equipment. One or more network controllers are used to integrate the
remote terminal unit controllers on to a central station / IP network, and they communicate with
one or more personal computer that are used as the operator interface. Such networked control
systems installations are typically used on large commercial and industrial buildings to allow
central control of many HVAC units around the building(s). Most of the new-generation controllers
communicate on IP directly and few have a web server built-in allowing remote access from a
web browser.
A sample of the HVAC equipment generally monitored and controlled by the HVAC control
systems includes:

 Air Handling Unit

 Fan Coil Unit
 Variable Air Volume Box
 Boiler Systems (For Heating)
 Mechanical Ventilation Fans (Exhaust Air Fan, Fresh Air Fan, Toilet Exhaust Fans, Car-
park Exhaust Fans)
 Variable Speed Drive
 Pumps and Plumbing Equipment
 Thermostat

Typically the HVAC Control system comprises of three layers:

 The Field Layer: Includes the sensors, actuators and other devices which help gather
the information or take action and connect to the local controller
 The Automation Layer: Typically includes the controllers which are used to monitor and
control the connected equipment.
 The Management Layer: The application, which the operators use to monitor and
control the HVAC points, is a part of this layer. It consists of the management of the
controller connected to the network.

[Link] System Components

[Link].1 Non-IP (Internet Protocol)
Traditionally the field devices communicate with the controller on low voltage (0-10V), current
(0- 20mA) or resistive signals (Thermocouple, RTD etc.) and digital inputs (dry contacts) and
outputs. These sensors or actuators (for implementing the command) are powered from the

© Dubai Design District, All rights reserved. Page 72 of 291

 controller and are non-IP based. Some examples are sensors (used for temperature, humidity
and pressure monitoring) actuators, motors for valves, transducers such as current transducer
used for electricity current, power meters, ballast, photo sensors and occupancy sensors.
The sensors and output devices are connected to the controllers (referred to as DDC – Direct
Digital Control). The DDC in its turn implements the control function programmed in it and
communicates this information to the management station.
Non-IP sensors are becoming more IP based in HVAC systems. Various industry specifications
such as ASHRAE (American Society of Heating, Refrigerating and Air – Conditioning
Engineers) or CSI (Construction Standards Institute) Master Format will provide sufficient details
on this matter.
The list below assists in clarifying the non-IP devices related to the HVAC BAS real estate
subsystem. Please note certain non-IP devices can be used across different real estate
subsystems.

 Temperature Sensor
 Pressure sensor
 Flow meter
 Flow switch
 Actuators
 Valve motors
 Power meters
 Transducers
 Enthalpy sensors
 Window contact
 Differential pressure switch
 Damper actuator

[Link].2 IP Devices
With technological advancements today, there are many IP based sensors / wireless sensors
communicating either on WiFi, Zigbee or Mesh protocol which has changed the view of how
sensors had been traditionally looked at. IP based DDC controllers have started becoming a
norm for all new major installations, to take benefit of having a unified cabling infrastructure
and ease of maintenance.
The IP devices of the HVAC System are intelligent devices that have a computing capability
and connectivity to sensors and other signals. The list below includes the most common IP
devices in the HVAC System:

 Direct Digital Controller (DDC)

 Thermostat
 IP-Gateway
 Management stations (Centralized in CCC)
 User thin / thick clients
 HMI Interface (Portable Operator Terminals and handhelds)

[Link].3 Software
The management software component of the HVAC control system is the link between the
hardware and the user interface display. The following requirements should be taken into
consideration:

© Dubai Design District, All rights reserved. Page 73 of 291

  There will be one management software only for the management of the HVAC control
field devices of all the project zones: one cost only regardless of the size of the project
 The HVAC Management System shall be used for programming purposes only and
will be transparent to the user
 This management software needs to expose its data to the d3 data virtualisation layer
 The management software shall be capable of integration to and providing alerts to d3
CCC
 The management software shall be capable of leveraging d3 designated service
enablement layer
 The HVAC control system will not need a Graphical User Interface (GUI) as the
maintenance team will have only one eye view on the building systems provided by the
mediation layer
 The user interface of the mediation layer will be used to monitor the HVAC control
system
 The HVAC server will be web enabled and rack mounted

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Specific Technical Requirements

In order to have a converged architecture, the main technical requirements are listed below:

 The HVAC controllers shall be IP based

 The HVAC controllers shall have an RJ45 port
 The HVAC controllers shall be compatible with the Layer 3 IP network
 The IP-enabled controllers on each floor will be connected to the unique IP network of
the building
 The HVAC controllers shall be integrated to the mediation layer
 The system integrator implementing the mediation layer may be separate from the
HVAC control vendor

An example of HVAC single line diagram and logical architecture are presented in Figure 4-13
below:

© Dubai Design District, All rights reserved. Page 74 of 291

 Figure 4-13: HVAC Control Single Line Diagram

© Dubai Design District, All rights reserved. Page 75 of 291

 [Link] Smart Dubai KPI’s
Smart Dubai KPIs d3 Interpretation of the KPI
I6.4.6 Electricity supply system Parametric data provided by DEWA on a
management with ICT measures count by regular basis
ratio of electricity supply systems under
management with ICT help
I6.1.1 Application level of energy saving Number of ICT energy enabled Sensors
technologies in public buildings count by connected to the d3 CCC
ratio of public buildings that have energy
saving systems, including energy
conservation systems and clean energy
systems
I6.1.2 Percentage of public buildings with Number of buildings with integrated
integrated technologies count by ratio of technologies and BMS at d3
public buildings with building management
systems, communication and control
Table 4-19: Smart Dubai KPI's for HVAC Control

4.2.2 Lighting Control

[Link] Description
The lighting control system provides controls luminance in a way which is appropriate to the
needs and can reduce operating costs by providing energy-saving programs. It also provides
automated status reports, service displays, alarms etc.
The lighting control system is an important factor to be considered in the design of a building.
The lighting control system normally consists of the control of the following list:

 Lighting Circuits
 Lighting Control Panels
 Dimming Circuits

The lighting controllers operate similar to the HVAC controllers.

[Link] System Components

[Link].1 Non-IP Devices (Internet Protocol)
The lighting control systems have been low power devices on a communication network and
have not evolved as much as the HVAC control systems have. Typically the lighting control
system modules have distributed intelligence and memory, limited storage and address all the
connected devices. Most of the components in a lighting control and management system are
bus-powered and form small islands for communication on their automation network. At the
field level, the most common protocols in the lighting control industry are:

 European Installation Bus (KNX EIB)

 LON

© Dubai Design District, All rights reserved. Page 76 of 291

  BACnet
 Modbus
 C-Bus
 DALI

Most of the manufacturers have their components interconnected on a daisy-chain network

and communicating on one of the above protocols. Since the devices consume much less power
for their operation, the communication network also provides the required power supply for
the devices operation and the power supply module in each island of network provides power for
the devices.
In systems, where the communication bus provides only the medium for information exchange,
the modules are powered from a separate power source.
From the above information, it is imperative that the system is primarily comprised of non-IP
devices such as:

 Intelligent switches
 Sensors such as lux level, motion detectors etc.
 Modules for lighting control – switching, dimming etc.

Most of the lighting control system manufacturers have options to control other devices such
as blinds, with specialized modules.

[Link].2 IP Devices
For the lighting control system to be scalable, it has to communicate on IP and bridge the
different islands of communication. This is made possible with IP devices customized for each
manufacturer, providing the interface unit to connect the lighting automation network to IP.
With the advancements in technology, most manufacturers also have a touch-panel for
providing additional interface for managing the system. Typically the touch-panels are available
in two interface options – Local communication bus and IP.
Depending on the requirements and scale of implementation the system might also require a
management station. With respect to SEC and the plan to co-host the servers of different
systems in the CCC, the design shall integrate the lighting control system with the mediation
layer and make the information available through the GUI of the mediation layer.

[Link].3 Management Software

The software component of the lighting control system is the link between the hardware and
the user interface display. Similar to the HVAC control system the following requirements
should be taken into consideration:

 There will be one management software only for the management of the lighting
control field devices of all the project zones: one cost only regardless of the size of the
project
 The lighting management system shall be used for programming purposes only and
will be transparent to the user
 The lighting control system will not need a Graphical User Interface (GUI) as the
maintenance team will have only one view on the building systems provided by the
mediation layer
 The user interface of the mediation layer will be used to monitor the lighting control
system

© Dubai Design District, All rights reserved. Page 77 of 291

  The lighting control system will not need any dedicated control station or computer
 The lighting server will be web enabled and rack mounted
 The lighting management software will integrate to the mediation Layer

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Specific Technical Requirements

In order to have a converged architecture, the main technical requirements are listed below:

 The lighting controller shall be IP based

 The lighting controller shall have an RJ45 port
 The lighting controller shall be compatible with a Layer 3 IP network
 The IP-lighting controller on each floor will be connected to the unique IP network of
the building.
 The lighting controllers shall be integrated to the mediation layer
 The system integrator implementing the mediation layer may be separate from the
lighting control vendor

An example of lighting single line diagram and the logical architecture are presented in Figure
4-14 below:

© Dubai Design District, All rights reserved. Page 78 of 291

 Figure 4-14: Lighting Control Single Line Diagram

[Link] Smart Dubai KPI’s

Smart Dubai KPIs d3 Interpretation of the KPI
I6.4.6 Electricity supply system Parametric data provided by DEWA on a
management with ICT measures count by regular basis
ratio of electricity supply systems under
management with ICT help
I6.1.1 Application level of energy saving Number of ICT energy enabled Sensors
technologies in public buildings count by connected to the d3 CCC
ratio of public buildings that have energy

© Dubai Design District, All rights reserved. Page 79 of 291

 saving systems, including energy
conservation
systems and clean energy systems
I6.1.2 Percentage of public buildings with Number of buildings with integrated
integrated technologies count by ratio of technologies and BMS at d3
public buildings with building management
systems, communication and control
Table 4-20: Smart Dubai KPI's For Lighting Control

4.2.3 Smart Metering

[Link] System Description
The management of energy begins with monitoring of the resources. The key resources
monitored are the electrical power, water consumption, gas consumption and BTU energy. The
metering information can then be used as the foundational information to provide billing
services as per usage. The energy management system normally consists of monitoring the
utility consumption of electro mechanical equipment as shown below. The generated data
contributes then to various facilities management decisions. Meters can be categorized as:

 Energy meters for:

o Fans
o AHUs
o FCUs
o Pumps
o Lighting circuits
o Power Distribution Board
o Elevators and escalators
 Water meters
 Gas meters
 BTU meters

The granularity of metering depends on the requirements and can be extended for providing
billing services as per the needs.

[Link] System Components

[Link].1 IP Devices
Typically, meters are located close to the energy distribution, such as electrical distribution
boards for electrical power, floor distribution for BTU meters, near gas bank / distribution for gas
meters and distribution pipelines for water meters, which are accessible for manual reading.

[Link].2 Management Software

Apart from the meters, the manufacturers also have management applications that can monitor
the meters on the network, collect the information from the individual meters, store the information
and provide a billing application. Similar to the HVAC control system the following requirements
should be taken into consideration:
There will be one management software only for the management of the lighting control field
devices of all the project zones: one cost only regardless of the size of the project

© Dubai Design District, All rights reserved. Page 80 of 291

  The metering management system shall be used for programming purposes only and
will be transparent to the user
 The meter management software will not need a Graphical User Interface (GUI) as
the maintenance team will have only one eye view on the building systems
provided by the mediation layer
 The user interface of the mediation layer will be used to monitor the meters
 The meter management system will not need any dedicated control station or computer
 The meter management server will be web enabled and rack mounted
 The meter management software will integrate to the mediation Layer
 The meters could be managed with the same software as the HVAC control system

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Specific Technical Requirements

 Meters shall communicate on IP directly

 The meters will be connected to the unique IP network of the building at the floor level
 In case the meters used are non-IP, they will be converted to the IP network at a floor
level using an IP gateway
 The exchange of information shall be done using enterprise level information
exchange formats such as XML.
 The meters connect to the IP network and the network architecture provides the
required connectivity to the CCC.

An example of metering single line diagram logical architecture are presented in Figure 4-15
below:

© Dubai Design District, All rights reserved. Page 81 of 291

 Figure 4-15: Metering Single Line Diagram

© Dubai Design District, All rights reserved. Page 82 of 291

 [Link] Smart Dubai KPI’s
Smart Dubai KPIs d3 Interpretation of the KPI
I6.4.6 Electricity supply system Parametric data provided by DEWA on a
management with ICT measures count by regular basis
ratio of electricity supply systems under
management with ICT help (SmartGrid)
I3.1.8 Improvement of traditional industry Statistical data on GDP vs. traditional
with ICT count by ratio of GDP improvement business improvements measures
due to technology upgrade
I6.1.1 Application level of energy saving Number of ICT energy enabled Sensors
technologies in public buildings count by connected to the d3 CCC
ratio of public buildings that have energy
saving systems, including energy
conservation systems and clean energy
systems
I6.1.2 Percentage of public buildings with Number of buildings with integrated
integrated technologies count by ratio of technologies and BMS at d3
public buildings with building management
systems, communication and control
systems, etc.
I2.2.1 Level of civilian electricity usage (per Number of ICT energy enabled Sensors
capita) with ICT measures Count by ratio of connected to the d3 CCC
average civilian electricity consumption
saved this year compared with last year
I2.2.2 Level of industrial electricity usage Number of ICT energy enabled Sensors
(per GDP) with ICT measures Count by ratio and Smart Meters connected to the d3 CCC
of average industrial electricity (including
charging electricity driven vehicles)
consumption saved this year compared with
last year
Table 4-21: Smart Dubai KPI's for Smart Meters

4.2.4 Access Control

[Link] Description
Access control and integrated data allows the adoption of security and control measures
against clandestine and unauthorized access to the facility yet facilitating easy access to
legitimate user. There is a growing need for development of an architectural framework and
appropriate methodologies for realizing open access systems that would enable easy access to
shared resources for common users along with the fine grained access control in closed
administrative domains.
From a user perspective the access control system is composed of a sequence of the
following events:

 The user swipes/presents a card near a door/gate reader

 The door/gate reader then responds with either granting access or rejection of
request to enter

© Dubai Design District, All rights reserved. Page 83 of 291

  When granted, the door/gate is unlocked/opened and this allows the user to pass
through the restricted area.

From an administrator point of view, access control is a system that is composed of servers,
supporting applications, operator workstation, controllers, card readers and supporting field
elements (i.e. magnetic locks and other related devices).
Normally the access control system is made up of the following components:

 ID Credential
 Credential Reader
 Auxiliary Elements such as Door Strike, Contact and Exit Button
 Door Access Controller
 Client/Server System

These components are displayed in Figure 4-16 below:

Figure 4-16: Access Control System Schematic

A variety of technologies are available for access control as shown in Figure 4-17. They include:

 Magnetic Stripe
 Wiegand Strip
 Barium Ferrite
 Contactless: Proximity, RFID (Radio Frequency Identification Device), Smart Cards,
Near Field Communications (NFC).

© Dubai Design District, All rights reserved. Page 84 of 291

 Figure 4-17: Access Card Technologies

[Link] System Components

The Access Control System consists of field devices connected to door controller which in turn
are managed by a software application.

[Link].1 Non-IP Devices

The IP access control devices are connected to field devices and sensors through conventional
low voltage electrical wiring. A sample list of those field devices includes:

 Magnetic Locks
 Emergency Push Buttons
 Door Contacts
 Motion/Presence detection sensors

[Link].2 IP Devices
The IP access control devices also have an IP network interface connecting directly to the
network. The IP access control devices can be diverse. Some of the most common are:

 Door Access Controllers

 Optical Portals
 Turnstiles
 Card Reader
 Biometric Reader

For additional security, access readers can combine two or more technologies. The results of
comparing two identification technologies (e.g. biometric and RFID) are:

 A reduction of the number of errors

© Dubai Design District, All rights reserved. Page 85 of 291

  An addition of an authentication procedure

[Link].3 Client/Server System Software

The system includes an operator workstation, servers, software and database. The database
contains the updated information on users’ access rights. In a centralized server system design,
the ID credentials are received and the software validates the data with the latest updated user
list in the database and determines if the person’s access privileges remain the same.
In most Access Control System (ACS) designs, the server periodically sends updated access
control information to the door controller so that these controllers can make a local decision
validating users on the spot rather than depending on the centralized server for decision making.
The data format exchanged within the ACS is an important consideration since it specifies how
data is translated for interoperability. The format specifies the sequence and alignment of
the bits that comprise the control and access information.
ACS vendors have developed proprietary formats that prevent unauthorized persons from
breaking into the system unlawfully.
Similar to the HVAC management software, the following requirements should be taken into
consideration:

 There will be one management software only for the management of the access
control system of all the project zones: one cost only regardless of the size of the project
 The Access Control management software shall be used for programming purposes
only and will be transparent to the user
 The user interface of the mediation layer will be used to monitor the access control
system
 The access control system will not need any dedicated control station or computer
 The access server will be web enabled and rack mounted
 The access management software will integrate to the mediation Layer

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

© Dubai Design District, All rights reserved. Page 86 of 291

 [Link] Specific Technical Requirements

 The access control biometric reader and door controllers shall be IP based
 Wherever possible Power over Ethernet IP devices shall be considered
 The access control biometric reader and door controllers shall have an RJ45 port
 The access control biometric reader and door controllers shall be compatible with a
Layer 3 IP network
 The access control biometric reader and door controllers on each floor will be connected
to the unique IP network of the building
 The access controllers shall be integrated to the mediation layer
 The system integrator implementing the mediation layer may be separate from the
access control vendor
 The user interfaces and endpoint devices must be compliant with various forms of
accessibility options wherever necessary.

An example of access control single line diagram and logical architecture are presented in Figure
4-18 below.

© Dubai Design District, All rights reserved. Page 87 of 291

 Figure 4-18: Access Control Single Line Diagram

[Link] Smart Dubai KPI’s

Smart Dubai KPIs d3 Interpretation of the KPI
I3.1.8 Improvement of traditional industry Statistical data on GDP vs. traditional
with ICT count by ratio of GDP improvement business improvements measures
due to technology upgrade
I4.2.1 Accident prediction ratio Count by ratio Provision of ICT enabled cameras/ sensors
of various accidents successfully predicted monitoring accidents and connected to the
through ICT means d3 CCC

© Dubai Design District, All rights reserved. Page 88 of 291

 I4.2.2 Penetration of ICT for natural disaster Provision of ICT enabled natural disaster
sensors connected to the d3 CCC
Count by number of various sensors per
square kilometre in disaster-prone regions
I4.2.3 Publication rate of natural disaster Provision of ICT enabled natural disaster
alert Count by ratio of disasters that is alerted sensors connected to the d3 CCC
ahead of time each year
I4.2.4 Penetration of City video surveillance Provision of ICT enabled video cameras
connected to the d3 CCC
Count by land coverage ratio of video
surveillance
I4.1.2 Satisfaction with environmental safety Provision of environmental safety
satisfaction surveys/interviews
Count by ratio of satisfaction expression in
paper/online interview
I4.1.6 Satisfaction with crime prevention and Provision of crime prevention satisfaction
security control Measured by Security surveys/interviews
Feeling in paper/online interview. Add Crime
rate and case solve rate.
Table 4-22: Smart Dubai KPI's for Access Control

4.2.5 Video Surveillance

[Link] Description
The video surveillance is a key component in the safety and security of the buildings tenants,
residents and visitors. As an application, video surveillance has demonstrated its value and
benefits by:

 Providing real time monitoring of a facility’s environment, people and assets

 Recording events for subsequent investigation, proof of compliance/audit purposes

In addition, the value of video surveillance has grown significantly with the introduction of motion,
heat and sound detection sensors as well as sophisticated video analytics.
The video surveillance solution in general is made up of the following main components:

 IP Gateway Encoders
 IP Cameras
 IP Gateway Decoders
 Convergence Chassis
 Recorders (various types)
 Software for managing and collecting video streams into archive

Software for distribution and control of video streams onto real time display screens
Figure 4-19 below illustrates some of these components.

© Dubai Design District, All rights reserved. Page 89 of 291

 Figure 4-19: IP Video Surveillance System

The IP gateway encoders and decoders run the video management software, allowing them to
become part of a “virtual matrix switch (VMS)” that distributes both real time live and recorded
video traffic over an IP network.
The IP gateway encoders, decoders plus the convergence chassis are exclusively used with
analogue cameras. This basis of design focuses on the implementation of an IP video
surveillance, consequently we will address a restricted list of components which include:

 IP cameras
 Recorders (various types)
 Software for managing and collecting video streams into archive
 Software for distribution and control of video streams onto real time display screens

[Link] System Components

The video surveillance system is composed of hardware and software. Each component that
makes up the video surveillance system is described in the section below. Today, a complete
video surveillance system based on IP exists; therefore this system does not have the section
entitled “non- IP devices”.

[Link].1 IP Devices
The most common IP devices of the video surveillance system consist of the following list:

 Cameras
 Cables
 Displays
 Servers

© Dubai Design District, All rights reserved. Page 90 of 291

 [Link].2 Software
The software component of the video surveillance system is the link between the hardware and
the user interface display. The IP video surveillance system server is preferred to be a stable
operating system platform such as Solaris, Linux or other UNIX variants.
The management software shall have the following high level requirements:
Supports Ethernet TCP/IP connectivity including configuration and data export

 Software structure of the workstation interaction should be a standard client/server

relationship
 Server should be used to archive data and store system database
 Operator can access the server for all archived data
 Server supports a minimum number of simultaneous clients (this number should be
determined depending on the facility to be controlled)
 Fully loaded with internet technologies and ICT standards
 Advanced user interface accessible via a Web browser
 Provide a secured user access authentication

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Specific Technical Requirements

© Dubai Design District, All rights reserved. Page 91 of 291

 Figure 4-20: IP Network Centric Video Surveillance System

In a summary and as shown in Figure 4-20:

 The fixed indoor and outdoor SD (standard definition) and the HD (high definition)
cameras should have the following requirements:
o IP cameras
o PoE (Power over Ethernet) IEEE802.3af.
o Overlay capabilities to overlay Time, date and camera ID.
o Memory should be a minimum of 64 MB flash, and 128 MB SDRAM
o Should support the following protocols: Dynamic Host Control Protocol (DHCP),
File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Secure HTTP
(HTTPS), Network Time Protocol (NTP), Real-Time Transport Protocol (RTP),
Real-Time Streaming Protocol (RTSP), Simple Mail Transfer Protocol (SMTP),
Secure Sockets Layer/Transport Layer Security (SSL/TLS), Transmission
Control Protocol/Internet Protocol (TCP/IP)
o Should support Quality of Service DSCP markings
o Outdoor Cameras should be housed in a suitable enclosure
o At least the following certifications: FCC, CE, and UL
o IP filtering
o Data rate control
 Standard services supported by the server computer operating system to be located in
the CCC will include the following:
o Multi-tasking Multi-User Support
o TCP/IP Network Support
o Graphic Display Building Editor
o Database Services
o Application Software
 Software at the Operator Workstation located in the CCC shall comprise of:

© Dubai Design District, All rights reserved. Page 92 of 291

 o TCP/IP Networking
o Graphic Display Building Editor
o Application Software
 The networking software shall use the industry standard TCP/IP LAN protocol.
 The server shall be capable of acting as a file server for graphic displays, cardholder
photo images, recorded video images and other related files. All LAN connected
operator workstations shall be able to view custom displays and photo/video images
from the server computer.
 All system peripherals shall be capable of being connected to the server computer
via the LAN.
 The user interfaces and endpoint devices must be compliant with various forms of
accessibility options wherever necessary.

An example of video surveillance single line diagram and logical architecture are presented in
Figure 4-21 below:

© Dubai Design District, All rights reserved. Page 93 of 291

 Figure 4-21: Video Surveillance Single Line Diagram

© Dubai Design District, All rights reserved. Page 94 of 291

 [Link] Bandwidth Consideration
The bandwidth consumed by the IP video surveillance system is significant and should be fully
considered during the design of the project network.
The standard formula for the bandwidth calculation of an individual camera is:
Bandwidth = Image Size * Rate * Normalization
In addition cameras that are high definition (HD) consume more bandwidth than the cameras that
has standard definition (SD). The security consultant will need to determine the quality of camera
to be used depending on its location and use.
A general assumption is to consider on average a 2Mbps rate for the SD and 15 Mbps rate for
the HD cameras.

[Link] Smart Dubai KPI’s

Smart Dubai KPIs d3 Interpretation of the KPI
I3.1.8 Improvement of traditional industry Statistical data on GDP vs. traditional
with ICT count by ratio of GDP improvement business improvements measures
due to technology upgrade
I4.2.1Accident prediction ratio Count by ratio Provision of ICT enabled cameras/ sensors
of various accidents successfully predicted monitoring accidents and connected to the
through ICT means d3 CCC
I4.2.2 Penetration of ICT for natural disaster Provision of ICT enabled natural disaster
sensors connected to the d3 CCC
Count by number of various sensors per
square kilometre in disaster-prone regions
I4.2.3Publication rate of natural disaster alert Provision of ICT enabled natural disaster
Count by ratio of disasters that is alerted sensors connected to the d3 CCC
ahead of time each year
I4.2.4 Penetration of City video surveillance Provision of ICT enabled video cameras
connected to the d3 CCC
Count by land coverage ratio of video
surveillance
I4.1.2 Satisfaction with environmental safety Provision of environmental safety
satisfaction surveys/interviews
Count by ratio of satisfaction expression in
paper/online interview
I4.1.6 Satisfaction with crime prevention and Provision of crime prevention satisfaction
security control Measured by Security surveys/interviews
Feeling in paper/online interview. Add Crime
rate and case solve rate.
Table 4-23: Smart Dubai KPI's for Video Surveillance

4.2.6 Car Parking

[Link] Description
The car parking system is important because it services as the first point of contact a user has
with a building. The car parking system includes:

© Dubai Design District, All rights reserved. Page 95 of 291

  Entrance to the car park
 Way finding in the car park
 Paying car park ticket
 Exit from the car park
 Security around the car park system

Figure 4-22: Car Parking System

[Link] System Components

[Link].1 Hardware
The car parking system can be integrated onto a converged network. In most circumstances the
equipment in this system operates via a standard power connection (ranges include 110 volt to
240 volt) and is connected to the network via an IP port.
There are a number of functions that can be completed by a car parking system. To support those
multiple functions, various devices are required:

 Ticket dispenser/reader station

 Gate barrier
 Parking guidance
 Parking bay sensor and controller
 Pay machine
 Automatic number plate recognition

© Dubai Design District, All rights reserved. Page 96 of 291

  Handheld monitors
 Bollard system

Further details about the car parking devices are provided in Appendix-E.

[Link].2 Software
The management software component of the car parking system is the link between the
hardware and the user interface display. The following requirements should be taken into
consideration:

 There will be one management software only for the management of the car parking
field devices of all the project zones: one cost only regardless of the size of the project
 The car parking management software shall be used for programming purposes only
and will be transparent to the user
 The user interface of the mediation layer will be used to monitor the car parking
control system
 The car parking control system will not need any dedicated control station or computer
 The car parking server will be web enabled and rack mounted
 The car parking management software will integrate to the mediation Layer

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Specific Technical Requirements

Find below a guideline of the features that the car park equipment shall have in order to converge
to the IP network:

 All field terminals such as lane controllers and pay stations have their local powerful
industrial PC which is able to handle ticket processing and streaming video in parallel
under real-time conditions.
 The operating system is used in all devices for maximum stability
 Lane terminals and pay stations may be equipped with a digital camera to allow for
online video communication with a remote operator

© Dubai Design District, All rights reserved. Page 97 of 291

  All lane terminals and pay station provide a colour screen of VGA resolution for most
comfortable communication with the user
 All devices are linked up by a Fast Ethernet network, supporting copper wire, optical
fibre or radio communication
 Communication both within the system and externally is based exclusively on TCP/IP
communication protocols
 The car park controller provides IP-routing, firewall and http-server functionality to allow
for easy integration with the Internet.
 All screen layouts are based on the Internet standard HTML, allowing for easy
customization of screens without the need for programming changes
 By extensively making use of state-of-the art programming languages like JAVA, multi-
language / multi-font capabilities are designed into the system. This means that
customers using different languages can be easily catered for.
 The user interfaces and endpoint devices must be compliant with various forms of
accessibility options wherever necessary.

An example of car parking single line diagram and logical architecture are presented in Figure
4-23 below:

© Dubai Design District, All rights reserved. Page 98 of 291

 Figure 4-23: Car Parking Single Line Diagram

© Dubai Design District, All rights reserved. Page 99 of 291

 [Link] Smart Dubai KPI’s
Smart Dubai KPIs d3 Interpretation of the KPI
I1.2.3 Proportion of business based on GIS Number of businesses using ICT methods
(location, navigation etc.) that include CAD/GIS and connected to the
d3 CCC
Count by ratio of social, governance and
enterprise businesses that utilize GIS based
services
I6.2.2 Coverage of parking guidance Provision of ICT enabled parking sensors
systems Count by ratio of parking lots under connected to the d3 CCC
automatic guidance
I3.1.8Improvement of traditional industry
with ICT count by ratio of GDP improvement
due to technology upgrade
Table 4-24: Smart Dubai KPI's for Car Parking

4.2.7 Digital Signage

[Link] Description
The digital signage system consists of electronic displays installed in public spaces. It carries
content typically used to entertain, inform or advertise (together known as "infotainment" in
audio visual industry language).
Major benefits of digital signs over traditional static signs are that the content can be
exchanged without effort, animations can be shown and the signs can adapt to the context and
audience. They can even be interactive. Digital signage advertising is a form of out-of-home
advertising in which content and messages are displayed on digital signs, typically with the
goal of delivering targeted messages to specific locations at specific times. Digital signage offers
return on investment compared to traditional printed signs. A digital signage system is divided
into two major parts:

 Hardware - Delivery & Display Devices

 Software - Content Management

The digital signage system is a comprehensive solution enabling organizations to create, manage
and access compelling digital media to easily connect customers, employees, partners or
students- anywhere, anytime from a single platform. It is also a scalable solution for publishing
dynamic content to thousands of users through digital signage displays. Being a network centric
collaboration tool, the digital signage system delivers optimal live and on-demand intelligent
content to enable organizational transformation by putting the human face back into business.

[Link] System Components

In most circumstances the equipment in this system operates via a standard power
connection (ranges include 110 volt to 240 volt) and is connected to an Integrated Operation
Centre (CCC) via IP.
As mentioned in the system overview, to support these applications and functionality, various
components are required. They are discussed in this section.

© Dubai Design District, All rights reserved. Page 100 of 291

 [Link].1 Non-IP Devices
The non-IP devices mainly consist of the LCD (Liquid Crystal Display) and PDP (Plasma Display
Panels), light emitting diode and video wall display and Interactive Kiosks enclosures. They can
be considered as end point devices.
Digital displays can be LCD or plasma display panels, electronic billboards, projection screens
or light emitting diode (LED) panels.
The Interactive Kiosk enclosure can include an LCD screen with a touch overlay panel to provide
interactive touch capabilities a camera and peripherals such as speakers, microphones, card
reader, scanners, etc.
All endpoints shall be controlled remotely allowing individuals or groups to remotely change
and control their content via IP through a digital media player.
All displays and interactive kiosks must be accessible and provide different methods of input and
output to support people with special needs.

[Link].2 IP Devices
Encoders
The encoder is the device that creates the content. The two main types are the portable real-
time and the multi-channel encoders. The first takes live video feed while the latter takes any
audio visual feeds e.g. satellite/cable TV and DVD (Digital Video Disc).

Portable Real-Time
These encoders are normally portable. They provide live and on-demand streaming digital
media, including video and audio, across an IP network-anywhere an event or meeting can
occur. In some regions, this application is also known as video overflow.
A single channel encoder (Refer to Figure below) is an integrated component of the digital
signage system for real-time video streaming to display devices or portal browsers (interactive
kiosks).

Figure 4-24: Single Encoder

The physical design shall be user-friendly for both professionals and novices. There shall be
push- button control access to predefined Windows Media and MPEG-4/H.264 encoder profiles.
An LCD display mounted on the front panel for access to configuration and operation
information shall be a consideration when selecting single-channel encoders.
In a nutshell, the single-channel encoders shall have rugged design and minimal weight to allow
the user to take video production out of the studio.

Multi-Channel Encoders
The multi-channel encoders are integrated components of the digital signage system for real-
time, archived or playback streaming to display devices or interactive kiosks.

© Dubai Design District, All rights reserved. Page 101 of 291

 Figure 4-25: Multi-Channel Encoder
These encoders are multiprocessor, studio-quality audio and video encoding appliances
providing live and on-demand streaming digital media across an IP network.
Multi-channel encoders are designed for sophisticated users who require multiple audio and
video input options, a variety of encoding formats and functions and high-bandwidth encoding.
The type with a colour display and audio output monitors mounted on the front panel provides
visual video and audio encoding monitoring. A user can manage the encoder locally through
the embedded LCD or remotely through management server software. Their multiprocessor
power and variety of input options make these encoders the choice for users, including corporate
offices or datacenters needing sophisticated creation of compelling digital media content.

Digital Signage Manager Hardware

This is the box that connects all digital signage components. The manager cannot work as a
standalone without the applications software. Nevertheless, the manager is the heart of the digital
signage system when the software applications are up and running.

Figure 4-26 Digital Signage Manager Hardware

Digital Media Players

Highly reliable IP-based hardware endpoints that handle digital media content display and
playback including high-definition live broadcasts and on-demand video, flash animations, text
tickers and other Web content across the digital signage system.

Figure 4-27 Digital Media Player

[Link].3 Software
The content displayed on digital signage screens can range from simple text and still images
to full- motion video, with or without audio. Some operators of digital signage networks,
particularly in the retail industry, regard their networks as comparable to television channels,
displaying entertaining and informational content interspersed with advertisements.
Nevertheless, the content delivery software must be user-friendly.
The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network

© Dubai Design District, All rights reserved. Page 102 of 291

  Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

A typical digital signage system network topology for a building can be represented by Figure
4-28 below:

Figure 4-28: Typical Digital Signage Network Topology

[Link] Specific Technical Requirements

Specific technical requirements about the digital media player are listed below:

 Solid-state device, with no moving parts

 Used for the decoding and display of digital media

© Dubai Design District, All rights reserved. Page 103 of 291

  Highly reliable IP-based digital media player that handles display and playback of
compelling, rich digital media-including high-definition live broadcasts or on-demand
video, flash animations, graphics, text tickers and other web content-across a network
of digital signs
 Fully manageable as a standalone device or part of the integrated offering,
 Have a centralized management system component to publish centralized content
to networked digital signs
 Have RS-232 connections for control of virtually any market-leading digital displays
 Built-in GUI for device and content playback management
 Built on an embedded operating system, making it highly reliable and low maintenance
 MPEG 1, 2 and 4 Part 2 in standard definition (SD) and HD, graphics, web content,
Adobe Flash 6 animation and tickers
 High local storage capacity
 IP-enabled delivery of live broadcasting and on-demand video content
 Grouping for targeted messaging
 Immediate and scheduled publishing of content
 Remote management of display (on/off, volume, contrast and brightness)
 Full-screen video or division of the screen
 Customizable on-screen presentations, templates and play lists
 Small form factor
 Low power consumption

Figure 4-29 Cables and Connectors

Signal delivery quality is dependent on cable quality. HDMI connection is preferred to get the best
quality high-definition video. It is important to note that a normal TV screen does not have the
technical specifications to be used as a digital signage display. The digital signage screen needs
to be commercial grade rather than consumer grade.
LCD displays are less susceptible to image burn-in given that signage content is not always video
and is more static in nature (for example, web and flash content). Plasma burn-in can occur more
easily when content is not dynamic, has high contrast colours (e.g. black against white) or has
sharp edges.
The user interfaces and endpoint devices must be compliant with various forms of accessibility
options wherever necessary.
An example of digital signage single line diagram is presented Figure 4-30 below:

© Dubai Design District, All rights reserved. Page 104 of 291

 Figure 4-30: Digital Signage Single Line Diagram

© Dubai Design District, All rights reserved. Page 105 of 291

 [Link] Smart Dubai KPI’s
Smart Dubai KPIs d3 Interpretation of the KPI
I4.1.1 Satisfaction with online commercial and Provision of online commercial and
financial services count by ratio of satisfaction financial services satisfaction
expression in paper/online interview surveys/interviews
I4.1.3 Convenience of government services Provision of government services
satisfaction surveys/interviews
Count by ratio of convenience expression in
paper/online interview
I3.1.8 Improvement of traditional industry with Statistical data on GDP vs. traditional
ICT Count by ratio of GDP improvement due business improvements measures
to technology upgrade
Table 4-25: Smart Dubai KPI's for Digital Signage

4.2.8 Audio/Video
[Link] System Description
The audio visual system consists of the devices used commonly in the meeting rooms,
conference rooms and auditorium in order to facilitate communication and collaboration. The
audio visual system is a complementary system that enhances the user experience based on the
systems mentioned above. An audio visual system is not a single product.

[Link] System Components

The audio visual solution generally consists of the following components:

 Screens
 Projectors
 Controllers
 Speakers
 Management centre

© Dubai Design District, All rights reserved. Page 106 of 291

 Figure 4-31: Audio Video Systems

The audio video system has evolved far beyond the touch panel and control system. It now has
become the definitive source for centrally and globally controlling, managing and presenting
information. In addition to managing the audio video and web information, the audio visual system
can control and automate the lights, drapes, screens, thermostats and AV equipment from a
centralized touch-panel or computer.

[Link] Specific Technical Requirements

Microphones and Speakers
A good audio system will allow every word to be heard, conversations to flow, and the
only adjustment that you'll ever want to make is to the volume. Expertly integrated microphones
and speakers play a key role in maximizing sound quality. The type of both depends on the size
and configuration of the room.
Good microphones are essential to good sounding audio. They can be of the following type:

 Boundary microphones
 Table microphones
 Ceiling microphones

High quality speakers provide clear reproduction of all the audio sources. The most common type
of speakers are:

 Program audio speakers

 Ceiling speakers

Fixed Wall Screen

Designed for permanent installations, these projection screens are designed to integrate
seamlessly into environments from boardrooms to living rooms.

© Dubai Design District, All rights reserved. Page 107 of 291

 Figure 4-32: Fixed Screen

These transparent rear-projection screens depend on a revolutionary coating to work their magic.
It can also be applied to a regular glass window for digital signage applications

Figure 4-33: Transparent Screen

Projector
A projector projects the video image onto a (white) surface of essentially any size. Some of the
functions that the projectors shall have are:

 Wireless transfer of presentation data from multiple PCs to a projector

 DVI connection with HDCP, enabling the addition of digital input sources
 Wired LAN mode
 Wireless LAN mode

Figure 4-34: Projector

Integrated security functions shall be provided by the device to effectively block theft and
manipulation by the use of passwords.

© Dubai Design District, All rights reserved. Page 108 of 291

 Smart White Board
The projection screen is a standard projection screen which can be electrical or non-electrical.
An additional feature for some of the white boards is to be interactive. The white board will have
the following functions:

 Permanent connection of the board to a PC

 Enable screens to be saved as computer files
 Enable the projection of computer screens
 Annotations can be added by the presenter on the white board and saves to the
computer
 The interactive board will be double sided

Figure 4-35: Smart Whiteboard

Touch Panel
The touch panel, used in addition to the presentation system, supports the control capabilities
such as:

 Touch sensing screens for finger-tip operated panel

 Precise drawing and annotation
 Wireless pen for drawing
 Seamless combination of touch panel control and pen-based annotation
 Flat screen, reduced size
 Fast annotation response
 Integration with other systems (HVAC, Lighting...)
 Touch panel to be tilted by an angle between 17 and 73 degrees
 USB ports to be provided on either side of the panel to support the connection
(mouse, keyboard…)
 VGA pass-thru port to be provided to enables the connection of a secondary monitor
display
 Compatible with VISA standards
 The user interfaces and endpoint devices must be compliant with various forms of
accessibility options wherever necessary.

© Dubai Design District, All rights reserved. Page 109 of 291

 Figure 4-36: Touch Panel

Switcher
The switcher distributes video and audio from one or more composite sources to one or more
destinations. Some of the features of the switcher are:

 Built-in video-sensing on each input

 Auto-switching
 Video routing capabilities
 Built-in volume, bass, treble and mute controls a
 6-band graphic/parametric equalizer allow for precise adjustment and complete control
 Settings and presets may be recalled and controlled from a touch panel, keypad or other
user interface

Controller
The audio/video controller can be a separate device or combined with the switcher in one
hardware device. Some of the features of the controller are:

 Ethernet control system

 Easily configured via a software
 Control of the room's AV
 Control of the environmental resources including VCRs, DVD/CD players, projectors,
screens, lighting and more
 IP control solution with full-duplex 10/100 Ethernet
 Built-in Web server and email client
 Support for both static and dynamic IP addressing.
 Built-in SNMP support that allows full control and monitoring from the ICT Help Desk or
NOC
 support SSL (Secure Sockets Layer), the industry standard for protecting sensitive
network communications
 wireless control solution using a wireless touch panel or a third-party universal IR remote
 Single-space EIA rack-mountable

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs

© Dubai Design District, All rights reserved. Page 110 of 291

  Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

An example of digital signage single line diagram is presented in Figure 4-31 below:

© Dubai Design District, All rights reserved. Page 111 of 291

 Figure 4-37: Audio Video Single Line Diagram

© Dubai Design District, All rights reserved. Page 112 of 291

 [Link] Smart Dubai KPI’s
There are no Smart Dubai KPI’s specified for this Audio Video system.

4.2.9 Life Safety

Fire Detection, Alarm Systems and Voice Evacuation are distributed throughout buildings to
monitor for indications of the presence of smoke or fire. When a fire alarm condition is
determined, the fire alarm system communicates that information with sufficient detail to allow
the proper fire response to begin. The fire alarm system may perform other control functions
such as fan shutdown and elevator recall, or those actions may be performed by other systems
that also handle those functions for normal conditions as well as for abnormal conditions.
Typical responses to fire alarm system status changes might include: HVAC fan control
operation, elevator capture, lighting control, and security system awareness. Specific examples
could include turning on lighting where needed, aiming security cameras on specific areas,
providing door release, and implementing detailed fan exhaust and/or pressurization
instructions.
The life safety systems need to be treated separately from the other integrated building systems.
The communication for the life safety systems has to be done through fire rated cable and
hard wired interfaces.
However, in order for the facility management team to have a holistic view of the building systems
in order to assess with precision any situation, the life safety systems need to interface through
a serial connectivity on the IP network of the building for secondary monitoring only.

Pressure

Smoke
3G/LTE or WiFI or
Heat Fiber/Copper d3 Command and Control
connection Center (CCC)
Extinguisher Monitor Telephone line to d3 IP Network
Civil Defence
BMS System Centralized Management

Firealarm System

Typical Sensor or End Point

Figure 4-38: Fire Alarm Logical Architecture

4.2.10 Elevators and Escalators

Elevators and escalators are a part of modern buildings especially in high-rise, enhancing the
standard of building occupants. As with other building systems the escalators and elevators
initially were stand-alone with no provision for remote monitoring and management. But
most of the manufacturers today have software interface options via open protocols such as
BACnet, LON, Modbus and can integrate with the other building systems.
In general, the recommendation would be for a system that supports interfacing and preferably
with the interfacing module communicating on IP network.
The user interfaces and endpoint devices must be compliant with various forms of accessibility
options wherever necessary.

© Dubai Design District, All rights reserved. Page 113 of 291

 Elevator Call System

Elevator Lights

Elevator Fans
3G/LTE or WiFI or d3 Command and Control
Fiber / Copper Center (CCC)
Extinguisher Monitor d3 IP Network

BMS System Centralized Management

Elevator Control System

Typical Sensor or End Point

Figure 4-39: Elevator Logical Architecture

4.2.11 Public Address/Background Music (PA/BGM)

The public address and background music system is separate from the voice evacuation which
belongs to the life safety systems. The PA/BGM system provides music/audio distribution in
the common areas of the building and in the retail common areas. Until a few years back the
systems were analogue and limited monitoring capabilities. To take advantage of the IP
technology and the flexibility it provides, most of the major PA manufactures provide IP
infrastructure that have components connected to IP and communicating with each other on IP.
The added flexibility of the IP infrastructure is the management functions the systems have.
The devices provide remote monitoring to the management station and can be remotely
programmed. The IP interface also extends the remote management capability to other
interfaced systems and permits monitoring by other systems for any failure. Typically the
systems communicate on SNMP trap for information about the failures. IP at the zone/speaker
level allows the granular control of sound to each zone/speaker.
The user interfaces and endpoint devices must be compliant with various forms of accessibility
options wherever necessary.

Standard Loudspeakers

Amplifiers

Medial Players
3G/LTE or WiFI or d3 Command and Control
Fiber / Copper Center (CCC)
IP Phones d3 IP Network

Public Address System Centralized Management

Background Music System

Typical Sensor or End Point

Figure 4-40: Background Music Logical Architecture

© Dubai Design District, All rights reserved. Page 114 of 291

 4.2.12 Solar Panels
[Link] Description
The Solar Panels produces renewable energy, which is clean, secure and limitless. It produces
no emissions and does not affect the environment. To become a producer and owner of clean
electricity, d3 will own and install its own solar panels installed in d3.
Solar panels or photovoltaic panels are devices that convert light from the sun directly into
electrical energy. Solar panels comprises of several solar cells that are interconnected with both
series and shunt (parallel) configuration. The sun can provides enough energy for all human
needs if only it could be well harnessed. Solar power is one of the alternative energy sources that
has seen a lot of development in the past two decades.
The energy produced by the solar panels will be used by d3. Any surplus of production will be fed
into the electricity network and will be credited for off-setting future consumption.

[Link] System Components

Solar cells produce electric power, which is usually measured in terms of peak kilowatt or kWp.
This measure is the amount of power a solar cell produces at full sunlight in summer. This means
that solar energy varies according to the position of the sun. Solar tracking technology is used to
track the sun’s movements and synchronize with the solar panel. This maximizes the daily output
power.
Solar panels are available in various sizes and prices. d3 can buy the panels and install them on
the roofs. In order to be compliant with the local regulations, d3 has to comply with “Shams Dubai”
project from DEWA. The specific regulations that need to be considered are listed below:

 Executive Council Resolution No. (46) of 2014

 DEWA DRRG Standards – Version 1.1 - Edition 2015
 DEWA DRRG Connection Guidelines – Version 1.0 - Edition 2015
 Safety of People - Recommendations for DRRG Solar PV – Version 1.0 - Edition 2015
 Safety of Environment - Recommendations for DRRG Solar PV Systems – Version 1.0 -
Edition 2015
 PV on Buildings and Fire Safety - Recommendations for DRRG Solar PV Systems –
Version 1.0 - Edition 2015
 DEWA DRRG Connection Agreement
 DEWA DRRG Connection Conditions

The array of solar panels are connected together and fed through an inverter, which converts
the direct current (DC) from the solar panels to alternating current (AC). The output is then fed
to DEWA’s grid.

[Link].1 Hardware
The main components of the solar panels system are:

 Panels: PV panels are the single biggest expense of a PV system. Their placement and
mounting affect the system performance more than any other parameter.
 DC-to-AC inverters: Inverters take the low-voltage, high-current signals from the PV
panels and convert them into 120VAC (or 240 VAC), which is directly compatible with
grid power.

© Dubai Design District, All rights reserved. Page 115 of 291

  Utility power meters: special digital smart meters will be used by DEWA when d3
connect to the grid.

[Link].2 Software
The Solar Panels need to have a back end Software application that provided the following
capabilities:
1 Configuration Management
2 Operations Management
3 Fault and Alarm Management
4 Reporting Management

The Software Application shall have client server type architecture and must also support web
based management interface.
The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Smart Dubai KPI’s

Smart Dubai KPIs d3 Interpretation of the KPI
I2.2.1 Level of civilian electricity usage (per Number of ICT energy enabled Sensors
capita) with ICT measures connected to the d3 CCC
Count by ratio of average civilian electricity
consumption saved this year compared with
last year systems and clean energy
systems
I6.1.1 Application level of energy saving Number of ICT energy enabled Sensors
technologies in public buildings connected to the d3 CCC
count by ratio of public buildings that have
energy saving systems, including energy
conservation
Table 4-26: Smart Dubai KPI’s for Solar Panels

© Dubai Design District, All rights reserved. Page 116 of 291

 4.2.13 Smart home
[Link] Description
The Smart Home system includes all aspects of a home automation including security,
environment (lighting and thermostat regulation) and entertainment. The Smart Home connects
multiple sensors, devices and appliances so they can communicate with each other and with the
user. The home will react to the command either by remote control, tablet, smartphone, voice or
a combination thereof.
The Smart home service is planned by d3 for deployment in Phase 3 of the Construction Phase.

[Link] System Components

The Smart Home shall combine the best technologies to create a platform that is both powerful
and flexible to meet a wide range of customer needs and enquiries. The solution shall integrate
all the aspects of the house including security, environment and entertainment.
The Smart Home shall use sensors, appliances and devices that run on open standard protocols
such as:

 TCP/IP
 Wi-Fi
 Zigbee: wireless mesh networking protocol for appliances based on the IEEE 802.15.4
standard
 Infrared signals for automatically controlling home theater equipment.
 RS-232 serial communication

It is recommended to use power over IP whenever possible for the devices, sensors and
controllers.

[Link].1 Hardware
The Smart Home solution consists of the following components:

1. Interfaces (TV, Tablet, Remote, Smart Phone)

2. Mobile Application
3. Controllers
4. Audio/Video devices (switches, amps, speakers and media players)
5. Lighting switches, dimmers
6. Smart Thermostat
7. Door Lock
8. Door Station
9. IP based Video Surveillance Cameras
10. Sensors (leak detectors, window contact, motion sensor, etc.)

The Smart Home shall also support the following devices:

 Smart Meters
 Standard home theatre equipment: televisions, CD/DVD players, VCRs, amplifiers,
cable/satellite set-top boxes, media players
 Professional home theatre equipment: audio-visual matrix switches, DVD changers,
projectors
 Security alarm panels, when they offer a serial "home automation" module or connection

© Dubai Design District, All rights reserved. Page 117 of 291

  Electrical devices that can be switched via relay contact closure, such as motorized
blinds, fireplaces, motorized door locks, sprinkler systems, radiant floors, etc.
 Heating and air conditioning systems (through "smart" thermostat)
 Apple iOS (through a proprietary networked wired/wireless streaming device)
 USB hard drives and flash drives containing media (such as MP3 files)
 Network-attached storage and file shares containing media files
 Immersive LED lighting controller for total lighting environment control and AV
integration
 The user interfaces and endpoint devices must be compliant with various forms of
accessibility options wherever necessary.

[Link].2 Software
The Smart Home Interface shall have the same look and feel from any device used. The PC, TV,
tablet and smart phone shall all present the same interface to make it easier to the user.
The Smart Home shall be capable of personalization and shall include a secure login for the
configuration of settings.
The Smart Home shall give the facility management team in-house control across the entire
community. Web-based Smart Home management software shall be used to seamlessly
integrate existing Property Management systems with trouble-ticketing systems and the Smart
Home solution. This web-based application shall be capable of alerting maintenance when an
issue arises and even notify maintenance staff when new batteries are needed for a remote
control.
The information specific to the user shall not be shared at any time with the FM team and be
securely independent from the rest of the information.
The Smart Home shall be capable of integrating with other smart services being deployed
(available at the present time or deployed in the future) in d3.
The Smart Home platform shall offer open APIs for application development.
The Smart Home platform shall monitor and control any device using software connectors, even
if not from the same brand.

[Link] Smart Dubai KPI’s

Smart Dubai KPIs d3 Interpretation of the KPI
I4.1.12 Satisfaction with housing conditions Provision of housing conditions
satisfaction surveys/interviews
Count by ratio of satisfaction expression about
housing conditions during paper/online
interview
I6.4.6 Electricity supply system management Parametric data provided by DEWA on a
with ICT measures count by ratio of electricity regular basis
supply systems under management with ICT
help
I6.1.1 Application level of energy saving Number of ICT energy enabled Sensors
technologies in public buildings count by ratio of connected to the d3 CCC
public buildings that have energy saving
systems, including energy conservation
systems and clean energy systems

© Dubai Design District, All rights reserved. Page 118 of 291

 I6.1.2 Percentage of public buildings with Number of buildings with integrated
integrated technologies count by ratio of public technologies and BMS at d3
buildings with building management systems,
communication and control
I6.1.3 Proportion of smart home automation Number of ICT enabled Smart Homes
adoption Count by ratio of families that enjoy connected to the d3 CCC
smart home tech
I1.1.4 Percentage of households with Internet Provision of home internet
access count by ratio of internet accessible
families
I4.1.6 Satisfaction with crime prevention and Provision of crime prevention
security control Measured by Security Feeling satisfaction surveys/interviews
in paper/online interview. Add Crime rate and
case solve rate.
Table 4-27: Smart Dubai KPI's for Smart Home

4.2.14 Point of Sale

The Point of Sale is the responsibility of the retailer in d3. It is common practice that large and
well-established retailers will have a preferred vendor for the Point of Sale. Smaller type of
retailers however may have no specific preference.

4.2.15 Potable Water Tank Quality Control

[Link] Description
Each building in d3 has its own water tank. It is important for d3 to monitor closely the quality of
the water in these water tanks before it is distributed to the tenant.

[Link] System Components

The components of the potable water tank quality control consist of sensors that will be mounted
in the tank. The sensors reading will be added to the BMS system for visualization.
The list of parameters to be monitored from the water tank include:

 pH value
 Pollution Level
 Toxic Level
 Tank leakage

© Dubai Design District, All rights reserved. Page 119 of 291

 5 ICT guidelines for Municipal Systems
in d3
d3 aims at integrating and analyzing massive amounts of data to anticipate, mitigate, and even
prevent many problems at the building level. This data will be leveraged, for example, to operate
the building efficiently, identify equipment malfunction and target resources for energy
consumption reduction.
In order to achieve the above, all stakeholders responsible for the building infrastructure and
systems need to follow the technical guidelines provided in this section.
It is also important for the designers to show leadership by providing designs that align with these
following guiding principles:

 The Network as the platform (Section 3.3.1)

 Convergence of the systems (Section 3.3.2)
 Transformation/ Service Delivery (Section 3.3.3)
 Automation of processes and systems (Section 3.2)
 Easy Accessibility (d3 Master Plan Accessibility review report submitted by DCCA with
Place Dynamix on 27th May 2015)

While convergence and automation is the way forward for any Smart City, due to Dubai’s specific
regulations, it may not be possible for d3 to converge all the systems particularly the
Telecommunications network, Security network, DEWA network and Empower network. All these
providers have shown reluctance to share and use one common network to carry their data to
their respective data centres. Keeping these limitations in view it has become mandatory for d3
to have its own communications network within d3 to cater to deliver Smart Services within the
district.
This section provides best practices to build a telecommunications network as well as specific
recommendations for d3 wherever necessary. This section also lists all the connectivity
requirements of the wet systems, dry systems and other citywide systems to easily converge
them on this network and be open for future integration.

5.1 City-Wet Utilities

5.1.1 Potable Water Network
The potable Water Network is linked to the Smart Dubai Initiative: Centralized water and sewage
distribution management system and automated leak detection.

[Link] Description
The Potable Water Network shall consist of a centralized system that manages the distribution of
water to the households and buildings within d3 and identifies operational status, incidents (such
as leakages, etc.) and generates alerts for responsible maintenance teams.

[Link] Functional blocks

The figure below provides a high level view of the Potable Water Network System.

© Dubai Design District, All rights reserved. Page 120 of 291

 Figure 5-1: Potable Water Network Logical Architecture

[Link] Typical list of parameter to be monitored and/or controlled

 Flow
 Pressure Level
 pH value : (To be monitored on the DEWA entry to the District and at each building
entrance)
 Valve Status & Control
 Pollution Level
 Flood Level
 Toxic Level
 Pump Motor Status & Control
 Leakage

[Link] d3 IP Network Connectivity

The Remote Measurement and Control Field Device can be used to read and/or control different
sensors cum devices as listed above. For the communication between the centralized
management system and Remote Measurement and Control Field Device one or more methods
of communication can be used as listed below:

 GSM/ 3G/ LTE

 Wi-Fi
 Wired

These Field devices shall provide for time stamped logging of the parameters and as well the
centralized management server shall be used to log the data, provide appropriate graphical user
interface and also to generate reports. The Field devices must have capability to use standard
protocols like TCP/IP, Bacnet/IP, Modbus and DPN3, or as required by design consultant. The
interfaces connectivity between the Field device and the sensors or control devices can be serial
RS 232 /RS 245 interfaces or Ethernet interfaces (TCP/IP).

© Dubai Design District, All rights reserved. Page 121 of 291

 [Link] Centralized Management
d3 will have a centralized management system that is compatible with DEWA standards for
control systems. This system will enable remote monitoring and management of the potable
water. The Centralized Management System shall provide capability of displaying information on
maps using geo location coordinates, provide reports and have the capability to record data and
display historical data in the shape of customized reports. The application must have capability
to use standard protocols like TCP/IP, Bacnet/IP, Modbus and DPN3.
The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Smart Dubai KPIs

Smart Dubai KPIs d3 Interpretation of the KPI
I2.1.1 Progress degree of ICT usage in the protection of Number of ICT enabled Sensors
main city water resources count by ratio of urban water connected to the d3 CCC added per
resources under protection with ICT measures year
I2.1.2 Effect of flood control monitoring by means of ICT Provision of ICT enabled flood level
measures count by ratio of flood that cause no fatal sensors connected to the d3 CCC.
damage or huge loss due to early warning with ICT

I2.1.3 Proportion of water pollution control by means of Provision of ICT enabled water
ICT measures count by ratio of water pollutant sensors connected to the d3 CCC, at
resources under automatic inspection every water pollutant source
12.1.5 Proportion of toxic substances monitoring by Provide ICT enabled Water Sensors
means of ICT measures count by ratio of highly connected to the d3 CCC, at every
dangerous toxic substance sources under control with source
the help of ICT
I6.2.1 Coverage of installation of road sensing terminals Number of ICT enabled Sensors
count by number of road sensors per kilometre in overall connected to the d3 CCC added per
urban road coverage year
I6.4.1 Drainage system management with ICT Number of ICT enabled Sensors
measures count by number of sensors per kilometre in connected to the d3 CCC added per
overall urban drainage system year

© Dubai Design District, All rights reserved. Page 122 of 291

 I6.4.7 Improvement of underground pipelines and Design the water management system
spatial integrated administration with ICT measures / using ICT methods that include
count by ratio of digital documented and spatial CAD/GIS and connected to the d3
integrated administration of underground pipelines CCC.
among all underground network
Table 5-1: Potable Water KPI Interpretation

5.1.2 Sewage Waste Network

The Sewage Waste Network (SWN) is linked to the Smart Dubai Initiative.

[Link] Description
SWN shall be a used to carry waste water coming out from various buildings within d3 and shall
consist of a centralized system that manages the collection of waste water in accordance with
applicable Dubai Municipality guidelines.

[Link] Functional blocks

The figure below provides a high level view of the SWN System.

Figure 5-2: Sewage Network Logical Architecture

[Link] Typical list of parameter to be monitored and/or controlled

 Flow
 Level Measurement
 pH Value
 Conductivity Measurement
 Sludge Level Measurement
 BCC Chemical Analysis
 Leakage Detection

[Link] d3 IP Network Connectivity

The Remote Measurement and Control Field Device can be used to read and/or control different
sensors cum devices as listed above. For the communication between the centralized

© Dubai Design District, All rights reserved. Page 123 of 291

 management system and Remote Measurement and Control Field Device one or more methods
of communication can be used as listed below:

 GSM/ 3G/ LTE

 Wi-Fi
 Wired

These Field devices shall provide for time stamped logging of the parameters and as well the
centralized management server shall be used to log the data, provide appropriate graphical user
interface and also to generate reports. The Field devices must have the capability to use standard
protocols like TCP/IP, Bacnet/IP, Modbus and DPN3, or as required by design consultant. The
interfaces connectivity between the Field device and the sensors or control devices can be serial
RS 232 /RS 245 interfaces or Ethernet interfaces (TCP/IP).

[Link] Centralized Management

d3 will have a centralized management system that is compatible with Dubai Municipality
standards for control systems. This system will enable remote monitoring and management of
the potable water. The Centralized Management System must provide capability of displaying
information on maps using geo location coordinates, provide reports and have the capability to
record data and display historical data in the shape of customized reports. The application must
have capability to use standard protocols like TCP/IP, Bacnet/IP, Modbus and DPN3.
The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Smart Dubai KPIs

Smart Dubai KPIs d3 Interpretation of the KPI
I2.1.1 Progress degree of ICT usage in the protection of Number of ICT enabled
main city water resources count by ratio of urban water Sensors connected to the d3
resources under protection with ICT measures CCC added per year
I6.3.1 Waster discharge management with ICT measures Number of ICT enabled
Count by number of sensors per kilometre in overall Sensors connected to the d3
waste network CCC added per year

© Dubai Design District, All rights reserved. Page 124 of 291

 I6.3.2 Improvement of waste water recycling with ICT Flow measurement to be
measures Count by ratio of water recycled this year with communicated to the CCC on
the help of ICT surveillance or management a yearly basis.
I6.4.1 Drainage system management with ICT measures Number of ICT enabled
count by number of sensors per kilometre in overall Sensors connected to the d3
urban drainage system CCC added per year
16.4.7 Improvement of underground pipelines and Design the water
spatial integrated administration with ICT measures / management system using
count by ratio of digital documented and spatial ICT methods that include
integrated administration of underground pipelines CAD/GIS and connected to
among all underground network the d3 CCC.
Table 5-2: Sewage Network KPI Interpretation

5.1.3 Storm Drainage Network

The Storm Drainage Network (SDN) is linked to the Smart Dubai Initiative.

[Link] Description
SDN typically is used to collect, retain, treat and transfer storm water runoff in an efficient and
sustainable manner.

[Link] Functional blocks

The figure below provides a high level view of the SDN System.

Figure 5-3: Storm Drainage Network Logical Architecture

[Link] List of Parameter (Input/ Output) to be provided by the field

devices
 Flow
 Level Measurement
 pH Value
 Pollutant Level (such as Oil Level Measurement)
 Flood Level
 Leakage Detection

© Dubai Design District, All rights reserved. Page 125 of 291

 [Link] d3 IP Network Connectivity
The Remote Measurement and Control Field Device can be used to read and/or control different
sensors cum devices as listed above. For the communication between the centralized
management system and Remote Measurement and Control Field Device one or more methods
of communication can be used as listed below:

 GSM/ 3G/ LTE

 Wi-Fi
 Wired

These Field devices shall provide for time stamped logging of the parameters and as well the
centralized management server shall be used to log the data, provide appropriate graphical user
interface and also to generate reports. The Field devices must have capability to use standard
protocols like TCP/IP, Bacnet/IP, Modbus and DPN3, or as required by design consultant. The
interfaces connectivity between the Field device and the sensors or control devices can be serial
RS 232 /RS 245 interfaces or Ethernet interfaces (TCP/IP).

[Link] Centralized Management

d3 shall have a centralized management system that is compatible with Dubai Municipality
standards for control systems. This system will enable remote monitoring and management of
the potable water. The Centralized Management System must provide capability of displaying
information on maps using geo location coordinates, provide reports and have the capability to
record data and display historical data in the shape of customized reports. The application must
have capability to use standard protocols like TCP/IP, Bacnet/IP, Modbus and DPN3.
The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Smart Dubai KPIs

Smart Dubai KPIs d3 Interpretation of the KPI
I2.1.2 Effect of flood control monitoring by Provision of ICT enabled flood level sensors
means of ICT measures count by ratio of connected to the d3 CCC
flood that cause no fatal damage or huge
loss due to early warning with ICT

© Dubai Design District, All rights reserved. Page 126 of 291

 I6.2.1 Coverage of installation of road Number of ICT enabled Sensors connected
sensing terminals count by number of road to the d3 CCC added per year
sensors per kilometre in overall urban road
coverage
I6.3.1 Waster discharge management with Number of ICT enabled Sensors connected
ICT measures Count by number of sensors to the d3 CCC added per year
per kilometre in overall waste network
I6.4.1 Drainage system management with Number of ICT enabled Sensors connected
ICT measures count by number of sensors to the d3 CCC added per year
per kilometre in overall urban drainage
system
I6.4.7 Improvement of underground Design the water management system
pipelines and spatial integrated using ICT methods that include CAD/GIS
administration with ICT measures / count by and connected to the d3 CCC.
ratio of digital documented and spatial
integrated administration of underground
pipelines among all underground network
Table 5-3: Storm Draining KPI Interpretation

5.1.4 Fire Fighting Network

The Fire Fighting Network (FFN) is linked to the Smart Dubai Initiative.

[Link] Description
FFN shall be a centrally monitored system that provide operational status, incident reports (such
as leakages, etc.) and generate alerts that can be viewed in the CCC. The functional design of
the FFN shall be in compliance with the applicable Dubai Civil Defense (DCD) specifications

[Link] Functional blocks

The figure below provides a high level view of the FFN System.

Figure 5-4: Fire Fighting Network Logical Architecture

[Link] Typical list of parameter to be monitored and/or controlled

 Flow
 Pressure Level

© Dubai Design District, All rights reserved. Page 127 of 291

  pH Value
 Tank Level
 Hydrant Clearance (pref. by CCTV Analytics)
 Leakage detection

[Link] d3 IP Network Connectivity

The Remote Measurement and Control Field Device can be used to read and/or control different
sensors cum devices as listed above. For the communication between the centralized
management system and Remote Measurement and Control Field Device one or more methods
of communication can be used as listed below:

 GSM/ 3G/ LTE

 Wi-Fi
 Wired

These Field devices shall provide for time stamped logging of the parameters and as well the
centralized management server shall be used to log the data, provide appropriate graphical user
interface and also to generate reports. The Field devices must have capability to use standard
protocols like TCP/IP, Bacnet/IP, Modbus and DPN3, or as required by design consultant. The
interfaces connectivity between the Field device and the sensors or control devices can be serial
RS 232 /RS 245 interfaces or Ethernet interfaces (TCP/IP).

[Link] Centralized Management

d3 will require a centralized management system that is compatible with Dubai Civil Defence
standards for control systems. This system will enable remote monitoring and management of
the potable water. The Centralized Management System must provide capability of displaying
information on maps using geo location coordinates, provide reports and have the capability to
record data and display historical data in the shape of customized reports. The application must
have capability to use standard protocols like TCP/IP, BACnet/IP, Modbus and DPN3.
The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

© Dubai Design District, All rights reserved. Page 128 of 291

 [Link] Smart Dubai KPIs
Smart Dubai KPIs d3 Interpretation of the KPI
I2.1.1 Progress degree of ICT usage in the Number of ICT enabled Sensors connected
protection of main city water resources to the d3 CCC added per year
count by ratio of urban water resources
under protection with ICT measures
I2.1.2 Effect of flood control monitoring by Provision of ICT enabled flood level sensors
means of ICT measures count by ratio of connected to the d3 CCC.
flood that cause no fatal damage or huge
loss due to early warning with ICT
I6.4.7 Improvement of underground Design the water management system
pipelines and spatial integrated using ICT methods that include CAD/GIS
administration with ICT measures / count by and connected to the d3 CCC.
ratio of digital documented and spatial
integrated administration of underground
pipelines among all underground network
Table 5-4: Fire Fighting KPI Interpretation

5.1.5 Irrigation Water Network

The Irrigation Water Network (IWN) is linked to the Smart Dubai Initiative.

[Link] Description
IWN shall be used to carry treated sewage effluent (TSE), as supplied by Dubai Municipality, for
the purpose of maintenance of landscapes within d3. The current requirement consists of a
centralized system that manages the distribution of water to the households for gardens and
green areas within d3 and identifies operational status, incidents (such as leakages, etc.) and
generates alerts for responsible maintenance teams.

[Link] Functional blocks

The figure below provides a high level view of the IWN System.

Figure 5-5: Irrigation Water Network Logical Architecture

© Dubai Design District, All rights reserved. Page 129 of 291

 [Link] Typical list of parameter to be monitored and/or controlled

 Flow
 Pressure Level
 Tank Level
 Ambient Environment (such as Atmospheric Temperature, Humidity, Rainfall, Wind
Speed, Radiation, Sunshine, etc.)
 Soil Temperature
 Soil Moisture
 Pump Motor Status & Control
 Leakage Detection

[Link] d3 IP Network Connectivity

The Remote Measurement and Control Field Device can be used to read and/or control different
sensors cum devices as listed above. For the communication between the centralized
management system and Remote Measurement and Control Field Device one or more methods
of communication can be used as listed below:

 GSM/ 3G/ LTE

 Wi-Fi
 Wired

These Field devices shall provide for time stamped logging of the parameters and as well the
centralized management server shall be used to log the data, provide appropriate graphical user
interface and also to generate reports. The Field devices must have capability to use standard
protocols like TCP/IP, Bacnet/IP, Modbus and DPN3, or as required by design consultant. The
interfaces connectivity between the Field device and the sensors or control devices can be serial
RS 232 /RS 245 interfaces or Ethernet interfaces (TCP/IP).

[Link] Centralized Management

d3 will have a centralized management system that is compatible with Dubai Municipality
standards for control systems. This system will enable remote monitoring and management of
the potable water. The Centralized Management System must provide capability of displaying
information on maps using geo location coordinates, provide reports and have the capability to
record data and display historical data in the shape of customized reports. The application must
have capability to use standard protocols like TCP/IP, Bacnet/IP, Modbus and DPN3.
The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases

© Dubai Design District, All rights reserved. Page 130 of 291

 o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Smart Dubai KPIs

Smart Dubai KPIs d3 Interpretation of the KPI
I2.1.1 Progress degree of ICT usage in the Number of ICT enabled Sensors connected
protection of main city water resources to the d3 CCC added per year
count by ratio of urban water resources
under protection with ICT measures
I2.1.2 Effect of flood control monitoring by Provision of ICT enabled flood level sensors
means of ICT measures count by ratio of connected to the d3 CCC.
flood that cause no fatal damage or huge
loss due to early warning with ICT
I6.4.7 Improvement of underground Design the water management system
pipelines and spatial integrated using ICT methods that include CAD/GIS
administration with ICT measures / count by and connected to the d3 CCC.
ratio of digital documented and spatial
integrated administration of underground
pipelines among all underground network
Table 5-5: Irrigation Water KPI Interpretation

5.2 City-Dry Utilities

5.2.1 Electrical
The Electrical Distribution Network is linked to the Smart Dubai Initiative.

[Link] Description
The Electrical Distribution Network shall be for the provision of (132/11kV) primary sub-stations
and the creation of an approved 11kV network within d3.

[Link] Typical list of parameter to be monitored and/or controlled

No specific performance parameter is identified for the Electrical Distribution Network

[Link] Smart Dubai KPIs

Smart Dubai KPIs d3 Interpretation of the KPI
Electricity supply system management with ICT measures Parametric data to be provided
count by ratio of electricity supply systems under by DEWA on a monthly basis
management with ICT help (Smart Grid)

Table 5-6: Electrical KPI Interpretation

© Dubai Design District, All rights reserved. Page 131 of 291

 5.2.2 Street Lighting
The Street Lighting is linked to the Smart Dubai Initiative.

[Link] Description
The street lighting within d3 shall leverage eco-friendly network enabled lighting control systems
on multi-use poles. Street lighting will be considered for roadways, junctions, interchanges, bridge
crossings and would also allow for devices like wireless outdoor access points, CCTV cameras
and other sensors for automation.

[Link].1 Typical list of parameter to be monitored and/or controlled

 Ambient LUX levels

 Energy consumption
 Fault Status

[Link].2 Network Connectivity

Figure 5-6: Street Lighting Logical Architecture

The Lighting network shall be connected to the lighting controller that will have the capability to
monitor and control the street lighting. The lighting controllers in different areas should be
connected to each other using IP network using fibre in the outdoor areas and copper in the indoor
areas. The figures below provide an over view of the connectivity and the protocol use for different
types of lights. The lighting system shall support protocols like DALI, PWM, BACNet/IP, TCP /IP.

[Link].3 Centralized Management

d3 will have a centralized management system that is compatible with Dubai Municipality and
RTA designated standards. The Centralized Management system will enable remote monitoring
and management including capability of displaying information on maps using geo location
coordinates, provide reports and have the capability to record data and display historical data in

© Dubai Design District, All rights reserved. Page 132 of 291

 the shape of customized reports. The application must have capability to use standard protocols
like TCP/IP, Bacnet/IP, Modbus and be accessible in the CCC.
The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link].4 Smart Dubai KPIs

Smart Dubai KPIs d3 Interpretation of the KPI
I6.4.2 Street Lighting & signal system management with ICT Number of ICT enabled Sensors
measures count by number of sensors per kilometres in connected to the d3 CCC
overall street lighting system

Table 5-7: Street Lighting KPI Interpretation

5.2.3 Telecom: Outside Plant Passive Infrastructure guidelines

for d3
[Link] Purpose and Usage
The purpose of this section is to provide an overview and recommendations on the initial district
wide fibre optics Outside Plant (OSP) design guidelines for d3.
An outside plant design guideline is necessary to serve as a guide to help effectively plan, design
and build a communications network capable of meeting all of the communications needs for
Smart Cities community wide digital and SMART services. This high level document will cover
the civil aspects of the Outside Plant (OSP) communications system design, which includes the
backbone cabling components required in order to implement an operational communications
network infrastructure for the district.
The outside plant design guidelines present a logical plan to follow as individual systems of the
entire district are placed into operation. Each design and construction phase will then
incrementally build on each preceding phase of the selected communication infrastructure.

© Dubai Design District, All rights reserved. Page 133 of 291

 The section can be used by the following audience:

 ICT/Smart City Team of d3

 d3 Consultants wanting to understand the Converged IP Network Infrastructure Design
particularly the architects, designers, consultants and engineers
 Any individual, organization or department wanting to understand the OSP infrastructure
design requirements and philosophy particularly the architects, designers, consultants
and engineers
 The information within this document can as a whole or partially be used in creating an
RFP or RFI document to help d3 or OSP provider procure the hardware or systems for
the city communications network. This document, however, is not a RFP or RFI
document as such.

[Link] Overview of Outside Plant Design Guideline

The scope of this section is to define districts Outside Plant infrastructure requirements after
clearly understanding the d3 service concepts and service strategies. In addition, it defines the
fibre optic OSP citywide design necessary for d3’s phased development plans. While defining
the guidelines, it has been ensured that the infrastructure will be suitable enough to support all
currently envisioned and flexible enough to handle future services. The design criterion has
considered network availability, physical diversity of fibre, scalability and multi-service support.
This section is a guideline for developing any Smart City Outside Plant infrastructure. However,
due to some operational limitations wherein the some of the Utility Service Providers are not keen
in sharing the same communications infrastructure it is necessary to recommend deviations from
the best practices. Such recommendations are clearly outlined in a subsection
“Recommendations for d3” wherever necessary. Sections were no “Recommendations for d3”
subsection exists as a subsection it must assumed that the guidelines are applicable to d3 without
change.

[Link] OSP Spaces

The OSP Spaces are known as Points of Presence (PoP). A point of Presence (PoP) is a small
environmentally secure control room designed to host communications network equipment and
fibre cabling distribution. Communication network POP is a transit point that connects different
network components and services together using certain communications design principles
around passive and active system connectivity. Communications network POPs could be of
different sizes and may have specific purposes as well. The different types of spaces necessary
for delivering services within a Smart City are as follows:

[Link].1 Primary PoPs

 Primary POPs will be serving one whole neighbourhood;
 Primary POPs will host IP-NGN Core, Distribution and Aggregation data equipment or
active equipment;
 They can also host optional IP Access active equipment on a case-by-case basis to
support localized services like Traffic Management, Digital Signage, Video Surveillance,
etc.;
 They will also host fibre optics OSP backbone and distribution links, and fibre ODFs as
well as cable patching gear;
 Recommended floor size for Primary PoP is around 12 x 10 meters (120 sq. meters) and
should be erected on land controlled by passive service provider in the city like public or
community land;

© Dubai Design District, All rights reserved. Page 134 of 291

  Primary PoP can be owned and operated by Passive layer Service provider in the city.
 The Primary PoP shall also have well designed environmental conditions including
cooling, humidity, air flow, power distribution, UPS, cable containment systems and
Inside Plant (ISP) cabling;
 The Primary PoPs shall be co-located with data centres as much as possible if the
neighbourhood is going to have a DC;
 Primary PoPs will become the anchor points to complete the active and passive
communications network design; and
 Primary PoPs can also host equipment from other telecom service providers of the
region if the Primary PoP has been designed to have “Traffic Peering Block”.

Recommendation for d3
For d3 the Primary PoP will contain Backbone fibre for the entire district, Distribution fibre for the
surrounding neighbourhoods, and Access fibre for the surrounding neighbourhoods. It may also
contain active equipment like the Smart City Core Switches and some storage. The size of the
Primary PoP for d3 shall be 6 x 4m (24 sq. meters). It is recommended to have a dedicated plot
for this purpose. Alternative it can also be co-located within a d3 owned building. For providing
Smart Services within d3 at least one such room will be required. The room must be located
centrally so as to ensure cost effective use of fibre infrastructure. The Primary PoP and the Data
Centre can be co-located within the same building.

[Link].2 Secondary PoPs

 Secondary PoPs will be serving multiple adjacent blocks and facilities within a
neighbourhood;
 Secondary PoPs will always host IP NGN aggregation data or active equipment;
 They can also host optional IP access active equipment on case-by-case basis to
support localized services like Traffic Management, Digital Signage, Video Surveillance,
etc.;
 They will also host fibre optics OSP Distribution and Access links, and fibre ODFs as
well as cable patching gear;
 Recommended floor size for Secondary PoP is around 6 x 6 meters (36 sq. meters) and
should be erected on land controlled by passive service provider in the city; if it is not
possible to provide dedicated plot for Secondary PoP then ground floor of any
residential/commercial building can be considered.
 Secondary PoP can be owned and operated by Passive layer Service provider in the
city.
 The Secondary PoP shall also have well designed environmental conditions including
cooling, humidity, air flow, power distribution, UPS, raised floor, cable containment
systems and Inside Plant (ISP) cabling; and
 Secondary PoPs will also become the anchor points to complete the active and passive
communications network design.

Recommendation for d3
For d3 the Secondary PoP will contain Distribution and Access fibre for the surrounding
neighbourhoods. It may also contain active equipment like the Smart City Distribution Switches
and some storage. The size of the Secondary PoP for d3 shall be 5 x 3m. (15 sq. meters). It is
recommended to have a dedicated plot for this purpose. Alternative it can also be co-located
within a d3 owned building. The Secondary PoP can act as the distribution for up to 5 buildings
provided the buildings are below G+10 floors

© Dubai Design District, All rights reserved. Page 135 of 291

 [Link].3 Tertiary PoPs (MCR/MER)

 Tertiary PoPs are sometimes referred to as Main Computer Room or Main Equipment
Room.
 Tertiary PoPs will be serving either a single building or a couple of adjacent buildings in
a block;
 Tertiary PoPs will mainly host IP NGN Access or data equipment;
 They will also host fibre optics OSP Access links and ODFs as well as cable patching
gear;
 The Tertiary PoP shall also have well designed environmental conditions including
cooling, humidity, air flow, power distribution, UPS, raised floor, cable containment
systems and Inside Plant (ISP) cabling;
 The Tertiary PoP can be located in a building owned by the building owner shall develop
the environmental conditions of the Tertiary PoPs based on the specifications provided
by ECA; and
 Tertiary PoPs can be referenced with multiple names and can have different sizes based
on the type of building as per Table 5-8.

Tertiary POP Room Type Minimum Floor Area

MCR/MER (Commercial) 12 - 36 sq. m
(4 X 3m) for building G+10 and below
(6 X 4m) for buildings up to G+20
(6 X 6m) for buildings G+21 and above
MCR/MER (Residential) 12 - 36 sq. m
(4 X 3m) for building G+10 and below
(6 X 4m) for buildings up to G+20
(6 X 6m) for buildings G+21 and above
MCR/MER (Hospitality) 36 – 54 sq. m (6 X 6m) – (9 X 6m)
MCR/MER (Retail) 24 sq. m (6 X 4m)
Table 5-8: Proposed Sizes of Tertiary POPs

Recommendation for d3
For d3 the Tertiary PoP will contain Distribution and Access fibre for the surrounding
neighbourhoods. It may also contain active equipment like the Smart City Distribution Switches
and will contain the fibre cross connect in case the room caters as the distribution point for up to
five buildings. Buildings that don’t have any distribution equipment planned in the Tertiary PoP
will only have racks that aggregate the fibre from the building Floor Telecom Rooms and the
neighbouring four buildings. This room however will contain other active equipment necessary for
building system automation, Security system and any other equipment specific to Smart Services
within the building. The size of the Tertiary PoP for d3 shall be 4 x 3m (12 sq. meters). It is
recommended to be in the ground floor of each building. Please note that this room shall not
house any equipment or fibre pertaining to the regulated services provider.

© Dubai Design District, All rights reserved. Page 136 of 291

 [Link] Definition of Data Centre
The term Data Centre has been used in multiple contexts in this document. From a physical
perspective, Data Centre is going to be office grade multi storey building whose lower level floors
will be used to house Data Centre active equipment like application servers, Ethernet switches,
IP communications network, for Smart City Operation, and higher level floors will be standard
office space used for the Smart City Command and Control Centre (CCC).
For the proper OSP design of city communications network, the physical aspect of the DC is more
important and shall cater for the following:

 Data centre will be serving the communications and services needs of the whole city;
 DC could also have a collocated Primary PoP hosting communications network active
and passive equipment;
 It is highly recommended to have a standalone building fully owned, controlled and
monitored;
 It shall have separate floors or rooms for different job functions of CCC like Network
Operations Centre (NOC), Data Centre Operations Centre (DCOC), Network Security
Operations Centre (SOC) and Security and Facility Operating Centre (SFOC) and Smart
City CCC;
 For City Wide Operations space needs to be allocated based on the size and the
number of Smart Services to be provided within the city. A minimum Tier 3 Data Centre
is recommended for running Smart City Services.

Recommendation for d3
Based on the proposed Smart Services for d3 for the next seven to ten years it is assumed to
occupy at least 20 Racks within the Data Centre Computer Room. To build a Tier 3 Data Centre
it will require at least a 100 Sq. m. space that would include the computer room and the ancillary
spaces for the Data Centre. The total power required for operating such a Data Centre is
approximately 240 kW.
Alternatively d3 can lease space from any Commercial Data Centre to provide Smart Services
within the district. In this case the number of racks can be added on demand basis.

[Link] Outside Plant Cable Containments

The exterior communications cabling pathways is required to provide a city wide distribution
system (manholes and conduit layout) for all intelligent system cabling that will be served in the
city. Each commercial/ Industrial/ mixed use plot shall be serviced by at least two manholes but
with a consideration to minimize the manholes as much as possible. The pathways for the city
distribution system may include all or some of the following types of manholes:

 Maintenance holes
 Hand holes
 Conduits
 Inner-ducts
 Duct banks

The Figure 5-7 and Figure 5-8 below are examples of a duct bank and a manhole:

© Dubai Design District, All rights reserved. Page 137 of 291

 Figure 5-7: A sample view of a 12 Way Duct Bank

Figure 5-8: Elevation view of a typical manhole

The manholes proposed for Smart City Services shall have multiple uses but are mainly used for
underground or direct-buried plant splicing operations. Manholes are intended to provide
accessible space in underground systems for:

 Placing and joining cables

 Pulling cables
 Splicing
 Maintenance and operation equipment

Manholes must be equipped with:

 A sump
 Corrosion-resistant pulling irons
 Spare Cable racks (grounded per applicable electrical code or practice)
 Ladders (grounded per applicable electrical code or practice)

© Dubai Design District, All rights reserved. Page 138 of 291

 Manholes should be constructed in such a way that they:

 Are capable of supporting the heaviest anticipated street traffic weight

 Are reasonably waterproof
 Provide sufficient racking space for the ultimate number of cables and other equipment
that requires permanent anchorage

Recommendations for d3
The d3 has different types of roads within the district. The table below provides a view of the
different road types and the recommended duct banks for each road type.
S. No Different types of Roads Recommended Service Manhole types
Specified by Parsons corridor for Smart
Services
1 61m to 43m Road 75 cm - JRC 4 or
4 Way D54 – 100 mm duct JRC 12(If Service
Corridor can be
more than 75 cm)
2 36m to 25m Road 75 cm JRC 4 or
2 Way D54 – 100 mm duct JRC 12(If Service
Corridor can be
more than 75 cm)
3 16m to 8m Road 50 cm JRC 4. Only if
2 Way D56 – 50 mm duct required.
Table 5-9: Service Corridor Recommendations for Smart Services
For specifications of duct banks and the manholes refer “Building Infrastructure Guidelines v.5”
document from d3 approved Telecom Service Provider (du).

[Link] District Fibre Network Design Considerations

When OSP fibre cable is to be placed, the first step is an evaluation of the possible routes
interconnecting the plots within the city. Suitable routes, communication fibre cabling spaces,
duct sizing, communication media (fibre) types and counts are critical to maintaining scalability,
flexibility and fault tolerance of the OSP cabling system. Other requirements that must be
considered when designing a metro OSP system are topography, climate, economics, local code,
network requirements, present / future equipment and customer requirements.
At designing stage limited plot details are generally available such as location of entrance facility
in Commercial/residential/industrial plots, roads layout inside larger plots, division of such large
plots etc. Enough flexibility should be provided in the design to make provisions for the future.
OSP designs also depend on standardization of design methodologies and components. The
cost of building and maintaining an OSP infrastructure can increase if the design isn’t based upon
standards and include standardization as a design driver. Standards-driven design and
installation is mission critical with increasingly complex and robust projects like d3. The district’s
OSP infrastructure should be designed to provide the following benefits:

 Facilitate a consistently installed system

 Conform to requirements as defined by Smart Dubai and or standards bodies like BICSI
and local regulated services providers like du and Etisalat.
 Provide flexibility and scalability for future expansion and technologies
 Provide uniform project documents that are consistent from plot to plot.

© Dubai Design District, All rights reserved. Page 139 of 291

 [Link].1 Smart City OSP Design Process
The design of OSP infrastructure contains a variety of challenges that are unique to this design
discipline. When properly designed or sized, the difficulties are minimal when compared to the
time, expense and level of disruption that occurs when an OSP infrastructure is not designed
properly. For this reason, extra care and attention is required to every aspect of the OSP spaces,
pathways and cabling systems. The design of the city wide OSP infrastructure documented in
the report included the following:

 Understanding network equipment requirements

 Calculation of the backbone sizing
 Topology:
 Physical
 Logical
 Redundancy and diversity in fibre rings for MDU areas only
 Determine Entrance Facility (EF) requirements:
 Internal duct , location(s), count and size
 External duct requirements within plot lines.
 Distribution method (Primary and Secondary Routed):
 Duct
 Tunnels
 Overhead and Other
 Selection of proper media
 Environmental considerations
 Roadway crossing considerations
 Building entrance protection
 Grounding and bonding

[Link].2 Fibre Design Architecture

These design metrics are interactive and a single design choice can impact the cost and efficiency
of an OSP system for its entire lifecycle. For example, the choice of direct-buried cable would
require overbuilding of the OSP plant and often falls short of growth requirements within just 5
years of installation. The use of duct banks with sufficient spare ducts and space within the ducts
provide a relatively inexpensive method of addressing subscriber growth, additional service
providers and emerging technologies that can also increase the life expectancy of OSP system
for 25 to 30 years. Blown fibre technology is best suited for the city that develops in multiple
phases. That is fibre core would be required in the later stages as the city develops.

[Link].3 Fibre Count Recommendations for d3

The OSP design recommends a point-to-point or PON “Fibre to the any” (FTTx) network to
provision each plot or single dwelling unit with their own individual fibre. FTTx is a generic term
for any network architecture that uses optical fibre to replace all or part of the typical copper local
loops for communication network, which includes a variety of designs including

 Fibre to the Node/Neighbourhood (FTTN)

 Fibre to the Cabinet (FTTCab) or Fibre to the Curb (FTTC)
 Fibre to the Building (FTTB)
 Fibre to the Home (FTTH) or Fibre to the Premises (FTTP)

© Dubai Design District, All rights reserved. Page 140 of 291

 The proposed FTTX design offers complete flexibility to support open system physical
architectures, which can easily accept passive or active upgrades. The type of upgrade required
will depend on Day-1 and future applications to be utilized. The OSP design proposed for Smart
City will be scalable and flexible to support new technologies as the city evolves to make use of
these emerging applications. Data connections can be directly supported using the appropriate
optical interfaces using a variety of physical and logical paths.
The scalability of the last mile fibre runs and active access layer depends on two things:

 First, a capability to connect as many subscriber edge devices as possible gradually as

the city grows
 Second, a long term presence of physical fibre between the different type of plots and
PoPs so that CAPEX and OPEX can be avoided related to lying of additional fibre in the
ground in future which could be very costly and may require civil works.

Table 5-10 below shows the recommend fibre core counts in the OSP design between different
type of plots and POPs.
Land Use Type Fibre Core Count
Residential High Density 8
Residential-Medium Density 8
Low Density Residential (splicing) 8
Single Dwelling Unit 2
Mosques 4
Community Facilities (Services and 8
Community Centre)
Retail Mall-Souk 8
Mixed use 8
Commercial High Density 8
Commercial Low Density 8
Schools 8
Knowledge Campus 12
Hospital 12
Hotel 8
Theme Park 8
Smart Pole 4
Road Crossing and Traffic Lights 4
Table 5-10: Last Mile Fibre Core Recommendation

[Link].4 Fibre Optic Specifications

The optical fibre proposed for Smart cities is a Low-Water-Peak (LWP) single-mode optical fibre
with full-spectrum availability for optical transmission systems operating over the entire
wavelength range from 1260 nm to 1625 nm. The optical fibre and cable shall be fully compliant
with the June 2005 issue of international standard ICTU-T G.652. Characteristics of a single-

© Dubai Design District, All rights reserved. Page 141 of 291

 mode optical fibre cable exceeds the stringent requirements of ICTU-T G.652.D for low-water-
peak and Polarization Mode Dispersion (PMD) specifications.
Low-Water-Peak fibre cable is recommended for SMART city distribution and multi-application
access networks due to its tight performance specifications regarding low optical loss across the
entire wavelength range from 1260 to 1625 nm, tightest tolerance on geometry, low splice loss,
and low PMD.
Single-mode fibre has long been known for its high bandwidth but traditionally only at a few
specific wavelengths. Today’s applications, such as 10 gigabit Ethernet and fibre to-the-home,
are pushing the limits of legacy fibre. The upcoming 40 and 100 gigabit Ethernet standard will
further tighten the operating specifications. Specialized fibres that are optimized for long haul
systems are available, but these are more costly, more difficult to engineer the network and are
not suitable for enterprise applications. Low-water peak fibre is a single-mode fibre product that
is versatile, capable of handling the network traffic of today and tomorrow and backwards
compatible with existing infrastructure, all at an economical price.

Figure 5-9: Graph of Signal Loss against Wavelength for Multiple Fibre Types

Legacy single-mode fibre shows elevated attenuation in the E-band operating window (1360 –
1460 nm) due to what is called the “water peak”. This elevated attenuation peak occurs at 1385
nm and is caused by hydroxyl ions – essentially moisture – in the glass that absorbs and
attenuates optical signals operating at, and near, 1385 nm. The term “Low Water Peak” (LWP)
describes this type of fibre and is standardized in ICTU-T G.652 C and D and IEC 60793-2-50
Class B1.3.
Attenuation due to this water peak in legacy single-mode fibre can reach upwards of 1 dB/km or
more (2.5 to 3 times the attenuation seen at 1310 nm). This renders the fibre practically
inoperable in the E-band region. The high water peak attenuation can spill over into adjacent
operating windows, including the 1490 nm S band (used in FTTH systems) and the 1310 nm O-
band, which is the common wavelength used in most single-mode systems for the enterprise. In
fact, the centre wavelength tolerance allowed by IEEE 802.3 Ethernet standards is 1355 nm with
a spectral width tolerance of up to 4 nm, which is very close to the 1383 nm water peak.
LWP fibre is created by a process that eliminates all the moisture in the glass during the fibre
manufacturing process. The process not only eliminates any added attenuation at the water peak

© Dubai Design District, All rights reserved. Page 142 of 291

 and E-band region, but it also lowers overall attenuation across the whole spectrum of operating
wavelengths from 1260 to 1625 nm. Eliminating attenuation due to the water peak opens up
additional wavelengths for future bandwidth upgrades, or for secure, dedicated, revenue-
enhancing services.

[Link].5 Specifications of Loose Tube Fibre

ICTU-T G.652.D allows for the following cabled fibre attenuations:

 0.4 dB/km @ 1310 nm;

 0.4 dB/km @ 1383 nm; and
 0.3 dB/km @ 1550 nm.

Use of LWP cabled fibre produces the following superior attenuation results:

 0.34 dB/km @ 1310 nm;

 0.31 dB/km @ 1385 nm; and
 0.22 dB/km @ 1550 nm.

TU-T G.652.D allows for a cabled fibre PMD of 0.22 ps/sqrt(km) while LWP cabled fibre has a
much lower PMD spec of less than or equal to 0.06 ps/sqrt(km). Low PMD allows longer system
lengths and/or higher data rates. Even systems running at 10 Gbps can be impacted by high
PMD values.

[Link].6 Lower Insertion Loss

LWP fibre can provide for lower connection and splice loss to further minimize channel insertion
loss. Benchmark lab-based splicing studies show that LWP fibre cables average about 0.02 dB
splice loss. Actual field splicing losses are usually higher, and are cumulative for multiple splices
in a run.
Lower splice and connection loss in LWP fibre cable is a result of the superior glass geometry
characteristics, namely Core-to-Clad Concentricity Error and Mode Field Diameter (MFD)
consistency. This allows for better alignment of the cores when splicing and connecting fibres
and tighter geometry leads to lower connection and splice loss. Additional benefits of tight
geometry include improved coupling/ centering with the active equipment and more uniform
coating for superior glass protection. The tighter tolerances on these values in LWP fibre cable
results in more consistent performance.

[Link].7 Conclusions LWP Fibre

Installation of optical fibre cable is a significant investment for smart cities. It is expected to
provide reliable service for 25 or more years, and be capable of handling ever-increasing
bandwidth demands. Low Water Peak (ZWP) fibre cable key advantages include:

 Loose tube cables with LWP single-mode optical fibre have a 0.06 dB/km attenuation at
1385 nm;
 Almost 2 km greater reach for 10 gigabit Ethernet at 1310 nm;
 0.6 dB more headroom over 10 km @ 1310 nm; and

© Dubai Design District, All rights reserved. Page 143 of 291

 [Link] High-Capacity/Density Fibre-Optic Panel and Modular Shelves
The high capacity shelves shall be designed to accommodate multiple modules for different
configurations as well as being used for traditional connectivity. These shelves shall be capable
of supporting Next Generation high capacity, high density fibre cabling solutions. All patch panels
offered shall be capable of supporting high and medium capacity splicing as well as Multi-Fibre
Push On (MPO) Connectors for next generation fibre optic applications. Empty space shall be
provisioned in each OSP fibre termination rack for future growth within or external to the city. This
is critical to the cities design strategy. The fibre patch panels shall be suitable for cross connect
installations for connection to other parts of the city. They shall also be suitable for inter-connect
applications for connection directly to equipment.
The cable plant should be interconnected to the applications equipment through the use of patch
cords to minimize accidental damage to the backbone cable. All fibre patch panels shall come
complete with:

 Universal shelf mounting brackets for 19", 23" or European Telecommunications

Standards Institute (ETSI) frame mounting;
 Occupy 4U rack mountable space;
 Cable entry protectors for incoming building fibre or OSP fibre;
 Fibre jumper bend limiters;
 Blank labels for identifying fibre splices and terminations;
 Rear splicing/termination panel that folds out for easy access;
 Support Mid-Span Splicing;
 Hinged rear splice management panel locks in open position for ease of installation;
 No-tools insertion/removal of connector panels or modules;
 Allow for vertical express fibre routing – even when legacy shelves are installed
immediately above;
 Support up to 288 LC/APC connectors and 192 splices;
 Internal components slide forward for front access to splicing area;
 Tool-less front and rear door fasteners; and
 Lift-off front door for unencumbered access during installation

© Dubai Design District, All rights reserved. Page 144 of 291

 Figure 5-10: High Density Fibre Splice Patch Panel

[Link] Splice Wallet

The Splice Wallet provides easy access and administration of six individual splice trays within the
High Density Fibre Splice Patch Panel. Each tray can accommodate 16 splices and a total of 96
splices per wallet. The purpose of the Wallet is to keep the splices protected and in a manageable
format (i.e. in their bundles and sorted by colour code). The concept of splice wallet is shown in
Figure 5-11 and the location of splice wallet in the high density fibre splice panel is visible in
Figure 5-10 below:

Figure 5-11: Spice Wallet

Fibre optic cables are terminated using an industry standard colour code. For cables that consist
of more than 12 strands, the colour code repeats itself. Each group of 12 strands is identified
with some other means such as:

© Dubai Design District, All rights reserved. Page 145 of 291

  Multiple tubes each with 12 or less strands either numbered or coloured following the
same colour code, e.g., 1st tube is blue, 2nd is orange, etc.
 24 strand groups with the colour code repeating with some variation, e.g., the 1st group
of 12 strands are solid colours and the 2nd group is solid colours with a stripe or some
other identifying mark.

The colour sequence is illustrated in Table 5-11 below:

Fibre/Tube No. u
1 Blue
2 Orange
3 Green
4 Brown
5 Grey
6 White
7 Red
8 Black
9 Yellow
10 Purple
11 Rose
12 Aqua
Table 5-11: Typical Fibre Colour Code for Splicing

[Link] Splicing Hardware

Pigtail splicing shall be used to terminate the OSP cable plant to the patching areas. Single pigtail
splicing takes a pigtail, which is a length of fibre cable terminated with an optical connector, and
splices it onto the OSP or building cable. All splices shall be fusion splices and each splice shall
be protected with a heat shrink retention sleeve and housed in a splice wallet as detailed above.
Terminating hardware must be modular and flexible to meet future requirements for additional
cable or rearrangement.

[Link] Low Profile, High Density Fibre Patch Panels

The low profile high density shelves shall be designed to be adaptable to accommodate multiple
snap-in panels or modules for different configurations as well as being used for traditional
connectivity. These shelves should be available in 1U and 2U configurations to support 24 and
48 port availability. These shelves can be used for a combination of splicing and termination of
building or OSP cables. The low profile high density fibre patch panels shall contain:

 Universal shelf mounting brackets for 19", 23" or European Telecommunications

Standards Institute (ETSI) frame mounting;
 1U-2U rack mountable Space;
 Cable entry protectors for incoming building fibre or OSP fibre;
 Top Cover Panel;

© Dubai Design District, All rights reserved. Page 146 of 291

  Front Cable management trough;
 Blank labels for identifying fibre splices and terminations;
 Supports Mid-Span Splicing;
 Support up to 24/48/72 LC APC in 1U and 96 LC APC in 2U and 48/96 connectors and
48/96 splices;
 Tool-less front and rear door fasteners; and
 Lift-off front door for unencumbered access during installation

Figure 5-12: Low Profile, High Density Fibre Patch Panel

[Link] LC/APC Connector

In today’s high performance networks, return loss is quickly becoming critical. Traditionally,
Angled Polish Connectors (APC) have been required for CATV and analogue video applications
to minimize optical reflections at connector interfaces. However, applications using Raman pump
amplification now also require superior return loss performance. Unfortunately, while an angled
polish on a connector improves return loss, it usually results in slightly higher insertion loss when
compared to connectors with a standard polish. While that may have been an acceptable trade-
off in the past, today’s networks require both superior return and insertion loss performance.
SC and FC APC connectors have been popular choices for years. However, in addition to optimal
performance, high density is quickly becoming an important connector requirement. At half the
size of an SC and FC connector, the LC/APC connector is an excellent connector for applications
where density is critical. The LC/APC utilizes the same footprint and rugged design of a regular
LC connector, but contains an angled polish on a ceramic ferrule to give the anti-reflective
attributes.
The LC/APC Connector is a small form factor connector that is half the size of ST or SC
connectors yet has superior optical performance and reduced installation time. It uses the familiar
insertion release mechanism similar to an RJ-45 plug and has a pull-proof design. The LC/APC
Connector allows engineers to design optical fibre infrastructures suited to the low loss needs of
the High-Speed Data Networks. The LC/APC connector family offers a complete connection
solution with a product range designed for fusion splicing onto 250 and 900 micron fibre. It is
available in simplex and duplex configurations for CATV, LAN, MAN and WAN applications.

© Dubai Design District, All rights reserved. Page 147 of 291

 Figure 5-13: Example of a LC/APC Connector

The LC/APC average insertion loss is 0.06 dB, with a standard deviation of 0.04 dB. This far
surpasses the typical insertion loss of an SC-APC connector of 0.25 - 0.30 dB.

Figure 5-14: LC/APC Connector Performance Chart

[Link] Fibre Splicing Implementation Recommendations

A fusion splice is a way of joining two fibre cores by melting the ends together using an electric
arc. A splicing machine is used to provide the high degree of accuracy that is required. The
fusion splicer lines up the two fibre cores and then executes the accurate amount of heat to melt
the ends before pressing them together. Fibre alignment, pre-clean, arc magnitude and duration,
and splice loss estimation are all components of a successful splice process.
Other splicing technologies are available but shall not be used in the Smart cities. For example,
splicing can be carried out using a mechanical splice which holds the fibre ends together in a bed
of index matching gel, but the fibres are not permanently joined.

© Dubai Design District, All rights reserved. Page 148 of 291

 Fusion splicing shall be the only approved splicing method throughout the complete Smart cities
at splice closures, POP’s and in the data centres.

5.2.4 Telecom: ISP guidelines for DC and PoPs in d3

[Link] Aims and Objectives
The intent of this section of the document is to propose a Structured Cabling System (SCS) for
all installations as per proposed project documents, including drawings and specifications. The
purpose of the SCS is to provide a flexible solution for the provision of services over the structured
cabling within the data centre and Primary/Secondary Points of Presence (POP) locations. This
guideline explains in detail all of ECA perceived requirements for new installations here after.
The Smart cities SCS will be based upon the following design criteria:

 Useful life in excess of 20 years

 Future-proofed by full Application Assurance Warranty
 Internationally recognized commercial building cabling standards:
o TIA/EIA-568-B
o ISO 11802-2
o EN 50173 2nd Edition.
 TIA-942
 TIA-862
 802.3af Power-over-Ethernet Compliance
 20 year manufacturer’s product warranty
 Full application assurance warranty.

[Link] Design Overview Acceptance Criteria

This section will require coordination with Smart cities ICT consultant and design professional
that is thoroughly familiar with the construction of the building, such as the MEP consultant or
designer. Scaled architects and MEP drawings detailing floor plans and coverage areas must be
supplied for full evaluation and final approval, including compliance with standards and installation
guidelines.
The following items of information internal to a building are required to be taken into consideration:

 All internal electric power cable routes

 All internal communication cable routes
 The design, size and shape of all equipment rooms to be coordinated with the relevant
consultant and architect
 The location and size of all risers and closet systems should be central to the building
and core areas
 The location, size and shape of all satellite closets and wall cabinets
 Any sources of Electromagnetic interference (EMI)
 All likely sources of water flooding or seepage under floor or adjacent to equipment
rooms
 All service elevators and their maximum load capacities if adjacent to risers
 Building entry facilities primary and secondary and duct size details
 Raised floors and false ceilings
 Highlight any potentially hazardous areas

The following parameters should also be considered:

© Dubai Design District, All rights reserved. Page 149 of 291

  The dimensions of all buildings and floor area coverage
 All proposed external communication duct routes or existing
 Coordination of all other planned service routes where applicable
 Interconnecting manholes, tunnels or conduits
 The telecom service providers entrance point
 Smart cities metro network entrance points
 Special landscape features etc.
 Depth of site water table
 Physical or legal restrictions

[Link] Cable Containment, Routing and Installation

During the design stages, segregation of power and SCS services will and must meet the
requirements of power separation guidelines by the IEEE Regulations based on a suitable design
of a cable containment system by others. Unshielded data cables should not be installed near
sources of electromagnetism. There are standards that specify these distances for structured
data cabling systems and as per EIA/TIA-569-B, the cabling pathways standard, specify the
following Table 5-12.

Typical Building Environment

(Minimum Separation Distance from Power Source at 415V or less @ 100A
Maximum)
Condition ≤100A-Separation
Unshielded power lines or electrical 600 mm
equipment in proximity to open or non-metal
pathways.
Unshielded power lines or electrical 300 mm
equipment in proximity to grounded metal
conduit pathway.
Power lines enclosed in a grounded metal 300 mm
conduit (or equivalent shielding (in proximity
to grounded metal conduit pathway).
Transformers and Electric Motors. 1000 mm
For all fluorescent light fixtures and associated 50 mm
power cables (in the vicinity of the light
fixtures),
Multi-channel outlet boxes or compartments 6 mm
where individual power conductors and
Category 5e or higher cabling are introduced
to serve a workstation.
If loose, open (spaced) power conductors are 50 mm
used and not bunched or maintained close
together.
Table 5-12: Power Separation Distances

Also as shown in Figure 5-15 and Figure 5-16, the following requirements shall also be met:

© Dubai Design District, All rights reserved. Page 150 of 291

  The building itself shall be suitably protected from direct lightning strikes according to the
applicable local or national codes.
 Power and SCS cables shall cross over at right angles. However, a bridge may be
required to meet national/local safety codes.
 Separate pathways will be required for all SCS cables. Electrical or other trades shall
not utilize the SCS pathways for routing.
 Communication spaces will be dedicated spaces used solely for housing and servicing
the structured cabling system and associated hardware.

Figure 5-15: Power Separation Guidelines - 1

© Dubai Design District, All rights reserved. Page 151 of 291

 Figure 5-16: Power Separation Guidelines - 2

© Dubai Design District, All rights reserved. Page 152 of 291

 [Link] Horizontal Office Areas
The horizontal communications cabling is to be provided to single, dual, and quad outlets
throughout the campus buildings. As the LSZH UTP Cat6 or CAT6a cables are star wired from
the MDF/IDF locations, a maximum of 90m distance is allowed to each outlet point. This is in
accordance with the relevant TIA/EIA 568B, EN50173 2nd Edition, and ISO11801-2 Generic
Cabling Standards and is required for a Cat6/Cat6a Class Ea or Class E link.
Any horizontal sub-system shall follow the main routes using cable tray and feeding off those in
suitably sized conduits to the outlet positions. It is mandatory that the containment system be
designed taking into account the 90 meter maximum horizontal cable length from patch panel to
RJ45 outlet at the work area.
As for the horizontal sub-system, the backbone sub-system must be designed using the shortest
routes possible from the MCR rooms to the respective TC closets. Diverse routing will generally
use the shortest secondary route available using adjacent risers if available.
Interlink backbone cables linking adjacent communication closets will again take the shortest
routes for both primary and secondary routes. Adjacent closets are defined as being on the same
level or agreed at further design meetings. This is covered by the star wired system and re-
routing services via patching facilities.
The d3 team will review and comment on the electrical contract drawings after inclusion of
technology input to ensure complete and accurate transfer of information. Define contract
drawings to fully incorporate technology/data/communications network infrastructure designs.
Requirements for communications cable pathways (conduits, sleeves, cable tray, etc.) will be
coordinated with team engineers for inclusion in the electrical construction package.

[Link] Cable Tray and Accessories Installation

As a guide only, the maximum number of UTP cables installed on a tray should be as shown in
Figure 5-12 below. However, this may need to be reduced for bend considerations.

Size of Tray Number of cables

100 mm 100 UTP cables
150 mm 150 UTP cables
300 mm 300 UTP cables
450 mm 495 UTP cables
Table 5-13: Tray Size Capacities
Careful consideration must be taken when designing a containment system containing fibre
components in respect to bend radius etc.

[Link] Trunking and Accessories Installation

The wiring capacity of trunking shall be determined from the standard tables as shown in Table
5-14. The specification is a guideline that must be followed when deciding upon the size of
trunking to be installed. It is based on the formula that for each 25 mm x 25 mm cross section,
10 cables can be accommodated and the stipulation that no trunking should be more than 50%
full on installation.

© Dubai Design District, All rights reserved. Page 153 of 291

 Size of Trunking Number of cables
50 mm x 50 mm 30
50 mm x 75 mm 45
50 mm x 100 mm 60
75 mm x 75 mm 67
75 mm x 100 mm 90
100 mm x 100 mm 120
150 mm x 150 mm 270
Table 5-14: Tray Size Capacities

[Link] Communications Network Equipment Room Specifications

The MCR, MDF/IDF rooms are spaces set aside for the communications equipment shared by
many users. MDF/IDF locations should be centrally situated midway in the riser complex
collapsing to an appropriately sited Mini-Core or MDF Room location. Standard specification for
these locations should be 300 mm high raised floor with antistatic floor tiles, fire protection,
suitably controlled AC unit, security door access and security camera monitoring.
The TIA/EIA – 569-B commercial building standard recommends 0.75 sq. ft. (0.07 sq. m) of
equipment room for every 100 sq. Ft. (10 sq. m) of workstation space (WA). A minimum of 150
sq. ft. (14 sq. m) should be provided for the equipment room. When the number of work areas
to be served is known the equipment room floor space shall be based on the information in the
following Table 5-15. Note that the sizes may change depending on the type of end user and
business requirements. In a multi-tenant buildings or MDUs there might be different equipment
rooms, sectioned areas or one room for specific tenant.
The table below is for Information only and equipment floor space shall properly be coordinated
with all the concerned parties involved in the design.

Room Type Number of Floor Area

Workstations
Main N/A Minimum Size 54 sq. m (9m X 6m)
Communications
Room
MDF 400 –1000 + 36 – 54 sq. m. (6m X 6) – (9m X 6m)
IDF 400 –1000 12 - 36 sq. m. (4 X 3) (6m X 4) (6m X
6)
TC ≤400 2 x 2 x 3 (H)
Table 5-15: Equipment Room Sizes

[Link] Data Centre Tier Types

The ISP SCS is tied into a data centre. There are four data centre tiers as originally defined by
The Uptime Institute in its white paper ‘Industry Standard Tier Classifications Define Site
Infrastructure Performance’. These tiers are explained below.

© Dubai Design District, All rights reserved. Page 154 of 291

 [Link].1 Tier I Data Centre – Basic
A Tier I data centre is susceptible to disruptions from both planned and unplanned activity. It has
computer power distribution and cooling, but it may or may not have a raised floor, a UPS, or an
engine generator. If it does have UPS or generators, they are single-module systems and have
many single points of failure. The infrastructure should be completely shut down on an annual
basis to perform preventive maintenance and repair work. Urgent situations may require more
frequent shutdowns. Operation errors or spontaneous failures of site infrastructure components
will cause a data centre disruption.

[Link].2 Tier II Data Centre – Redundant Components

Tier II facilities with redundant components are slightly less susceptible to disruptions from both
planned and unplanned activity than a basic data centre. They have a raised floor, UPS and
engine generators, but their capacity design is “Need plus one” (N+1), which has a single
threaded distribution path throughout. Maintenance of the critical power path and other parts of
the site infrastructure will require a processing shutdown.

[Link].3 Tier III Data Centre – Concurrently Maintainable

Tier III level capability allows for any planned site infrastructure activity without disrupting the
computer hardware operation in any way. Planned activities include preventive and
programmable maintenance, repair and replacement of components, addition or removal of
capacity components, testing of components and systems and more. For large sites using chilled
water, this means two independent sets of pipes. Sufficient capacity and distribution must be
available to simultaneously carry the load on one path while performing maintenance or testing
on the other path. Unplanned activities such as errors in operation or spontaneous failures of
facility infrastructure components will still cause a data centre disruption. Tier III sites are often
designed to be upgraded to Tier IV when the client’s business case justifies the cost of additional
protection.

[Link].4 Tier IV Data Centre – Fault Tolerant

Tier IV provides site infrastructure capacity and capability to permit any planned activity without
disruption to the critical load. Fault-tolerant functionality also provides the ability of the site
infrastructure to sustain at least one worst-case unplanned failure or event with no critical load
impact. This requires simultaneously active distribution paths, typically in a System-plus-System
configuration. Electrically, this means two separate UPS systems in which each system has N+1
redundancy. Because of fire and electrical safety codes, there will still be downtime exposure
due to fire alarms or people initiating an Emergency Power off (EPO). Tier IV requires all
computer hardware to have dual power inputs as defined by the Institute’s Fault-Tolerant Power
Compliance Specification.
Tier IV site infrastructures are the most compatible with high availability ICT concepts that employ
CPU clustering, RAID DASD, and redundant communications to achieve reliability, availability,
and serviceability.

© Dubai Design District, All rights reserved. Page 155 of 291

 [Link] Telecommunications Tier Types
The ISP SCS is also tied into the telecommunication tier types. There are four telecommunication
tier types.

[Link].1 Tier I (Telecommunications)

The telecommunications infrastructure should meet the requirements of this standard to be rated
at least tier I. A tier I facility will have one customer owned maintenance hole and entrance
pathway to the facility. The access provider services will be terminated within one entrance room.
The communications infrastructure will be distributed from the entrance room to the main
distribution and horizontal distribution areas throughout the data centre via a single pathway.
Although logical redundancy may be built into the network topology, there would be, no physical
redundancy or diversification provided within a tier I facility.
There should be labels applied on all patch panels, outlets and cables as described in
ANSI/TIA/EIA-606-A and annex B of this standard. Similarly, all cabinets and racks shall be
labelled with their identifier at the front and rear.
Some potential single points of failure of a tier I facility are:

 Access provider outage, central office outage, or disruption along a access provider right
of way;
 Access provider equipment failure;
 Of router or switch failure, if they are not redundant;
 Any catastrophic event within the entrance room, main distribution area, or maintenance
hole may disrupt all telecommunications services to the data centre; and
 Damage to backbone or horizontal cabling.

[Link].2 Tier II (Telecommunications)

The Tier II telecommunications infrastructure should meet all the requirements of tier I.
Critical telecommunications equipment, access provider provisioning equipment, production
routers, production LAN switches and production SAN switches, should have redundant
components (power supplies, processors).
Intra-data centre LAN and SAN backbone cabling from switches in the horizontal distribution
areas to backbone switches in the main distribution area should have redundant fibre or wire pairs
within the overall star configuration. The redundant connections may be in the same or different
cable sheathes.
Logical configurations are possible and may be in a ring or mesh topology superimposed onto
the physical star configuration. A tier II facility addresses vulnerability of telecommunications
services entering the building.
A tier II facility should have two customer owned maintenance holes and entrance pathways to
the facility. The two redundant entrance pathways will be terminated within one entrance room.
The physical separation of the pathways from the redundant maintenance holes to the entrance
room is recommended to be a minimum of 20 m (66 ft.) along the entire pathway route. The
entrance pathways are recommended to enter at opposite ends of the entrance room. It is not
recommended that the redundant entrance pathways enter the facility in the same area as this
will not provide the recommended separation along the entire route.
All patch cords and jumpers should be labelled at both ends of the cable with the name of the
connection at both ends of the cable for a data centre to be rated tier 2.
Some potential single points of failure of a tier II facility are:

© Dubai Design District, All rights reserved. Page 156 of 291

  Access provider equipment located in the entrance room connected to same electrical
distribution and supported by single HVAC components or systems;
 Redundant routing and core switching hardware located in the main distribution area
connected to same electrical distribution and supported by single HVAC components or
systems;
 Redundant distribution switching hardware located in the horizontal distribution area
connected to same electrical distribution and supported by single HVAC components or
systems; and
 Any catastrophic event within the entrance room or main distribution area may disrupt all
telecommunications services to the data centre.

[Link].3 Tier III (Telecommunications)

The Tier III telecommunications infrastructure should meet all the requirements of tier II.
The data centre should be served by at least two access providers. Service should be provided
from at least two different access provider central offices or points-of-presences. Access provider
cabling from their central offices or points-of-presences should be separated by at least 20 m (66
ft.) along their entire route for the routes to be considered diversely routed.
The data centre should have two entrance rooms preferably at opposite ends of the data centre
but a minimum of 20 m (66 ft.) physical separation between the two rooms. It should not share
access provider provisioning equipment, fire protection zones power distribution units and air
conditioning equipment between the two entrance rooms. The access provider provisioning
equipment in each entrance room should be able to continue operating if the equipment in the
other entrance room fails.
The data centre should have redundant backbone pathways between the entrance rooms, main
distribution area and horizontal distribution areas.
Intra-data centre LAN and SAN backbone cabling from switches in the horizontal distribution
areas to backbone switches in the main distribution area should have redundant fibre or wire pairs
within the overall star configuration. The redundant connections should be in diversely routed
cable sheathes.
There should be a “hot” standby backup for all critical telecommunications equipment, access
provider provisioning equipment, core layer production routers and core layer production
LAN/SAN switches. All cabling, cross-connects and patch cords should be documented using
spreadsheets, databases, or programs designed to perform cable administration. Cabling system
documentation is a requirement for a data centre to be rated tier 3.
Some potential single points of failure of a tier 3 facility are:

 Any catastrophic event within the main distribution area may disrupt all
telecommunications services to the data centre; and
 Any catastrophic event within a horizontal distribution area may disrupt all services to
the area it servers.

[Link].4 Tier IV (Telecommunications)

The Tier IV telecommunications infrastructure should meet all the requirements of tier III.
Data centre backbone cabling should be redundant. Cabling between two spaces should follow
physically separate routes, with common paths only inside the two end spaces. Backbone cabling
should be protected by routing through conduit or by use of cables with interlocking armour.

© Dubai Design District, All rights reserved. Page 157 of 291

 There should be automatic backup for all critical telecommunications equipment, access provider
provisioning equipment, core layer production routers and core layer production LAN/SAN
switches. Sessions/connections should switch automatically to the backup equipment.
The data centre should have a main distribution area and secondary distribution area preferably
at opposite ends of the data centre but a minimum of 20 m (66 ft.) physical separation between
the two spaces. Do not share fire protection zones, power distribution units and air conditioning
equipment between the main distribution area and secondary distribution area. The secondary
distribution area is optional, if the computer room is a single continuous space, there is probably
little to be gained by implementing a secondary distribution area.
The main distribution area and the secondary distribution area will each have a pathway to each
entrance room. There should also be pathway between the main distribution area and secondary
distribution area.
The redundant distribution routers and switches should be distributed between the main
distribution area and secondary distribution area in such a manner that the data centre networks
can continue operation if the main distribution area, secondary distribution area, or one of the
entrance rooms has a total failure.
Each of the horizontal distribution areas should be provided with connectivity to both the main
distribution area and secondary distribution area. Critical systems should have horizontal cabling
to two horizontal distribution areas. Redundant horizontal cabling is optional even for tier 4
facilities
Some potential single points of failure of a tier IV facility are:

 The main distribution area (if the secondary distribution area is not implemented); and
 At the horizontal distribution area and horizontal cabling (if redundant horizontal cabling
is not installed).

[Link] Data Centre Design Overview

The Figure 5-17 below concentrates on the redundancy of the communications network
infrastructure. A Tier II facility has a second entrance manhole at least 66 feet (20 meters) from
the primary entrance hole. In a Tier III facility, this leads to a second entrance room, also 66 feet
(20 meters) from the primary entrance room and with separate power distribution, HVAC and fire
protection. Cabled conduit may be used to interconnect the primary and secondary maintenance
holes and entrance rooms for further flexibility.

© Dubai Design District, All rights reserved. Page 158 of 291

 Figure 5-17: Hierarchy Design Overview

Redundancy can be further enhanced by using a second telecommunications provider, as long

as the back-up provider uses different routing and a different central office than the first provider.
Within the computer room, a second distribution area makes sense as long as it and the
equipment it serves are in a different room than the main distribution area.
Redundant horizontal and backbone cabling provide another level of redundancy if they are
placed in different routes. As a secondary route may be longer, take care to make sure that the
maximum channel length is not exceeded.
Tier IV is a fault tolerant data centre with multiple pathways and components so that it stays in
operation during a planned shutdown of any of these infrastructures. It is also built to withstand
at least one worst-case unplanned event. All equipment has redundant data and power cabling
over separate routes. Separate distribution areas may serve mirrored processing facilities.
Seismic protection is increased to beyond minimum requirements, as is the ability to withstand
hurricanes, flooding or even terrorist attack. A Tier IV data centre should expect an uptime of
99.995% or better — downtime, which should be due to a planned test of fire alarm or emergency
power-off, should be no more than a few minutes a year.
The purpose of this example diagram Figure 5-17 is to highlight the different areas associated
within the data centre. Data centres concentrate a great deal of electronic equipment in a small
area, so they require organization to handle growth and reconfiguration the above highlights a
fully loaded example. This includes placement of electrical and communications network
entrance rooms, HVAC (Heating Ventilation Air Conditioning, sometimes called the mechanical
equipment), a network operations centre, offices for personnel, redundant power and, of course,
the computer room. Other issues include placing racks, cabinets and equipment for optimum
cooling, grouping them for efficiency and segregating them for security. The diagram below

© Dubai Design District, All rights reserved. Page 159 of 291

 indicates all of these areas and goes on to describe the infrastructure elements associated with
the data centre.

Figure 5-18: Layout of a typical Data Centre

[Link].1 Entrance Facility

The Entrance Facility (EF) is the place where cabling system enters the building and it is being
envisioned to have redundant entrances i.e. The primary and secondary for the service provider.
The active equipment that connects the data centre to both the private and the public access
provider resides here. Active equipment breaks the access provider’s signal down into channels
that can be passed to the main distribution area over the backbone cabling. OM3 50 μm
multimode and 8.3 μm single mode distribution backbone fibre cabling is terminated with compact
LC connectors and connected through SCS patch panels/fibre management hardware. Cross
connects shall be implemented here to forward transmission to the MDA, MCR/MDF etc. Care
shall be taken as to final layout with a focus on security and demarcation between SP and ECA.
Refer to data centre floor layout Figure 5-18 for details.

© Dubai Design District, All rights reserved. Page 160 of 291

 [Link].2 Main Distribution Area (MDA)
The Main Distribution Area (MDA) is the central space where the point of fully redundant
distribution for the structured cabling system in the data centre is located. The data centre shall
have at least 2 main distribution areas. The routers and core switches for the data centre
networks are located in or near the main distribution area.
The MDA(s) are positioned in the Data Cent to keep the backbone connections to the horizontal
distribution areas as short as possible. From the MDA, single mode fibre shall connect to the
Entrance Facility (EF) room and is usually routed via primary and secondary pathways.
The MDA areas shall also be used to support inter-connectivity and primary and secondary routed
links to the Horizontal Distribution Area (HDAs). The inter-connectivity may cover Core,
Aggregation, Distribution, SAN, Intranet, Extranet, management links, etc. Connectivity shall be
achieved using patch cords between racks or patch panel to patch panel. The Figure 5-19 shows
an example of a MDA.

Figure 5-19: Example MDA

[Link].3 Horizontal Distribution Area (HDA)

The horizontal distribution area (HDA) is the space that supports cabling to the equipment
distribution areas. The LAN, SAN, console and KVM switches that support the end equipment
are also typically located in the horizontal distribution area. There are multiple HDA areas set out
in a modular zoned layout to serve the data centre.
If the data centres use multiple organizations tenants, such as Internet, hosting and collocation
facilities, the horizontal distribution areas should be in a secure space. These areas have been
specifically designed to localize patching and avoid long patch.

© Dubai Design District, All rights reserved. Page 161 of 291

 Figure 5-20: Example HDA

[Link].4 Storage Area Network (SAN)

The Storage Area Network (SAN) is the space that supports cabling to the MDA, HDA, and server
rack area within the data centre. This area shall comprise of passive and active equipment to
cover Direct Attached Storage (DAS), Networked Attached Storage (NAS), and Storage Area
Networks (SAN) FC IP. The cabling used in this section may vary depending on the application
to be used. The connectivity between components should be carefully coordinated between all
parties to ascertain correct component and connectivity levels.
Single mode fibre is recommended to be installed as this will accommodate differing fibre channel
upgrades throughout the life cycle of the data centre. This cabling infrastructure will support high
performance SAN and NAS implementations. OM3 fibre may be considered for rack inter-
connectivity.

© Dubai Design District, All rights reserved. Page 162 of 291

 Figure 5-21: Example SAN

[Link].5 Access Floor

Access flooring is made from a variety of materials that combine strength with anti-static
properties. The panels are a standard 24 in x 24 in (600 mm x 600 mm) and are supported at the
corners by posts attached to the slab. Stringers may be run between the posts for additional
stability. TIA-942 recommends distributed floor loads of 250 lbf/ft2 (12 kPA) (minimum allowable
load is 150 lbf/ft2 [7.2 kPA]). A hanging capacity of 50 lbf/ft2 (2.4 kPA) for cable trays is
recommended (minimum allowable load is 25 lbf/ft2 [1.2 kPA]). Flooring should be electrically
continuous and fully earth bonded. The flooring system should at minimum meet NFPA 75
requirements for fire protection. Local codes take precedence if they are stricter.

[Link].6 GSM Landing Point

A separate GSM landing point room may be required for multi storied buildings and should be
adjacent to TER. ECA will advise at the time of MCR request if a separate GSM landing point
room will be required. Minimum dimension for GSM landing point room is 4 (W) x 3 (L) x 3 (H).
A 450 x 200 mm slot to be provided below raised floor level with cable basket (as noted below)
fitted to allow routing of cables between TER and GSM landing point room. GSM landing point
room is to follow the same specifications as the MCR but it is recommended to have a dedicated
riser for this to all GSM service providers to lay their cables.

[Link].7 Cable Containment

The entry points for external cables i.e., routing to site duct system, should be managed in cable
basket or cable tray mounted below raised floor to the equipment cabinet locations. Basket/tray
is to be sized at 450 x 100 mm and 200 mm x 100 mm to accommodate large volume of copper

© Dubai Design District, All rights reserved. Page 163 of 291

 and fibre cables. Layout of the cable containment and cable basket/tray work to be agreed on
when room layout is finalized.

[Link].8 Utility Services

All DC and POP rooms to be completely free of utility piping carrying any form of liquids, no
location above the room should have any water carrying services. If wet area exists above the
TER, then an attic slab will be required (note requirement for 3 meter clear height). Mains voltage
cables must not be routed through this room. The TER should be free of all safety hazards and
should have no suspended ceiling.

[Link].9 Environmental Requirements

The environmental control requirements shall include:

 Air conditioning, temperature control and humidity control

 Fire detection and fire protection
 Power supplies (Mains and uninterruptible power supplies)
 Lighting controls (normal and emergency)
 Primary and assistant closed Control air Conditioning Units (CCU) to be fitted and to be
interlocked with each other
 Temperature must be maintained at 20° Celsius ± 3° Celsius - heat dissipation figures to
be calculated based on 500 Watts per sq. m of DC and POP floor area (1706 BTU/Hr)
 Relative humidity (non-condensing) must be maintained at 50% ± 10 %
 The room must contain a manual / auto control air-conditioning switch and must digitally
display temperature for operators
 The ambient temperature and humidity shall be measured at distance of 1.5 m (5ft)
above the floor level, after the equipment is in operation, at any point along an
equipment aisle centre line.

[Link].10 Electromagnetic Interference

The room shall be located away from sources of electromagnetic interference. Special attention
shall be given to electric power supply transformers, motors and generators, X-ray equipment,
radio or radar transmitters and induction sealing devices.

[Link].11 Lighting Requirements

An average illumination level of 500 lux measured 1 meter above finished floor is required in the
DC and POPs. Lighting shall be minimum of 500 lux (50 foot candles), measured at 1m (3ft)
above the finished floor in middle of all aisles between cabinets. The lighting shall be controlled
by one or more switches located near the entrance doors to the room. Generator backup should
be considered.

NOTE: The lighting fixtures should not be powered from the same electrical distribution panel as
the communications network equipment in the ER. Dimmer switches should not be used and
emergency lighting and signs should be properly placed such that an absence of light will not
hamper emergency exit.

© Dubai Design District, All rights reserved. Page 164 of 291

 [Link].12 Fire Suppression System
An automatic fire suppression system using inert gas (FM200 / Inergen / Argon) to the local
standards / regulations is required at ceiling height and below the raised floor. Gas integrity
testing must be carried out on the room and the results passed to ECA. Additionally, a local
government certificate may be required for the DC and POP locations.

[Link].13 Video Surveillance Monitoring for DC and TER

A minimum of one camera / monitoring point linked to Smart cities network is recommended.
Camera / monitoring system placement will allow for recognition and identification of all incoming
personnel to TER room and data centre. Video surveillance cameras should be deployed both
inside and outside of the TER room and DC. The solution should be built over IP platform so that
the monitoring could be done from central command and control centre in CCC. The solution
should be closely tied in with IP based access control system as well.

[Link].14 Access Control for DC and TER Rooms

The TER and DC should be secured from access from all unauthorized personnel. Entrance and
access to TER and DC shall only be available to service provider personnel and authorized staff
24 x 7 x 365. Electronic and smart card IP based access control solution shall be employed on
all entrance doors. The IP based access control system will ease its integration with IP Video
Surveillance solution so that if any unauthorized person tries to enter through the doors, an alarm
could be initiated towards CCC and video surveillance manager and the cameras in the vicinity
could be activated to monitor the incidence. This video information could later be used for proper
investigation and event analysis.

[Link].15 Electrical Systems

The electrical system must comply with the local electricity authority standards. Separate supply
circuit serving the DC & PoPs shall be provided and terminated in its own electrical panel. Electric
power provisioning for the DC and POPs, is not specified herein because it is dependent upon
the equipment load and supporting facilities.

If stand by power source is available in the building, the DC’s and POP panel should be connected
to standby supply. This standby generator should feed UPS load, rectifiers, 50% of standard
lighting and standby A/C units. The electrical layout will be agreed upon completion of equipment
design, power sockets to be distributed by bus bar or power cable routed inside flexible metal
conduit.

[Link].16 Earthing Requirements

Two separate earth bars shall be supplied for AC and DC active equipment. This should be
entirely separate from the building earth. Grounding should also include any raised floor
installations. Refer to ANSI/TIA/EIA-607 for detailed specifications of the required
communications earthing system.

[Link].17 Labelling
All plant items and individual components shall be clearly labelled as per ANSI/TIA/EIA-606-A
with designation shown on the accompanying drawings. A full description of the item should also
be included. The labels should be of the engraved plastic “Trifoliate” or similar type and fixed to
the plant item in a permanent manor.

© Dubai Design District, All rights reserved. Page 165 of 291

 [Link].18 Design Considerations for Smart cities
The Smart cities data centre and POP’s must be readily accessible to ICT personnel and
equipment 24 hours/day, 7 days a week and secured from unauthorized entry via IP based video
surveillance and access control solutions. It is required that the TER be located away from
sources of high voltage (such as substation transformer room) and not be in close proximity to
any garbage rooms. The distance margin should be a minimum of 30 meters or more. The room
must meet the criteria as detailed below:

 DC and POP walls, floor and ceiling should be finished in such a manner as to eliminate
dust and static electricity. Walls and ceilings shall receive primer and finish coat of light
colour paint;
 The DC and POP should not be located below water table level unless preventative
measures against water ingress are employed; and
 The TER shall be free from all water and drainage pipes not directly required in the
support of the equipment within the TER. A floor drain fitted with an automatic
submersible pump shall be provided in the case of any risk of water ingress.
 During the detail designing (Low Level Design) for DC and POPs, the possibility for
physical capacity expansion should be considered. The physical layout of the DC and
POP should be designed in a way that if there is a need in future to further expand the
floor area of the DC then there is reserved land available either behind or on the lateral
sides of DC.
 At the time of DC floor area expansion, the new floor could be constructed first and then
by removing a common wall between the old and new DC floor, both areas could be
merged.
 No equipment or racks shall be placed next to the common wall between the main DC
floor and reserved expansion land. This early consideration will help merge the old and
new DC floors without impact to live services.

[Link].19 Estimate for Data Centre Power Requirements

The following Table 5-16 provides the guidelines for electrical power calculations for the data
centre.

Item Estimated Data Centre Power Requirements

Power Calculations Electrical
Data Required Description of Totals Subtotals
Calculations Kw
#1 Rating for each ICT (Calculator total in VA x 0.67) /
Device 1000
#2 General Power ( Subtotal VA x 0.67 ) / 1000
Requirements
#3 Future Capacities [ (Add VA rating of future
devices) x 0.67 ] / 1000
#4 Total Power Draw inc ( # 1 + # 2 + # 3 ) x 1.05
variations

© Dubai Design District, All rights reserved. Page 166 of 291

 #5 Actual Load + Future ( # 1 + # 2 + # 3 ) x 0.32
Loads UPS and Battery
(In kW)
#6 Lighting 0.002 x floor area (sq. ft.) or
0.0215 x floor area (sq. m)
#7 Total Power to support (# 4 + # 5 + # 6)
electrical demands
Power Calculations – Cooling
#8 Total from # 7 above For Chiller systems # 7 x 0.7
For DX systems # 7 x 1.0
Total Power Requirement
#9 Total from # 7 and # 8 (# 7 + # 8)
above
Electrical Service Budget
#10 Total from # 9 above (# 9 x 1.25)
#11 AC voltage Volts
Total from # 10 and AC (# 10 x 1000) / (# 11 x 1.73) Amps
voltage in # 11
Standby Generator Estimate (Optional)
#12 Total from # 7 above # 7 x 1.3
#13 Total from # 8 above # 8 x 1.5
Size of generator Total from #12 and #13
needed above
Table 5-16: Example Data Centre Power Requirements

The following bullet points explain the assumptions taken in the Table 5-16:
#1 The Power Rating for each ICT device within the rack based on VA. An allowance of 30% has
been estimated for passive racks. The 0.67 coefficient is a diversity factor as the name tag
power is worst case scenario and never equates to actual power
#2 General power requirements cover all other power needed within the Data Centre such as:
ring main and radial circuits to cover 13A sockets, BMS, security, fire life and safety etc.
These calculations are based on 0.3 kW per square meter
#3 Future capacities cover ICT based equipment to come on line at later stages during the Smart
cities growth plans. There is a built in estimate of an additional 40 racks assuming the same
criteria as in #1 for calculations
#4 this is the total Power draw from sections ((#1 + #2 + #3) x 1.05) to accommodate variations
on power demand
#5 this is the total actual load plus future load for UPS and battery. The only time a full load
would be applied here is when the batteries have been drained and recharging power may
account for 20% of the UPS rated load
#6 lighting load in the data centre is nominal compared to other systems and draws the least
amount of load. The calculations are based on 0.0215A per square meter

© Dubai Design District, All rights reserved. Page 167 of 291

 #7 This Total Power to support electrical demands cumulative through (#4 + #5 + #6)
#8 Covers cooling with two factor built in the first of which has not been used, using a chilled
water system is generally more efficient as a rule of thumb the power consumption is
somewhere around 70% of the total load being supported. Direct Expansion (DX) systems
require approximately 100% of the total load being supported. This calculation is done based
on worst case
#9 Therefore the total power requirements for the data centre including Cooling is the total of (#7
+ #8)
#10 The Electrical capacity required in Kilowatts is multiplied by 125% as required by the National
Electrical Code and most likely governed by local codes
#11 The Single Phase Voltage 220V multiplied by 1.73 provides a 3 phase voltage of 380V. The
total provided in this section is in Amps as sometimes required or requested from the utility
service provider. This calculation is based on total Power divided by the three phase voltage
#12 this an estimate for the Generator load based the data centre load with attention given to
electrical characteristics of the loads to be attached to the generator through a transfer switch.
Mechanical loads require high starting current imposing harmonic currents native with
generators hence the reason for the 1.3 coefficient. When selecting a UPS system the
operating characteristics should be favourable to reliable generator operation
#13 the coefficient of 1.5 is higher in the cooling section due to the higher mechanical demands
associated with the HVAC equipment. Therefore, the size of generator estimated for the data
centre is the total of (#12 + #13)
Note: The description above has also been adopted in the calculations for the Primary and
Secondary POP locations in the following Table 5-17 and Table 5-18 respectively.
The calculations provided above are for information purposes only and should be re-confirmed
by the MEP consultant.

[Link].20 Estimate for Primary PoP Power Requirements

The following Table 5-17 provides the guidelines for electrical power calculations for the Primary
POP.

Data Required Description of Totals Subtotals

Calculations Kw
#1 Rating for each ICT Device (Calculator total in VA x 0.67
) / 1000
#2 General Power ( Subtotal VA x 0.67 ) / 1000
Requirements
#3 Future Capacities [ (Add VA rating of future
devices) x 0.67 ] / 1000
#4 Total Power Draw inc ( # 1 + # 2 + # 3 ) x 1.05
variations
#5 Actual Load + Future Loads ( # 1 + # 2 + # 3 ) x 0.32
UPS and Battery (In kW)
#6 Lighting 0.002 x floor area (sq. ft.) or
0.0215 x floor area (sq. m)

© Dubai Design District, All rights reserved. Page 168 of 291

 #7 Total Power to support (# 4 + # 5 + # 6)
electrical demands
Power Calculations – Cooling
#8 Total from # 7 above For Chiller systems # 7 x 0.7
For DX systems # 7 x 1.0
Total Power Requirement
#9 Total from # 7 and # 8 (# 7 + # 8)
above
Electrical Service Budget
#10 Total from # 9 above (# 9 x 1.25)
#11 AC voltage Volts
Total from # 10 and AC (# 10 x 1000) / (# 11 x 1.73) Amps
voltage in # 11
Standby Generator Estimate (Optional)
#12 Total from # 7 above # 7 x 1.3
#13 Total from # 8 above # 8 x 1.5
Size of generator needed Total from # 12 and # 13
above
Table 5-17: Example Primary POP Power Requirements

Power calculations for Primary POP in Table 5-17 are based on the following assumptions:

#1 The Power Rating for each ICT Device within the rack based in VA. The 0.67 coefficient is a
diversity factor as the name tag power is worst case scenario and never equates to actual
power
#2 General power requirements cover all other power needed within the data centre such as:
ring main and radial circuits to cover 13A sockets, BMS, Security, Fire Life and Safety etc.
These calculations are based on 0.3 kW per square meter
#3 Future capacities cover ICT based equipment to come on line at later stages during the Smart
cities growth plans. There is a built in estimate of an additional 6 racks assuming the same
criteria as in #1 for calculations
#4 this is the total Power draw from sections ((#1 + #2 + #3) x 1.05) to accommodate variations
on power demand
#5 this is the total actual load plus future load for UPS and battery. The only time a full load
would be applied here is when the batteries have been drained and recharging power may
account for 20% of the UPS rated load
#6 lighting load in the data centre is nominal compared to other systems and draws the least
amount of load. The calculations are based on 0.0215A per square meter.
#7 This Total Power to support electrical demands cumulative through (#4 + #5 + #6)
#8 Covers cooling with two factor built in the first of which has not been used, using a chilled
water system is generally more efficient as a rule of thumb the power consumption is

© Dubai Design District, All rights reserved. Page 169 of 291

 somewhere around 70% of the total load being supported. Direct Expansion (DX) systems
require approximately 100% of the total load being supported. This calculation is done based
on worst case
#9 Therefore the total power requirements for the data centre including cooling is the total of (#7
+ #8)
#10 The Electrical capacity required in Kilowatts is multiplied by 125% as required by the National
Electrical Code and most likely governed by local codes
#11 this is the Single Phase Voltage 220V multiplied by 1.73 provides a 3 phase voltage of 380V.
The total provided in this section is in Amps as sometimes required or requested from the
Service Utility provider. This calculation is based on total Power divided by the three phase
voltage
#12 this an estimate for the Generator load based the data centre load with attention given to
electrical characteristics of the loads to be attached to the generator through a transfer switch.
Mechanical loads require high starting current imposing harmonic currents native with
generators hence the reason for the 1.3 coefficient. When selecting a UPS system the
operating characteristics should be favourable to reliable generator operation
#13 the coefficient of 1.5 is higher in the cooling section due to the higher Mechanical demands
associated with the HVAC equipment. Therefore, the size of generator estimated for the data
centre is the total of (#12 + #13)
The calculations provided above are for information purposes only and should be re-confirmed
by the designated MEP consultant for d3.

[Link].21 Estimate for Secondary PoP Power Requirements

The following Table 5-18 provides the guidelines for electrical power calculations for the
Secondary POP.

Item Estimated Secondary POP Power Requirements

Power Calculations Electrical
Data Required Description of Totals Subtotals
Calculations Kw
#1 Rating for each ICT (Calculator total in VA x
Device 0.67 ) / 1000
#2 General Power ( Subtotal VA x 0.67 ) / 1000
Requirements
#3 Future Capacities [ (Add VA rating of future
devices) x 0.67 ] / 1000
#4 Total Power Draw inc ( # 1 + # 2 + # 3 ) x 1.05
variations
#5 Actual Load + Future ( # 1 + # 2 + # 3 ) x 0.32
Loads UPS and Battery (In
kW)
#6 Lighting 0.002 x floor area (sq. ft.) or
0.0215 x floor area (sq. m)

© Dubai Design District, All rights reserved. Page 170 of 291

 #7 Total Power to support (# 4 + # 5 + # 6)
electrical demands
Power Calculations – Cooling
#8 Total from # 7 above For Chiller systems # 7 x
0.7
For DX systems # 7 x 1.0
Total Power Requirement
#9 Total from # 7 and # 8 (# 7 + # 8)
above
Electrical Service Budget
#10 Total from # 9 above (# 9 x 1.25)
#11 AC voltage Volts
Total from # 10 and AC (# 10 x 1000) / (# 11 x 1.73) Amps
voltage in # 11
Standby Generator Estimate (Optional)
#12 Total from # 7 above # 7 x 1.3
#13 Total from # 8 above # 8 x 1.5
Size of generator Total from # 12 and #
needed 13 above
Table 5-18: Example Secondary POP Power Requirements

Power calculations for Secondary POP in Table 5-18 are based on the following assumptions:

#1 The Power Rating for each ICT Device within the rack based in VA. The 0.67 coefficient is a
diversity factor as the name tag power is worst case scenario and never equates to actual
power
#2 General power requirements cover all other power needed within the data centre such as:
Ring Main and radial circuits to cover 13A sockets, BMS, Security, Fire Life and Safety etc.
These calculations are based on 0.3 kW per square meter
#3 Future capacities cover ICT based equipment to come on line at later stages during the Smart
cities growth plans. There is a built in estimate of an additional 6 racks assuming the same
criteria as in #1 for calculations
#4 this is the total Power draw from sections ((#1 + #2 + #3) x 1.05) to accommodate variations
on power demand
#5 is the total actual load plus future load for UPS and battery. The only time a full load would
be applied here is when the batteries have been drained and recharging power may account
for 20% of the UPS rated load
#6 lighting load in the data centre is nominal compared to other systems and draws the least
amount of load. The calculations are based on 0.0215A per square meter
#7 This Total Power to support electrical demands cumulative through (#4 + #5 + #6)

© Dubai Design District, All rights reserved. Page 171 of 291

 #8 Covers cooling with two factor built in the first of which has not been used, using a chilled
water system is generally more efficient as a rule of thumb the power consumption is
somewhere around 70% of the total load being supported. Direct Expansion (DX) systems
require approximately 100% of the total load being supported. This calculation is done based
on worst case
#9 Therefore the total power requirements for the data centre including cooling is the total of (#7
+ #8)
#10 the electrical capacity required in Kilowatts is multiplied by 125% as required by the National
Electrical Code and most likely governed by local codes
#11 is the Single Phase Voltage 220V multiplied by 1.73 provides a 3 phase voltage of 380V. The
total provided in this section is in Amps as sometimes required or requested from the Service
Utility provider. This calculation is based on total Power divided by the three phase voltage
#12 this an estimate for the Generator load based the data centre load with attention given to
electrical characteristics of the loads to be attached to the generator through a transfer switch.
Mechanical loads require high starting current imposing harmonic currents native with
generators hence the reason for the 1.3 coefficient. When selecting a UPS system the
operating characteristics should be favourable to reliable generator operation
#13 the coefficient of 1.5 is higher in the cooling section due to the higher Mechanical demands
associated with the HVAC equipment. Therefore, the size of generator estimated for the data
centre is the total of (#12 + #13)
The calculations provided above are for information purposes only and should be re-confirmed
by the MEP consultant.

5.3 Other City Systems

5.3.1 Traffic Lights
Traffic light and traffic management system is provided by RTA. d3 will only ensure that the data
required from RTA is captured by the Data Virtualization System.
To ensure accessibility, Smart Traffic management must be used to ensure smooth and safe
traffic flows particularly near public area that include, schools, colleges, universities, hospitals and
parks

[Link] Smart Dubai KPI

The below table describes the interpretation of the KPI associated with Traffic Lights (signal):

Smart Dubai KPIs d3 Interpretation of the KPI

I6.4.2 Street Lighting & signal system management with ICT Number of ICT enabled
measures count by number of sensors per kilometre in overall Sensors connected to the d3
street lighting system CCC
Table 5-19: Traffic Lights (signal) KPI Interpretation

© Dubai Design District, All rights reserved. Page 172 of 291

 5.3.2 Outdoor Sensors
[Link] Description
The Multifunction sensors are required to provide insight into the environmental conditions of the
city. These sensors have to be spread over regular intervals to monitors some of the most
important environmental conditions like air pollution, water flooding on roads and streets,

[Link] Functional Blocks

Gaseous Air Pollution

3G/LTE or WiFI or
Dust /Suspended Air Pollution Fiber/Copper d3 Command and Control
connection Center (CCC)
Road Flooding Telephone line to d3 IP Network
Civil Defence
Noise Level Centralized Management

Typical Sensor or End Point

[Link] Typical List of Parameters to be monitored

 Gaseous Air Pollution

 Dust cum Suspended Air Pollution
 Road Flooding
 Noise Level

[Link] d3 IP Network Connectivity

The Multifunction Sensors shall communicate either directly or via a Control Field using one of
the following methods of communication.

 GSM/ 3G/ LTE

 Wi-Fi
 Wired

These sensors or Field devices shall provide for time stamped logging of the parameters and as
well the centralized management server shall be used to log the data, provide appropriate
graphical user interface and also to generate reports. The Field devices must have capability to
use standard protocols like TCP/IP, Bacnet/IP, Modbus and DPN3, or as required by design
consultant. The interfaces connectivity between the Field device and the sensors or control
devices can be serial RS 232 /RS 245 interfaces or Ethernet interfaces (TCP/IP).

[Link] Centralized Management

d3 will have a centralized management system that will enable remote monitoring and
management of the sensors. The Centralized Management System shall provide capability of
displaying information on maps using geo location coordinates, provide reports and have the
capability to record data and display historical data in the shape of customized reports. The

© Dubai Design District, All rights reserved. Page 173 of 291

 application must have capability to use standard protocols like TCP/IP, Bacnet/IP, Modbus and
DPN3.
The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Smart Dubai KPI

Smart Dubai KPIs d3 Interpretation of the KPI
I4.1.4 Convenience of smart traffic Provision of ICT enabled traffic sensors
information administration and service connected to the d3 CCC and conducting
satisfaction surveys
Count by ratio of convenience expression
about smart traffic in paper/online interview
I4.2.2 Penetration of ICT for natural disaster Provision of ICT enabled natural disaster
sensors connected to the d3 CCC
Count by number of various sensors per
square kilometre in disaster-prone regions
I4.2.3Publication rate of natural disaster alert Provision of ICT enabled natural disaster
Count by ratio of disasters that is alerted sensors connected to the d3 CCC
ahead of time each year
I2.1.4 Proportion of air pollution monitoring Provision of ICT enabled air pollution
by means of ICT measures sensors connected to the d3 CCC
Count by number of air quality sensors per
square kilometre
I2.1.5 Proportion of toxic substances Provision of ICT enabled dangerous/toxic
monitoring by means of ICT measures substances sensors connected to the d3
CCC
Count by ratio of highly dangerous toxic
substance sources under control with the
help of ICT
I2.1.6 Proportion of noise monitoring by Provision of ICT enabled noise monitoring
means of ICT measures sensors connected to the d3 CCC
Count by number of noise sensors per
square kilometre

© Dubai Design District, All rights reserved. Page 174 of 291

 I6.2.1 Coverage of installation of road Provision of ICT enabled road sensors
sensing terminals connected to the d3 CCC
count by number of road sensors per
kilometre in overall urban road coverage
I3.1.8 Improvement of traditional industry Statistical data on GDP vs. traditional
with ICT Count by ratio of GDP improvement business improvements measures
due to technology upgrade
Table 5-20: Smart Dubai KPI's for Outdoor Sensors

5.3.3 Weather Station

[Link] Description
Weather stations are portable or fixed devices that can be placed with d3 to provide a very realistic
weather conditional prevalent with d3 at any moment of time. One or several such stations can
be placed with the boundaries of d3. This will allow d3 to predict weather conditions within d3
accurately and can enable its residents, tenants, employees and visitors be abreast with the most
react and very accurate weather conditions. Inputs can also be used by other automation system
that may be dependent on the weather conditions e.g. the irrigation system.

[Link] Functional Blocks

Temperature

Humidity
Remote
Wind Direction Measurement and d3 Command and Control
Control Field Center (CCC)
d3 IP Network
Wind Speed Devices

Centralized Management
Rainfall

Typical Measurement and/

or Control Parameters

Figure 5-22: Weather Station Logical Architecture

[Link] Typical List of Parameters to be monitored

 Temperature
 Humidity
 Wind Direction
 Wind Speed
 Rainfall

[Link] d3 IP Network Connectivity

For Weather Station device shall use any of the following methods of communication:

 GSM/ 3G/ LTE

 City Wi-Fi

© Dubai Design District, All rights reserved. Page 175 of 291

 The end points or sensors within the vehicle shall be communicate with a vehicle management
system within the d3 data centre using standard protocols like TCP/IP, DHCP, FTP, HTTP,
HTTPS, NTP, RTP, RTSP, SMTP, SNMP, etc.

[Link] Centralized Management

Weather Station device shall communicate to the Weather Management System in the d3 data
centre to enable management and operations of the services. The services can potentially need
to communicate with more than one application in the d3 data centre that are but not limited to
the following:

 Digital Signage System

 Command and Control Server
 Data Virtualization Server
 GIS Server

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Smart Dubai KPI

No KPIs defined for this service

5.3.4 Connected Bus

[Link] Description
This Connected Bus shall extend services to passengers to include enhanced safety and security
services; improved user experience by providing free Internet, interactive signage that includes
timetable information, road conditions, traffic conditions and other relevant d3 city data. This
service shall be provided jointly by d3 Smart Service team and the transportation section of RTA.

© Dubai Design District, All rights reserved. Page 176 of 291

 [Link] Functional Blocks

Geo-Location

CCTV Camera D3 & or RTA Command and

3G/LTE or WiFI
Router Control Center (CCC)
Interactive Digital Sign d3 IP Network

Ticketing System Centralized Management

Typical Sensor or End Point

Figure 5-23: Connected Bus Logical Architecture

[Link] Typical List of Sensors and or End Points to be monitored

 Geo-Location
 CCTV Camera
 Interactive Digital Sign
 Ticketing System

[Link] d3 IP Network Connectivity

For connected bus all the endpoints shall connect using an IP gateway that shall have the
capability to connect to the d3 network using either wired IP network or wireless network. The
connectivity can be one or more of the following types:

 GSM/ 3G/ LTE

 City Wi-Fi
 Smart City Fibre Network

The end points or sensors within the bus shelter shall connect to the IP based router or gateway
using 10/100/1000 PoE based Ethernet copper using Cat6 Cable and RJ45 Connectors. Some
of the sensors can also connect using the integrated Wi-Fi network on the Gateway. The
passengers can also use the d3 Wi-Fi Network on their mobile device.
The end points or sensors within the bus shelter shall be communicate with their respective
applications within the d3 data centre using standard protocols like TCP/IP, Bacnet/IP, Modbus
and DPN3. The devices shall also support protocols such as DHCP, FTP, HTTP, HTTPS, NTP,
RTP, RTSP, SMTP, SNMP, SSL / TSL. The devices shall support quality of service, minimum
DCSP.

[Link] Centralized Management

Different end points shall communicate to their respective application in the d3 data centre to
enable management and operations of the services defined for the bus. The services can be a
combination of more than one application in the d3 data centre that are but not limited to the
following:

 LAN/ WAN/ WiFi/ Security Management Server

 Digital Signage Manager
 CCTV Management Server
 Command and Control Server

© Dubai Design District, All rights reserved. Page 177 of 291

  Data Virtualization Server
 GIS Server

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Smart Dubai KPI

No KPIs defined for this service

5.3.5 Connected Garbage Bins

[Link] Description
The Intelligent Waste Management System enables the level of Solid Waste, Recycled Waste,
Medical Waste or Electronic Waste (E-Waste) to be remotely monitored using wireless sensors
installed in the waste bin. Waste collection is then managed via a Web Portal.

[Link] Functional Blocks

The figure below provides a high level functional view of the Connected Garbage Bins Network
System

Waste Level in the bin Mobile Network

Operator d3 Command and Control
Or Center (CCC)
Geo-Location d3 IP Network
City WiFi

Centralized Management

Typical Sensor or End Point

Figure 5-24: Connected Garbage Bins Logical Architecture

© Dubai Design District, All rights reserved. Page 178 of 291

 [Link] Typical List of Parameters to be monitored

 Waste Level in the bin

 Geo-Location of the bin

[Link] d3 IP Network Connectivity

For the communication between the centralized management system and the Remote Sensor
can use one or more methods of communication as listed below:

 GSM/ 3G/ LTE

 City Wi-Fi

These Field devices shall provide for time stamped logging of the parameters and as well the
centralized management server shall be used to log the data, provide appropriate graphical user
interface and also to generate reports. The Field devices must have capability to use standard
protocols like TCP/IP, Bacnet/IP, Modbus and DPN3, or as required by design consultant.

[Link] Centralized Management

The wireless bin sensors automatically measure container fill levels hourly and send updates
to the Web portal via GSM cellular communications. Immediate updates are sent if fill levels
exceed action levels. The waste collection depots will see the bin fill levels on a daily basis and
use the Planning Route Tool to rapidly build customized collection routes to pick-up waste bins
that are full.
The host server and database in the Data Centre uses the Unified Computing System
compute, network and storage systems.
The Web Portal provides the following services:

 Provide pick up alerts to waste collection company based on bin fill levels
 Provide remote location of bins and the collection distances
 Update service information from waste collection companies

The Web portal in the Data Centre provides both live summary views of the status of all the
bins in a community. The waste bins community can include bins which are in a similar location
or bins that collect a similar type of material. The types of waste material can be solid waste,
recycled waste, medical waste or electronic waste. Clicking on a community brings up the live
fill level data for the community bins. The Google/GIS maps view gives a visual representation
of all the bins in a community and show the fill level as color-coded markers. So, at a glance,
a birds-eye view of all bins under management can allow intelligent decisions on deployment
of the waste collection fleet. The Web portal can be used to filter bins by fill level for collection
and then use Google Maps/GIS to build a collection route for the selected bins. The system
will then show the number of kilometres required to travel, how much material will be collected
and how much CO2 emissions will be used. To find out the status and collection history for a
specific bin, just click on a particular bin sensor. The Web portal makes it easy to manage the
bins, collection routes and see historical information on each bin.
The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network

© Dubai Design District, All rights reserved. Page 179 of 291

  Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Smart Dubai KPI

No KPIs defined for this service

5.3.6 Vehicle Tracking

[Link] Description
This service is referred to within the ESD document as the “Adaptive Traffic Control Solution
(C09)”. An adaptive traffic management allows for dynamic changing/adapting of the roadway
infrastructure, such as traffic signal timings, signage, and lane designations, to more efficiently
move vehicles within d3 depending changing traffic conditions. It provides the ability to respond
in real-time to changing traffic levels such as during rush hour and special events. Through
utilization of smart services district residents and visitors will be efficiently guided through key
areas within d3. The reduction of congestion wait times and carbon emissions increases resident
and visitor satisfaction
The solution leverages a combination of wireless vehicle tracking sensors (preferably using GPS
technology) active device tracking software and GIS data for locating tracked vehicles. The
Vehicle Tracking solution would allow for d3 CCC to be aware of and locate any designated
vehicles within d3 and. This solution can be bound by both geo boundaries and other d3
designated guidelines and should be integrated into the campus safety and security (ISS)
management platform. For d3 fleet the devices can be hardwired to the vehicle computer system
and shall support CAN (ISO 15765). For visitor or tenant or other delivery vehicles the tracking
system can be a mobile unit that can be handed over at the entrance gate. The device needs to
be handed over on the exit from the d3 community.

© Dubai Design District, All rights reserved. Page 180 of 291

 [Link] Functional Blocks

d3 & Command and Control

Geo-Location 3G/LTE or WiFI Center (CCC)
d3 IP Network

Typical Sensor or End Point Centralized Management

Figure 5-25: Vehicle Tracking Logical Architecture

[Link] Typical List of Parameters to be monitored

 Geo-Location of Vehicle

[Link] d3 IP Network Connectivity

For vehicle tracking the vehicle tracking device shall use any of the following methods of
communication:

 GSM/ 3G/ LTE

 City Wi-Fi

The end points or sensors within the vehicle shall be communicate with a vehicle management
system within the d3 data centre using standard protocols like TCP/IP, DHCP, FTP, HTTP,
HTTPS, NTP, RTP, RTSP, SMTP, SNMP, etc.

[Link] Centralized Management

Vehicle tracking device shall communicate to the Vehicle Management System in the d3 data
centre to enable management and operations of the services. The services can potentially need
to communicate with more than one application in the d3 data centre that are but not limited to
the following:

 Vehicle Management System

 Command and Control Server
 Data Virtualization Server
 GIS Server

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.

© Dubai Design District, All rights reserved. Page 181 of 291

  Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Smart Dubai KPI

No KPIs defined for this service

5.3.7 Electric Vehicle Charging Stations (EVCS)

[Link] Description
The electric vehicle power and charging initiative consists of installing charging stations for
electric vehicles in a few locations in d3. The electric vehicle power and charging stations will
encourage visitors, tenants and employees of d3 to use electric vehicles and to be more
environmentally friendly. Subject to approval and feasibility the initiative should integrate to (or
even extend) DEWA Services for Electric Vehicle Power and Charging.

[Link] Functional Blocks

Geo-Location

CCTV Camera d3 & or DEWA Command and

3G/LTE or WiFI
Router Control Center (CCC)
Smart Meter d3 IP Network

PoS + Payment Gateway Centralized Management

Typical Sensor or End Point

Figure 5-26: EVCS Logical Architecture

[Link] Typical List of Parameters to be monitored

 Geo-Location
 CCTV Camera
 Smart Meter
 PoS + Payment Gateway

[Link] d3 IP Network Connectivity

For EVCS all the endpoints shall connect using an IP gateway that shall have the capability to
connect to the d3 network and DEWA network using either wired network or wireless network.
The connectivity can be one or more of the following types:

 GSM/ 3G/ LTE

 City Wi-Fi

© Dubai Design District, All rights reserved. Page 182 of 291

  Smart City Fibre Network

The end points or sensors within the EVCS shall connect to the IP based router or gateway using
10/100/1000 PoE based Ethernet copper using Cat6 Cable and RJ45 Connectors. Some of the
sensors can also connect using the integrated Wi-Fi network on the Gateway.
The end points or sensors within the bus shelter shall be communicate with their respective
applications within the d3 data centre using standard protocols like TCP/IP, Bacnet/IP, Modbus
and DPN3. The devices shall also support protocols such as DHCP, FTP, HTTP, HTTPS, NTP,
RTP, RTSP, SMTP, SNMP, SSL / TSL. The devices shall support quality of service, minimum
DCSP.

[Link] Centralized Management

Different end points shall communicate to their respective application in the d3 CCC and or DEWA
operations centre to enable management and operations of the services defined for the electric
vehicle charging station. The services can be a combination of more than one application in the
d3 data centre that are but not limited to the following:

 LAN/ WAN/ Wi-Fi/ Security Management Server

 CCTV Management Server
 d3 Command and Control Server
 DEWA IP Network
 Data Virtualization Server
 GIS Server

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Smart Dubai KPI

Smart Dubai KPIs d3 Interpretation of the KPI
I2.2.2 Level of industrial electricity usage (per Number of ICT energy enabled Sensors
GDP) with ICT measures and Smart Meters connected to the d3
CCC
Count by ratio of average industrial electricity
(including charging electricity driven vehicles)

© Dubai Design District, All rights reserved. Page 183 of 291

 Consumption saved this year compared with
last year
I2.2.5 Level of fossil fuel usage with ICT Provision of ICT enabled fossil fuel
measures (per GDP) sensors connected to the d3 CCC
Count by ratio of average industrial fossil fuel
consumption saved this year compared with
last year
I4.1.4 Convenience of smart traffic information Provision of ICT enabled traffic sensors
administration and service connected to the d3 CCC and conducting
satisfaction surveys
Count by ratio of convenience expression
about smart traffic in paper/online interview
I5.3.2 Appliance of smart community services Number of ICT enabled Smart Community
count by ratio of communities that is assisted Services connected to the d3 CCC
with smart community services
I6.2.1 Coverage of installation of road sensing Provision of ICT enabled road sensors
terminals connected to the d3 CCC
Count by number of road sensors per
kilometre in overall urban road coverage
Table 5-21: EVCS KPI Interpretation

© Dubai Design District, All rights reserved. Page 184 of 291

 5.3.8 Bus Shelter
[Link] Description
Bus Shelters can be used as hubs for information sharing and social interaction in addition of
being connected to the urban commuting and travel network. This Smart Bus Shelters Initiative
will extend services to passengers and overall d3 tenants to include enhanced accessibility and
comfort, safety and security, improved user experience by providing free Internet, and local area
integration including interactive signage with timetable information at bus stops, road conditions,
traffic conditions and other relevant city data .

[Link] Functional Blocks

Geo-Location

CCTV Camera

3G/LTE or WiFI d3 Command and Control

Interactive Digital Sign Center (CCC)
Router
d3 IP Network
Light Control
Centralized Management
HVAC Control

Typical Sensor or End Point

Figure 5-27: Bus Shelter Logical Architecture

[Link] Typical List of Sensors and or End Points to be monitored

 Geo-Location
 CCTV Camera
 Interactive Digital Sign
 Light Control Device
 HVAC Control Device

[Link] d3 IP Network Connectivity

For bus shelters all the endpoints shall connect using an IP gateway that shall have the capability
to connect to the d3 network using either wired network or wireless network. The connectivity can
be one or more of the following types:

 GSM/ 3G/ LTE

 City Wi-Fi
 Smart City Fibre Network

The end points or sensors within the bus shelter shall connect to the IP based router or gateway
using 10/100/1000 PoE based Ethernet copper using Cat6 Cable and RJ45 Connectors. Some
of the sensors can also connect using the integrated Wi-Fi network on the Gateway. The
passengers can also use the d3 Wi-Fi Network on their mobile device.
The end points or sensors within the bus shelter shall be communicate with their respective
applications within the d3 data centre using standard protocols like TCP/IP, Bacnet/IP, Modbus
and DPN3. The devices shall also support protocols such as DHCP, FTP, HTTP, HTTPS, NTP,

© Dubai Design District, All rights reserved. Page 185 of 291

 RTP, RTSP, SMTP, SNMP, SSL / TSL. The devices shall support quality of service, minimum
DCSP.

[Link] Centralized Management

Different end points shall communicate to their respective application in the d3 data centre to
enable management and operations of the services defined for the bus shelter. The services can
be a combination of more than one application in the d3 data centre that are but not limited to the
following:

 LAN/ WAN/ Wi-Fi/ Security Management Server

 Digital Signage Manager
 CCTV Management Server
 Central BMS and or iBMS Server
 Command and Control Server
 Data Virtualization Server
 GIS Server

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

[Link] Smart Dubai KPI

No KPIs defined for this service.

5.3.9 Advanced Parking Management

[Link] Description
Advanced Parking Management will be deployed in d3 public parking areas and outside the
buildings. d3 visitors, tenants and employees can use the advanced parking management to
easily find an available parking spot and to pay for their usage. The sensors will detect free
parking spots. Correlation of sensors will enable the generation of meter violations.

© Dubai Design District, All rights reserved. Page 186 of 291

 [Link] Functional Blocks

Figure 5-28: Advanced Parking Management Logical Architecture

[Link] Typical List of Sensors and or End Points to be monitored

 Sensors on parking spots
 New generation parking meters
 Video camera with analytics

[Link] d3 IP Network Connectivity

For advanced parking management all the endpoints shall connect using an IP gateway that shall
have the capability to connect to the d3 network using either wired network or wireless network.
The connectivity can be one or more of the following types:

 GSM/ 3G/ LTE

 City Wi-Fi
 Smart City Fibre Network

The end points or sensors from the advanced parking management shall connect to the IP based
router or gateway using 10/100/1000 PoE based Ethernet copper using Cat6 Cable and RJ45
Connectors. Some of the sensors can also connect using the integrated Wi-Fi network on the
Gateway. The passengers can also use the d3 Wi-Fi Network on their mobile device to find a
parking spot and get a turn-by-turn guidance to the available parking spot.
The end points or sensors from the advanced parking management shall communicate with their
respective applications within the d3 data centre using standard protocols like TCP/IP, Bacnet/IP,
Modbus and DPN3. The devices shall also support protocols such as DHCP, FTP, HTTP, HTTPS,
NTP, RTP, RTSP, SMTP, SNMP, SSL / TSL. The devices shall support quality of service,
minimum DCSP.

[Link] Centralized Management

Different end points shall communicate to their respective application in the d3 data centre to
enable management and operations of the services defined for the advanced parking
management. The services can be a combination of more than one application in the d3 data
centre that are but not limited to the following:

 LAN/ WAN/ Wi-Fi/ Security Management Server

© Dubai Design District, All rights reserved. Page 187 of 291

  Digital Signage Manager
 CCTV Management Server
 Command and Control Server
 Data Virtualization Server
 GIS Server

The system that will be procured from third party vendors shall follow the below guideline:

 Get secure connectivity to the d3 network

 Open ports to the API Management Server
 Expose/Publish key APIs required by the d3 network
 Have Extensible Markup Language (XML) APIs
 Have Representational State Transfer (RESTful) APIs
 Have Simple Object Access Protocol (SOAP) APIs
 Have JavaScript Object Notation (JSON) APIs.
 Open its ports to the Data Virtualization Server using:
o RDBMS
o NoSQL databases
o Web Services
o Big Data (Hadoop)
o JMS messaging, etc…
 Have the right interface to integrate with the d3 service enablement layer, to be
defined at a later stage

Smart Dubai KPI

Smart Dubai KPIs d3 Interpretation of the KPI
I1.2.3 Proportion of business based on GIS Number of businesses using ICT
(location, navigation etc.) methods that include CAD/GIS and
Count by ratio of social, governance and connected to the d3 CCC
enterprise businesses that utilize GIS based
services
I6.2.2 Coverage of parking guidance Provision of ICT enabled parking
systems Count by ratio of parking lots under sensors connected to the d3 CCC
automatic guidance
I3.1.8Improvement of traditional industry
with ICT count by ratio of GDP improvement
due to technology upgrade
Table 5-22: Smart Dubai KPI's for Advanced Parking Management

5.3.10 Miscellaneous Services

To ensure accessibility, it is recommended to additionally provide the following:

 Hi Tech Community centres within parks to increase community contact and interaction
particularly during times when meeting and interacting in the open is not feasible due to
weather conditions.
 Self-operated and monitored wheel chairs for elderly and people with special needs in
parks and retail areas.

© Dubai Design District, All rights reserved. Page 188 of 291

  Remote education and learning and remote medicine for people including people with
special needs using technology

6 ICT Network Infrastructure guidelines

for d3
One key requirement of any Smart City is a robust and converged IP Network, both within the
building and outside in public areas of the City. The Network Components refer to specific
Network Devices and their connectivity. Keeping in view the Smart Services and the size of the
buildings it is strongly recommended to build a hierarchical network design, borderless and a
media ready network as detailed in the following sections. The proposed network needs to be
built on the principles of Campus Ethernet and Carrier Ethernet. It must have the resilience of the
Campus Ethernet and the service capability of the Carrier Ethernet.

6.1 Hierarchical Design guideline

The architecture of the network for a Smart building should be a hierarchical design laid out in
different layers as follows:

 Core
 Distribution
 Access

This hierarchical model shall help d3 to design a modular network topology using scalable
“building blocks” that allow the network to meet evolving business needs. The modular design
makes the network easy to scale, understand, and troubleshoot by promoting deterministic traffic
patterns. The building blocks of a highly available network are the access layer, the distribution
layer and the core (backbone) layer.

Figure 6-1: Hierarchical Design Model

The principal advantages of this model are its hierarchical structure and its modularity. In a
hierarchical design, the capacity features, and functionality of a specific device can be optimized
for its position in the network and the role that it plays. This promotes the scalability, stability, and

© Dubai Design District, All rights reserved. Page 189 of 291

 resiliency of the network. The number of flows and their associated bandwidth requirements
increase as they traverse points of aggregation and move up the hierarchy from access to core.
Functions are distributed at each layer.
A hierarchical design avoids the need for a fully-meshed network in which all network nodes are
interconnected. The building blocks of modular networks are easy to replicate, redesign, and
expand. There should be no need to redesign the whole network each time a module is added or
removed. Distinct building blocks can be put in-service and taken out-of-service without impacting
the rest of the network. This capability facilitates troubleshooting, problem isolation, and network
management.
The hierarchical design segregates the functions of the network into these separate building
blocks to provide availability, flexibility, scalability, and fault isolation.
The access layer of the network aggregates network end-points. It provides all the intelligent and
advanced services like Quality of Service, broadcast suppression, access security and spanning
tree features. It should also have the capability to provide power over Ethernet to end points like
Wireless Access Points, IP Cameras, access control end points and if possible to other building
automation end points like HVAC, Lighting and other controllers.

6.1.1 Design Considerations for d3 Network

The network infrastructure should ensure the following recruitments

 Scalability
 Flexibility
 Resiliency
 Availability
 Functional Segmentation
 Routing Protocol
 Quality of Service
 Multicast support

[Link] Scalability
Due the ever increasing business demands there can be future services added to this network.
As these services grow; so will the demands on the backbone network. The network must not
only be able to grow with these services, but ensure that existing services are not inhibited by the
addition of new ones.
The Core and Distribution devices should be chassis based design with dual processor having
either centralized or distributed processing. These devices should be 50-60% populated to cater
to the current needs leaving the remaining 40-50% for future growth.
Access switches should be modular in case more than 96 ports are required per IDF room.

[Link] Flexibility
The network should be flexible enough to accommodate changes as the network evolves in due
course of time. These changes can be planned or unplanned driven by the ever changing need
of user applications. This additional need can arise from the following:

 Additional Bandwidth
 Additional Ports or Slots
 Additional Features

© Dubai Design District, All rights reserved. Page 190 of 291

 Each network device as such should have the capability to satisfy these needs either within the
device itself or by seamless addition of capacity or change of software.

[Link] Resiliency
Resiliency should be built at every layer of the entire network. This includes redundant
connectivity and redundant modules.
The core layer should have redundancy at the chassis level. Each distribution router should be
connected to both core routers to maintain the link redundancy as. To provide backbone resiliency
at building level, it is recommended that one core device is physically placed in different MDF
rooms and preferably in different buildings. The core devices should be fully mesh connected to
the distribution devices using 10G uplinks.
More than one pair of distribution devices should be used in case the number of access switches
is large. The exact number of distribution pairs can only be advised after getting more details of
the building demographics or building space planning. Each distribution device pair should be
split the same way as the core (one in each MDF room).
The floor access switches in each floor IDF rooms shall have dual 10Gbps or 1Gbps uplinks
connected to two different distribution switches. The choice of bandwidth should be made on the
basis of the port density.
The proposed network carries delay sensitive services like voice and video. The maximum
acceptable round trip delay for a voice call and video conferencing should not exceed 150ms.
All the uplinks should be designed to work in active-active mode. Fast convergence techniques
that should be deployed in the network are listed below:

 Fast spanning tree convergence – 802.1s

 Per VLAN Rapid Spanning Tree
 Features like HSRP/VRRP for fast convergence for redundant gateways
 Fast convergence of routing protocol based on active-active topology
 Stateful Switch Over and Non Stop Forwarding
 Bidirectional Forwarding Detection

[Link] Availability
Availability would depend on many factors as given below (but this is not an exhaustive list):

 Failure of the Active components: This will be covered by redundant modules at every
level; starting from the access towards the core. All access, distribution and core devices
should have redundant processor engines. All the access devices should have dual
uplinks from different modules to the relevant distribution block.
 System-level redundancy: This shall be achieved using redundant routing or switching
processor engines and redundant power supplies. This provides high-availability for
critical applications and services
 Bundling technologies: Provides link redundancy techniques like Ether-Channel on
1Gbps or 10Gbps ports
 Loop Free Network Connectivity: The Network devices should support IEEE 802.1d,
802.1s, 802.1w protocol support. Should there be a need to run spanning tree,
advanced spanning-tree features should be available. Other additional variations which
will enhance the convergence time and ensure Loop-free topologies.

© Dubai Design District, All rights reserved. Page 191 of 291

 All core and distribution devices except the access / floor switches shall be running on Layer 3
and core routing protocol is recommended to be OSPF. By setting up sub-second tuning
parameters such as throttle timers and fast hellos, sub-second convergence can be achieved.
All core, distribution and WAN (Remote offices if any) devices should be connected using different
fibre run to ensure that physical damage to the fibre cable does not disrupt the services.

[Link] Functional Segmentation

Distinct Functional blocks like Data Centre, WAN and Internet should be connected to the core
as shown in the figure below. All interconnecting links are recommended to be 10Gbps links.

Figure 6-2: Functional Segmentation of the Converged Network

The figures below show the connectivity and the uplink utilization that the building should follow
in different areas of the network. The illustrations below identify the subscription ratios to ensure
high performance and response to every application or traffic pattern on the network. These
subscription ratios are only for illustration and will be detailed in the final High Level Design
document based on the actual requirements of the building.

© Dubai Design District, All rights reserved. Page 192 of 291

 Figure 6-3: Uplink Connectivity for a 10/100/1000 port connected to the end point

Figure 6-4: Uplink connectivity for the Data Centre Device Connectivity

© Dubai Design District, All rights reserved. Page 193 of 291

 [Link] Routing Protocol
OSPF is proposed as the Routing protocol for the core and distribution segments using the
following considerations. The core and the distribution devices should support other routing
protocols like EIGRP etc. In case need arises for supporting L3 MPLS based VPNs the core and
distribution devices should support BGP. The OSPF Routing protocols allow a hierarchical
implementation where different areas can be created for core, distribution and other functional
blocks. This allows routing scalability and ensures easy troubleshooting. The use of OSPF will
ensure that it can be run over different media types. Features like route summarization can be
implanted on the distribution router for efficient routing design.

 Typically deployed in distribution-to-core, and core-to-core interconnections

 Used to quickly re-route around failed node/links while providing load balancing over
redundant paths
 Triangle type connectivity and not squares for deterministic convergence
 Only peer on links that you intend to use as transit
 Insure redundant L3 paths to avoid black holes
 Summarize distribution to core to limit OSPF LSA propagation
 Tune CEF L3/L4 load balancing hash to achieve maximum utilization of equal cost paths
(CEF polarization)

[Link] Quality of Service (QOS) Requirements

QoS is the measure of transmission quality and service availability of a network. Service
availability should be crucial foundation element of the building network QoS strategy. The
network infrastructure needs to be designed to be highly available before QoS can be
implemented successfully. The target for High Availability is 99.999% uptime in the core and
distribution segments, with only five minutes of downtime permitted per year particularly for
services pertaining to safety, security and building automation. 99.99% uptime is recommended
to be achieved on the access segment. While this figure is difficult to achieve using non redundant
or non-chassis based devices, distribution of access devices on more than once physical access
switch can help achieve higher uptime and avoid complete network or functionality outages.
The transmission quality of the network is determined by the following factors:

Loss - A relative measure of the number of packets that were not received compared to the
total number of packets transmitted. Loss is typically a function of availability. If the network is
Highly Available, then loss during periods of non-congestion would be essentially zero. During
periods of congestion, however, QoS mechanisms can determine which packets are more
suitable to be selectively dropped to alleviate the congestion.
Delay - The finite amount of time it takes a packet to reach the receiving endpoint after being
transmitted from the sending endpoint. In the case of voice, this is the amount of time it takes
for a sound to travel from the speaker’s mouth to a listener’s ear.
Delay variation (Jitter) - The difference in the end-to-end delay between packets. For example,
if one packet requires 100 ms to traverse the network from the source endpoint to the
destination endpoint and the following packet requires 125 ms to make the same trip, then the
delay variation is 25 ms.

The illustration below gives a view of different types of traffic patterns which the network will be
exposed to and their corresponding characteristics.

© Dubai Design District, All rights reserved. Page 194 of 291

 Figure 6-5: Traffic Patterns expected on the network
The following QOS Architecture is recommended for the Network.
Access switches require the following QoS policies:

 Appropriate (endpoint-dependent) trust policies, and/or classification and marking

policies
 Policing and markdown policies
 Queuing policies.

Distribution and core routers require the following QoS policies:

 DSCP trust policies

 Queuing policies

It is very important to note that the information provided herein are typical guidelines which need
to be finalized during the creation of the low level designs. The RFC 4594 Configuration guidelines
are shown below:

© Dubai Design District, All rights reserved. Page 195 of 291

 Figure 6-6: Marking Strategy
The possible queuing strategies that can be deployed at the time of implementation are shown
below:

Figure 6-7: 1P3Q8T Queue Structure

© Dubai Design District, All rights reserved. Page 196 of 291

 Figure 6-8: 1P7Q4T Queue Structure

6.1.2 Functions of the Access Layer

The access layer is the point at which local end users are allowed into the network. This layer
shall use access lists or filters to further optimize the needs of a particular set of users. The Access
layer devices should support 802.1q for VLAN and trunk implementations.
Access-layer functions should include the following:

 Switched bandwidth
 MAC layer filtering
 Micro segmentation
 Layer 2 Quality of Service functions
 Access Control Lists at the port level

© Dubai Design District, All rights reserved. Page 197 of 291

 Figure 6-9: Access Layer of Hierarchical Design Model

The layers are defined to aid successful network design and to represent functionality that must
exist in a network. The instantiation of each layer can be in distinct routers or switches, can be
represented by a physical media, can be combined in a single device, or can be omitted
altogether. The way the layers are implemented depends on the needs of the network being
designed. Note, however, that for a network to function optimally, hierarchy must be maintained.

[Link] Recommendations for d3

The access layer in d3 shall provide port connectivity to the end endpoints for the Smart City
services. Based on the current site situation, the access layer shall provide the connectivity to the

 Indoor and Outdoor Wireless Access points

 BMS system endpoints
 EnergyWise
 Kiosks
 Digital Signage

The same access network shall be able to scale to provide the access level connectivity to the,
Smart Workspaces and other Smart services including but not limited to the 45 Smart City
Services listed in the Services Catalogue of d3.
It is recommended that 24 port x 1 Gbps PoE switches should be placed in each floor to provide
the access connectivity and power to end devices like digital media players, wireless access
points, cameras etc.
However to save on the capex for access switches, connectivity to three floors can be provided
from one floor. This means that the access switches will be placed in the IDF of a floor and it shall

© Dubai Design District, All rights reserved. Page 198 of 291

 be provided access connectivity to the floor above and below it, including the floor where the IDF
is. This will however increase the horizontal cable runs and it should be kept in mind that the
longest distance from the IDF to the endpoints should not exceed a distance of 90 meter.
It is recommended that the access switches should have a minimum uplink capacity of 1Gbps.
However the switches should be ready to accommodate an uplink connectivity of 10 Gbps without
going through a fork lift upgrade.
It is recommended that the uplink bandwidth calculation should be done considering the full
capacity of the access switch and an oversubscription ratio of 1:15 should be applied.

6.1.3 Function of the Distribution Layer

The distribution layer of the network is the demarcation point between the access and core layers.
The purpose of this layer is to provide boundary definition and is the place at which packet
manipulation can take place.
Availability, load balancing, QoS and provisioning are the important considerations at this layer.
Some of the salient features of distribution layer include:

 Aggregates wiring closes (access layer) and uplinks to core

 Protects core from high density peering and problems in access layer
 Route summarization, fast convergence, redundant path load sharing
 Protocol support to provide first hop redundancy
 The distribution layer can be summarized as the layer that provides policy-based
connectivity

Figure 6-10: Distribution Layer of Hierarchical Design Model

© Dubai Design District, All rights reserved. Page 199 of 291

 The distribution block provides policy enforcement and access control, route aggregation, and
the demarcation between the Layer 2 subnet (VLAN) and the rest of the Layer 3 routed network.
The distribution block within the network shall use a combination of Layer 2 and Layer 3 switching
to provide for the appropriate balance of policy and access controls, route summarization,
availability, and flexibility in subnet allocation and VLAN usage.

[Link] Recommendation for d3

The distribution layer in d3 shall serve as an aggregation point to consolidate the access switches
on one side and for establishing the connectivity to the core switches.
It is recommended that the distribution switches be placed in the MDF of each building. All the
uplinks from the access switches in the building shall consolidate in this distribution switch.
d3 can use one of the two following methods for connecting the distribution layer with the access
and the core layers. The distribution layer must be capable of supporting the MPLS functionality
It is assumed that each building shall on an average generate 7Gbps of traffic into the distribution
layer via its uplinks. Limiting 4 to 5 buildings in one ring means 35 Gbps traffic within the ring on
an average. Applying a 1:5 over subscription 7 Gbps traffic is expected to be running between
the distribution and the core layer on an average.

[Link].1 Option 1: Block aggregation method

This method is the recommended option and it is hinged on the fact that multiple buildings within
the block ranging from 4 to 5 buildings use one building to aggregate the buildings of the block.
This option necessitates that the access vertical backbone fibre from the buildings can be
extended to the block MTR. It implies that enough fibre capacity is made available between the
MTRs of each building to the MTR of the block aggregation building. Cross Connect facility must
be provided in the MTRs to support the concept. Figure 6-11 below provides a view of this
connectivity option. To reduce the capex, block wise distribution can also be considered. All the
building in one block shall have a common distribution layer. The block aggregation switch also
provides connectivity to the Smart Services Endpoints in the public areas outside the building.

Figure 6-11 Block Aggregation method of connecting access to distribution switches

© Dubai Design District, All rights reserved. Page 200 of 291

 [Link].2 Option 1: Building aggregation method

Figure 6-12: Building Aggregation method of connecting access to distribution switches

This option demands that a dedicated distribution is available in the MTR of each building. For
providing connectivity to the access layer for the public areas dedicated distribution switches are
placed in the Primary or Secondary PoP. This will provide d3 with operational flexibility to manage
and operate the network.
It is recommended that the connectivity between the distribution layer and the core layer should
be based on 10 Gbps uplinks. To calculate the number of uplinks for bandwidth calculation of the
uplinks, an oversubscription ratio of 1:5 should be considered with a buffer of 40% for future
growth. Each ring should accommodate 4 to 5 distribution switches to ensure meeting the desired
performance levels.

6.1.4 Function of the Core Layer

The core layer is a high-speed switching backbone and should be designed to switch packets as
fast as possible. This layer of the network should not perform any packet manipulation, such as
access lists and filtering that would slow down the switching of packets.

© Dubai Design District, All rights reserved. Page 201 of 291

 Figure 6-13: Core Layer of Hierarchical Design Mode
The core layer includes several functions such as the following: Backbone for the network -
connects network building blocks

 Performance and stability vs. complexity ( less is more in the core)

 Aggregation point for distribution layer
 Separate core layer helps in scalability during future growth
 Keep the design technology-independent

The core and aggregation layers of the network provide high capacity transport between the
attached building blocks. The core layer of the network should use Layer 3 routing to provide the
necessary scalability, load sharing, fast convergence, and high speed capacity.

[Link] Recommendations for d3

It is recommended that core switches be places within the Primary PoP of d3. The Core switches
should have a high density of 10 Gbps ports so that all the uplinks from the distribution switches
aggregate at the core. The core should support the MPLS functionality. The core should be
connected to the Data Centre Core Switches either using a direct fibre link or using MPLS links
in case the Data Centre is not present within d3.

© Dubai Design District, All rights reserved. Page 202 of 291

 6.1.5 d3 Smart City Data Centre concept design
The Smart Services Data Centre shall be designed on tiered data centre architecture having a
core, distribution and access layer. The Figure 6-14 below provides a segmented view based of
the d3 Data Centre functionality.

Figure 6-14: d3 Data Centre Functional Segmentation

The Figure 6-15 shows a logical view of the above concept. It is very clear that the segregation
of different functional blocks like Production, Testing, DMZ and Network Management needs to
be achieved either by building physically different blocks or by making use of virtualization in the
Aggregation block to provide the same type of segmentation. This segmentation will allow d3 to
apply different Security, Network management and QoS policies to ensure that the different
segments can be treated with a very specific and stringent policy. This type of segmentation will
also allow d3 to manage and operate the network infrastructure better at the time of applying
changes or modifications to the network infrastructure. This way better uptime figures can be
achieved. It is recommended that the Test and Development and DMZ functions have separate
aggregation and access switches. This will enable the d3 staff to make changes and conduct
tests during work hours without disrupting the production environment. Alternatively this
functionality can also be achieved through virtualization of Network, Security, Storage and
Compute.

© Dubai Design District, All rights reserved. Page 203 of 291

 Figure 6-15: A Logical View of the Data Centre Network Infrastructure
Figure 6-15 shows the High level design for the d3 network Infrastructure. It clearly identifies the
layers of the DC infrastructure connectivity. The Access devices are not show as per the actual
number. The figure clearly shows how the campus network and the partner networks will connect
to the data centre.
This high level design also shows how the Group IP network will connect to the d3 Smart City
Network as some applications will need to be connected together for sharing data to the Data
Virtualization Network.

© Dubai Design District, All rights reserved. Page 204 of 291

 Figure 6-16: d3 High Level Network Design

[Link] Recommendation for d3

Based on the proposed Smart Services for d3 for the next seven to ten years it is assumed to
occupy at least 20 Racks within the Data Centre Computer Room. To build a Tier 3 Data Centre
it will require at least a 100 Sq. m. space that would include the computer room and the ancillary

© Dubai Design District, All rights reserved. Page 205 of 291

 spaces for the Data Centre. The total power required for operating such a Data Centre is
approximately 240 kW. For connectivity with Internet and Intranet two links each of 50 Mbps and
100 Mbps is proposed to be requested from two local service providers to meet the day one need.
Additional capacity can be added on a need basis as and when it is required.
Alternatively d3 can lease space from any Commercial Data Centre to provide Smart Services
within the district. In this case the number of racks can be added on demand basis.

6.1.6 Wireless Network

The wireless network shall be part of the building IP Network Architecture. The users of the
building wireless LAN shall require the same accessibility, security, quality-of-service (QoS), and
high availability that is enjoyed by wired users. In addition to users, services such as RFID,
parking control and direction finding could also be using the Wireless LAN. The diagram in figure
below gives a high level view of Mobility Architecture that the Wireless LAN brings. At the top of
the architecture are the applications that run on the Mobility platform using Wireless LAN. Most
of the applications will be needed by the building for its common areas etc. The Mobility services
that run on the Wireless LAN are the cornerstone of the Wireless Network. In addition to voice
and guest access, services such as Context Aware (for Location Based Services), mobile
intelligent roaming can also be deployed using Wireless LAN.
Network access elements of the Architecture use open protocols that carry the services for the
applications that will be deployed.

Figure 6-17: Mobility High Level Architecture

The ability to provide services any time anywhere for its visitors and customers, the building
Wireless LAN brings in added value to its portfolio by providing the following advantages:

© Dubai Design District, All rights reserved. Page 206 of 291

  Mobility within building — which facilitates implementation of applications that require an
always-on network and that tend to involve movement within the building environment
such as Active RFID for asset tracking facility particularly within the retail areas.
 Convenience — which simplifies networking of large, open access areas such as main
lobby, sky lobbies and the mall areas.
 Flexibility— allows work to be done at the most appropriate or convenient place rather
than where a cable drop terminates such as the main lobby, sky lobbies and the mall
areas.
 Easier to set-up within temporary spaces or the meeting room areas.
 Easier adds, moves, and changes and lower support and maintenance costs — allows
temporary networks become much easier to set up, easing migration issues and
reducing costly last-minute fixes.
 Productivity gains —Visitors and employees spend more time using the network rather
than looking for network availability.
 Easier to collaborate — Facilitates access to collaboration tools from any location, such
as meeting rooms; files can be shared on the spot and requests for information handled
immediately.
 More efficient use of space — allows greater flexibility for accommodating groups, such
as e- book in the library.

[Link] WLAN Functional Requirements

The requirements for the building Wireless LAN have to be the same as its wired network. WLANs
must permit secure, encrypted, authorized communication with access to data, communication,
and business services as if connected to the resources by wire. The WLANs must be able to do
the following:

 Maintain accessibility to resources while the building users are not wired to the network
 Secure the network from unauthorized, unsecured, or "rogue" WLAN access points.
 Extend the full benefits of integrated network services to mobile users— Services such
as VoIP, video CAM and data.
 Segment authorized users and block unauthorized users—The WLAN must be able to
configure support for a separate public network, a guest network, VIP network or staff
network.
 Easily manage central or remote access points. The ability for the Network Operations
Centre (NOC) to be able to easily deploy, operate, and manage the access points within
the building.
 Enhanced Security Services—the service should be able to provide WLAN Intrusion
Prevention System (IPS) and Intrusion Detection System (IDS) control to contain
wireless threats, enforce security policy compliance, and safeguard the information.
 Voice Services—the mobility and flexibility of wireless networking should be able to
support voice services.
 Location Services — Simultaneous tracking of Wi-Fi and active RFID devices from
within the WLAN infrastructure for critical applications such as high-value asset tracking,
ICT management, location-based security, and business policy enforcement.
 Guest Access— provides building visitors, customer, and partners with easy access to a
wired and wireless LANs.

[Link] WLAN Security Requirements

The mobile network clients need to be protected on all interfaces at all locations. The security
policy should be similar to wired network to avoid duplication of any security parameters. The

© Dubai Design District, All rights reserved. Page 207 of 291

 security can be based on the industry standards as defined by IEEE, IETF and Wireless Alliance
Consortium. Security contribution from each entity of the organization is described further below:

 IEEE-The IEEE defines the 802.11 group of standards. Amendments were made to
802.11 requirements published in 1999 include adding physical layer implementations
and providing greater bit rates (802.11b, 802.11a, and 802.11g), adding QoS
enhancements (802.11e), and adding security enhancements (802.11i). The IEEE also
defines the 802.1X standard for port security, which is used in 802.11i for authentication
of WLAN clients.
 IETF -The main IETF RFCs and drafts associated with 802.11 are based on EAP. The
advantage of EAP is that it decouples the authentication protocol from its transport. EAP
can be carried in 802.1X frames, PPP frames, UDP packets, or RADIUS sessions. In
802.11 networks, EAP is transported across the WLAN in 802.1X frames and from the
Wireless LAN Controller (WLC) to the Authentication, Authorization, and Accounting
(AAA) server in the RADIUS protocol, thus providing end-to-end EAP authentication
between the WLAN client and the AAA server.
 Wi-Fi Alliance-The Wi-Fi Alliance is an industry body that certifies WLAN device
interoperability through its Wi-Fi, Wi-Fi Protected Access (WPA), Wi-Fi Protected Access
2 (WPA2), and Wi-Fi Multimedia (WMM) certification programs.

The WPA standard was developed to address the weakness in the WEP encryption process,
which existed before the ratification of the 802.11i workgroup standard. One of the key goals in
the development of WPA was to ensure backward compatibility with WEP-based hardware. To
that end, the WPA standard still uses the base RC4 encryption method used in WEP, but adds
keying enhancements and message integrity check improvements to address the weaknesses in
WEP.
WPA2 is based on the ratified 802.11i standard and uses Advanced Encryption Standard-
Counter Mode with Cipher Block Chaining Message Authentication Code Protocol (AES CCMP)
encryption at its core. WPA2 requires new client and AP hardware. Given current upgrade cycles
for laptops and other client devices, it can be expected that a mixture of WPA and WPA2
environments will co-exist for some time. In a green field enterprise deployment like SEC, WPA2
shall be deployed from the start.

 WEP and Cipher Suites

 Wi-Fi Protected Access
 TKIP
 IEEE 802.1x

[Link] Wireless Network Components

WLANs consist of multiple elements and behaviours, which make up the foundation of the 802.11
protocol. A key part of the protocol discovers the appropriate WLAN and establishes a connection
with that WLAN. The primary components of this process are as follows:

 Beacons—Used by the WLAN network to advertise its presence

 Probes—Used by WLAN clients to find their networks
 Authentication—An artefact from the original 802.11 standard
 Association—Establishes the data link between an AP and a WLAN client

The Wireless LAN should broadcast its service set identifier (SSID) to the users of the Wi-Fi
network. The SSID should be unique and it should not give any indication of what type of network
and whose network the user is associated with.

© Dubai Design District, All rights reserved. Page 208 of 291

 6.2 IP Network Management
The fact that the IP network is going to be a central piece to the communications and automation
within the building it becomes necessary that proper Operations and Network Management
(ONM) infrastructure is put in place so that the configuration, trouble shooting and performance
monitoring is achieved resulting in enhanced customer satisfaction and high levels of productivity.
The Network management also provides a view into to the network to manage the network
proactively in addition to the reactive demands.

6.2.1 The ONM Motivators

As d3 is a new development, a number of motivators become relevant to build its ONM
infrastructure. Some of these drivers are listed below:

 Integrated, Scalable and Industry Best Practice based ONM Architecture

 Operational costs savings through automation and reduction of manual processes
 Improved Customer Satisfaction
 Improved Fault response times
 Unified Operations environment
 Long Term consolidated ONM systems strategy
 Greater flexibility
 High Availability and Resiliency

6.2.2 ONM Blueprint Design Goals

The proposed architecture addresses a number of design goals, chief amongst these are the
following:

 Support ICT department which would help create a unique user experience for its
visitors and employees.
 Support the ability to consolidate and correlate events across the infrastructure
 Support the ability to identify root cause of problems across the infrastructure
 Support the ability of a centralized support function to address performance issues
 Improving level of granularity at which traffic flows within the network infrastructure can
be viewed.
 Support the move to policy based networking with a management solution that controls
change and highlights policy compliance issues.
 Support the delegation of key network support tasks to first line resolution by Helpdesk
resources

6.2.3 The ONM Functional Architecture

For d3 there is a need to have an Operations and Network Management function which will enable
it be agile and add new features and functionality to meet the needs of its Users and Visitors. The
functional architecture is shown in the figure below. It shows the functional Operations and
Network Management (ONM) products that should constitute the ONM Blueprint to operate and
manage its converged network. These ONM functions are mapped to the enhanced Telecom
Applications Map (TAM) Framework to show the general functionality being covered.

© Dubai Design District, All rights reserved. Page 209 of 291

 Figure 6-18: ONM Functional Blueprint

6.2.4 NMS Components, Features and Functions

[Link] Domain Management
[Link].1 Overview
Resource Domain Management is the application area that provides the exposed resource
services that are available to all other application areas, including those others in the Resource
Management layer.
Domain Management’s role is to hide the idiosyncrasies and shortcomings of the Network, ICT
computing, ICT and building automation applications equipment from the rest of the OSS estate,
freeing it to be agile. This is particularly important as providers install lots of new, untried
equipment with early release Element Management software.

[Link].2 Building Management Systems

Integrating building systems into the network infrastructure also entails integrating the traditional
building management systems that control a wide array of the building’s systems (such as
heating, cooling, lighting, various sensors, fire, and safety) into the overall Operations and
Network management Architecture.
The value of this integration is in enabling a unified and consistent operations strategy as well as
allowing the use of the flexible and scalable ONM infrastructure to manage the building resources.
This integration as part of the overall ONM architecture is achieved by considering the BMS
systems as Domain managers. As defined above, the role of the domain managers is to hide the
complexity and vendor-specificity of the communication with the managed resources from the

© Dubai Design District, All rights reserved. Page 210 of 291

 rest of the ONM infrastructure. Domain Managers handle fault, monitoring and configuration in
their domain. Hence, services enabled by the building systems will be considered like any other
service enabled by SEC’s infrastructure. It will not differ from an operation and management
perspective from the other ICT services.
BMS systems need to be chosen carefully with respect to their integration capabilities. Some
aspects to consider are Off-The-Shelf integration capabilities, APIs availability (for example
JAVA, XML, CRBA and SOAP), SNMP and SYSLOG support.

[Link].3 Functionality
The Resource Domain Management applications are responsible for providing a completely
encapsulated interface to network technology domains by:

 Hiding vendor specific idiosyncrasies through the use of template mechanisms.

 Providing in-domain activation.
 Providing in-domain alarm collection, filtering (and non-data based correlation)
to supplement that done by Correlation & Root Cause Analysis.
 Providing in-domain QoS activation.
 Providing in-domain inventory discovery to supplement that done by Resource Inventory
Management.
 Containing limited distributed copies of logical network inventory sufficient to
support atomic operation rollback, element manager selection and network auto-
discovery.

[Link] Configuration Management Application

[Link].1 Overview
Applications in this area manage the provisioning and configuration of resources required
for services. This would include the ICT and the building management systems

[Link].2 Functionality
Typical functions include:

 Configuration of the physical and logical resource (network element or component,

ICT system, application, building automation systems or other entities defined within
systems)
 Management of the resource activation or deactivation
 Interface with NE or EMS or BMS or other provisioning or activation application
 Management of resource properties, including changes in characteristics
 Maintaining up-to-date status of resources in Resource Inventory applications
 Maintain resource state and topology
 Interface to Workforce or Workflow applications
 Control of the manual provisioning tasks possibly via Workforce Management
application
 Update the resource to activate Billing data collection if required for a particular service
or services
 Notify Resource Provision / Control of the activation status
 Update Resource Inventory with the resource status information
 Queued / scheduled activation requests
 Configuration validation and rollback

© Dubai Design District, All rights reserved. Page 211 of 291

  Manage dependencies within, and across network elements through rules
 Multi-vendor and multi-technology activation
 Multiple NE activation coordination
 Confirm / identify available resources

[Link] Performance Management Application

[Link].1 Overview
Traditionally, the management of network resources has been geared to managing the
technology that supports the network - monitoring events. With multi-service networks it will be
managed according to the services being delivered across the network - monitored on service
levels.
As the services and the network infrastructure that supports them become more complex,
automation of the data analysis is required.

[Link].2 Functionality
Applications that support Performance Management will have one or more of the following
capabilities:

 Resource Performance data collection

 Resource Topology Status data collection
 Business rules / formulae / KPIs, KQIs
 Reporting on Groups based on heterogeneous Network Objects
 Service Performance Reporting
 Long-term performance archive
 Short-term performance repository
 Input to capacity planning applications
 Input to resource problem management applications
 Historical trending
 Problem identification: Capacity, Configuration problem identification
 Problem triage / testing
 Utilization trending and forecasting
 Resource Performance “dashboard”
 Service Performance “dashboard”

[Link] Service Control Platform

[Link].1 Overview
The Service Control Platform enables the ICT / Facility service provider or providers to analyse,
charge for, and control IP network traffic at multi-gigabit wire line speeds. It also gives them the
tools they need to provide tiered (differentiated) services for different types of users both internal
and external including but not limited to classes of service, grades of service for different user
types. These capabilities are essential for transforming the network from an aggregation of
bandwidth pipes to an intelligent network that enables offering advanced and premium services
for creating new revenue sources. This should include services that are created either
independently by ICT, Telecom or Building Management Systems or by a combination of one or
more such systems.
This solution ensures that the provider can move beyond best effort services and guarantee
performance of quality of service (QoS) sensitive IP applications such as Voice-over-IP (VoIP),

© Dubai Design District, All rights reserved. Page 212 of 291

 IPTV and Video-on-Demand (VoD) and other critical building management systems like CCTV
and Access Control.

[Link].2 Functionality

 Deep Packet Inspection (DPI) up to layer-7

 Classification of traffic based on IP protocol, TCP and UDP port
 Classification of traffic based on layer-7 signatures regardless of port numbers
 Sampling and reporting on network activities
 Creation of frequent/real-time usage-export for selected sub-set of subscribers and long-
period reports for all subscribers
 Centralized data collection and management by exporting required information to a
central source for storage and reporting
 Control of traffic based on originating and destination IP address, destination port,
protocol and application (e.g. VoIP is combination of protocols such as SIP, SDP and
RTP)
 Enforcement of a different policy or set of policies on different subscribers, depending on
the nature of the services selected
 Enforcement of bandwidth limits, guarantees and priorities on different
services/protocols of an individual subscriber
 Ability to assign different policies to traffic from different sub-net & IP-ranges
 Maintain usage quotas across multiple subscriber sessions
 Support for automatic subscriber management via AAA integration

© Dubai Design District, All rights reserved. Page 213 of 291

 6.3 IP Network Security
Once a shared packed network is deployed it becomes important to ensure proper security. The
Security solution for any IP network has more of an operational or policy perspective rather than
one of a product. Like network management, the philosophy is one that addresses a dynamic,
process towards security and keeps evolving and changing on a periodic basis to mitigate any
risk that may arise sooner or later.
The Security Wheel is cyclical, ensuring diligence and improvement. The paradigm incorporates
the following five steps:

 Develop a strong security policy

 Secure the network
 Monitor the network and respond to attacks
 Test existing security safeguards
 Manage and improve corporate security

Data gained from steps 2 through 5 should always be reflected back to the corporate security
policy in step 1. This will ensure high-level security expectations are being met.

Figure 6-19: Security Process Wheel

6.3.1 Developing a Strong Security Policy

Consideration of the following is crucial in developing a strong security policy for any IP network:

 What assets must be protected?

 What is the risk to those assets?
 What is the impact (in terms of reputation, revenues, profits, research) of a
successful attack?
 How much sensitive information is available online? What is the impact if this information
is damaged or stolen?
 Which users have access to those assets?
 What do users (including partners and customers) expect in terms of security
control procedures and mechanisms?
 Should users be trusted?

© Dubai Design District, All rights reserved. Page 214 of 291

  Are users accessing assets locally or remotely, or a mixture of both?
 Do distinct parts of the organization have different security requirements?
 What types of traffic exist on the network?
 Are the needs of security consistent with the business/operational needs of
the organization?
 Is there a strong commitment from to provide sufficient resources to implement security
policies and technologies?
 Is there a strong commitment for security awareness training?

A strong security policy should be clearly defined, implemented, and documented, yet simple
enough that users can easily conduct business within its parameters. A policy of strong password
creation can only work if there is a system to validate password selection.
In many ways, the security policy is a risk management plan, as it documents the risk threshold
an organization is willing to accept. Because no security technology provides one hundred
percent protection, and in most cases organizations do not have the budget to implement all
required security elements, the security policy rates assets and applies commensurable levels of
security. A critical element often overlooked is the policy on incident response. What is the official
organization response if a policy is violated?

6.3.2 Network Based Service Concepts

For a tiered network, as discussed in the Network Infrastructure section, the security has to be
considered at each level of the network layer.

© Dubai Design District, All rights reserved. Page 215 of 291

 Figure 6-20: Security to be implemented on each Level

The L2 / L3 design provides an excellent approach for building security for the network. The VRF
(virtual routing and forwarding) based design allows a network segment to be extended to virtually
anywhere on the network. Therefore this keeps the network under the visibility of the security
devices which is of critical imperative.

6.3.3 Internet Block

To extend the network connectivity to the public network it needs to be connected to the internet
to provide the required out bound access to the users and visitors within the building and at the
same time to user and other patrons from outside the building. Redundant links from the service
provider should be used to connect to the internet and the links should be properly firewalled by
using a Redundant Firewall.

© Dubai Design District, All rights reserved. Page 216 of 291

 VPN

Figure 6-21: DMZ block overview

The internet security shall comprise of several components following a modular approach. This
approach shall allow additional functional components to be added with minimal disruption to
existing network services as well as making the network easy to diagnose and troubleshoot.
The security devices recommended all serve different purposes but also integrate together to
provide strong security measures at different levels of the network.
The 1st layer of protection shall be provided by applying packet filtering on the internet facing
routers and then DDOS (Distributed Denial of Service) protection applied via the anomaly detector
/guard appliances followed by a stateful session filtering. The Intrusion Prevention System (IPS)
functionality shall be applied to ensure application level security and deeper traffic inspection
policies. This will apply policies enforcing the entry of the internet traffic.

6.3.4 VPN Service

The service goal of VPNs (virtual private networks) is to provide cost-effective, secure connectivity
over a shared infrastructure with the same policies and service attributes enjoyed within a
dedicated private network to users of the building.

To achieve this goal, a VPN solution must deliver the following essential attributes: quality of
service (QoS), ease of management, security, high availability, and scalability.

© Dubai Design District, All rights reserved. Page 217 of 291

 To offer network-based IP VPN services, the network shall need a robust, centralized, scalable
VPN and VPN management capabilities for its internal users / customer / partners. The VPN
service users can connect to their corporate resources from remote locations outside the building.
VPNs also must be resistant to denial-of-service (DoS) attacks and intrusion. Effective security
mechanisms used to protect VPNs shall include: tunnelling, encapsulation, encryption,
constrained routing distribution, routing table separation between VPNs, traffic separation, packet
authentication, user authentication, and access control.
An AAA (Authentication, Authorization and Accounting) application shall provide secured access
to users and visitors. The AAA server must at least support IETF Radius protocol. This application
will ensure the access to users who are permitted and will not only control the level of access but
will also account for the access during the period of use.

6.3.5 Email Security

Email security involves ensuring that internet email is free from malware and SPAM.
In order to do this an email security device should be placed in a public DMZ of the internet block.
This device will handle incoming email and ensure it is SPAM and malware free.

6.3.6 Intrusion Prevention System

Intrusion detection has become a critical component of enterprise and service provider
infrastructures. Increasing complexity in public networks for data transport in light of new business
applications, e-commerce, extranets and virtual private networks (VPNs) has created increased
risks to the integrity and security of internal network. In order to counter increasing security
threats‚ Intrusion Detection Systems (IDS) offers added abilities for detection, logging, auditing
and mitigation of potential security threats
Possible IPS (Intrusion Prevention System) responses to an attack maybe:

 Alarm: sends an alarm to a syslog server

 Drop: drops the packet
 Reset: resets the TCP connection

In order to detect and protect against attempted exploitation of known vulnerabilities an IPS
should be deployed. This should be deployed to monitor the internet block for potential attacks.
IPS functionality can be applied inline within the internet zone without causing bottle necks or
affecting the network performance, alternatively it may also be applied in a non-intrusive
promiscuous mode where it will only inspect a copy of the traffic. This is recommended if the
segments that need be monitored may exceed the throughput of the inline capacity of the device
or whenever the traffic profiles are unknown.
Traffic from the internet will initially enter the internet routers, which shall have ACLs (Access
Control Lists) implemented to allow only the services as defined by the security policy as well as
recommended ACL rules for packet filtering. Stateful filtering will not be implemented at this point.
At this point traffic shall be analysed by the DDOS appliances and filtered before being passed
onto the devices for stateful inspection.

6.3.7 Access and Distribution

At the access layer security shall be implemented on the access switches. All access switches
should be capable of providing the mechanisms to control the security threat emerging due
viruses, spoofing etc. The features like VLAN segmentation, sticky macs, routing protocol security

© Dubai Design District, All rights reserved. Page 218 of 291

 mechanisms, trunk filtering, MAC / ARP/ DHCP protection mechanisms and utilizing voice /
wireless security best practices shall need to be used to ensure a safe network.
The filtering should be applied close to the access ports and will limit any security threat to affect
the core. The will ensure high performance routing and switching network. In general, granular
packet filtering and stateful deep packet inspection should be applied at the access layer,
preferably at the SVI level while aggregate policies should be applied at the distribution layer as
a second layer of defence. This will ensure compliancy from the access layer.

6.3.8 Security Management

Any security implantation is not complete without a proper security management infrastructure.
For a robust security need to have a proper SOC (Security Operations Centre) which will contain
the management and monitoring systems. This SOC shall connect to devices through a network
made up of terminal services connected to console ports “CLI access” on the security devices. If
the security devices need to communicate with other entities over the network, this can be
accomplished via secure in-band communication methodologies to AAA server”.
The SOC devices need to be properly protected behind a firewall. Protocols like TFTP (Trivial File
Transfer Protocol), Syslog and AAA servers shall be required to provide for secure logging and
maintenance procedures. Inline IPS (Intrusion Prevention System) can be applied here without
impact to the network as this is not a bandwidth intensive segment and traffic profiles can be
easily deduced due to the nature of the traffic traversing it.
Security Monitoring, Analysis, and Response System can provide for log correlation from security
devices, thus providing a consolidated view of the network’s security posture as well as threat
analysis and response capabilities.
Security Manager can provide for fast easy and accurate deployment of security features on the
network.
Access Control Server provides for centralized administrative authentication and authorization
services for all networking equipment that support IETF Radius and other protocols. It also
provides for logging activities on the network.
Network Admission Control applications or appliance shall be used to ensure only
desktops/laptops or other endpoints like Wireless access points, IP Phones etc. which meet the
security policy can connect to the building Network. The Network Admission Control system will
ensure anti-virus software and other security patches are up-to-date before being allowed to
access other network resources.
The building network users shall have a host-based IPS that shall protect desktops/laptops from
attaches including zero day attacks. This application need not be signature based so does not
need regular updates to protect against new threats.

© Dubai Design District, All rights reserved. Page 219 of 291

 7 Green ICT Guideline
7.1 Purpose
The Green ICT guideline, also referred to as the Energy Efficiency Management Guideline,
provides d3 design best practice guideline for an Enterprise level Energy Management Platform
that manages specifically Network and Network attached systems.
The Green ICT guideline has many aspects. The primary focus of the Green ICT guideline is the
energy usage by ICT assets and the correlated Greenhouse Gasses (GHG) emissions. Recycling
and materials composition will not be addressed in this document. The system being described
in this section is primarily focused on ICT asset energy management. This focus is related but
separate and distinct from building energy management systems, which rely upon a Building
Management System (BMS) for monitoring and control. The key differences between the two
focus on the end point devices being managed (ICT versus Facilities Infrastructure) and the
communications protocols being employed (Internet Protocols versus Building Management
Protocols). This specification does provide a section on how the two related approaches could
interface for energy usage reporting.

7.2 Scope
The Green ICT guideline section provides guidance on the logical attributes of energy
management protocols, applications and management constructs. These attributes serve as the
basis for the energy management platform specific for d3.
In addition, this section provides recommended logical energy management architecture for the
ICT assets to be deployed in d3. This management hierarchy and architecture is subject to
change based on any subsequent changes to the d3 ICT application and infrastructure
architecture.
The Green ICT guideline provides structured guidance to enable d3 to request information
proposals from leading solution providers for industry leading energy management technologies.
Where possible these recommendations seek to simplify the management administration of an
energy management system to ensure the system can scale effectively across d3 ICT
architecture.
The recommendations presented in this section are based on the design recommendations of
emerging, reference standards organizations like The Green Grid and Climate Savers Computing
Initiatives.

7.3 Design Overview

In order to describe the best energy management platform, this document has broken out all the
major and minor system attributes. This includes but is not limited to the following:

 System Specification
 System Attributes
 Logical Management Architecture
 End Point Devices
 Data Aggregation
 Database Attributes
 Reporting
 Energy and Systems Utilization Management

© Dubai Design District, All rights reserved. Page 220 of 291

  Energy Domains
 User Interface

Each of these system components will be covered in detail throughout this section and shall serve
as a guide for d3 to specify the best possible energy management platform.

7.4 Topological Overview

An ICT energy management system is distinct from a domain specific system in both scale and
application hierarchy. Similar to an asset or databases management system, an energy
management system needs to provide a central management capability with a high degree of
automation. These system qualities need to scale broadly across compute, network and
communications infrastructure. In order to be considered an ICT system, the following system
attributes were selected:

 Must provide multi-protocol support for energy reporting

 Must provide multi-operating system support for energy control policies
 Must provide database of energy profiles of assets that cannot support energy reporting
protocols
 Must support multiple infrastructure classes including network, computing and
communications assets
 Must provide for automated reporting to multiple stakeholders
 Must be able to report energy capacities and Greenhouse (GHG) equivalencies
 Must be able to accommodate temperature monitoring inputs
 Must be able to monitor server energy and system utilization
 Must support architectural modelling between asset configurations
 Must support integration to building management system protocols for energy reporting
 Should support reporting and control policy administration through smart mobile devices
 Must be able to provide API’s into contemporary enterprise management platforms
 Must integrate with Active Directory or LDAP

The system should be able to accommodate a wide range of ICT assets across the many different
environments being constructed in d3. These environments include but are not limited to tenant
office and retail space, data centre, wiring closets and common areas supporting digital signage.
Figure 7-1 provides a high topology of an energy management platform that uses both network
and compute centric approaches to provide cross-domain value. This type of energy
management system is conducive to cloud-based management constructs.

© Dubai Design District, All rights reserved. Page 221 of 291

 Figure 7-1: Central monitoring and control of ICT asset energy usage
The energy management system specification focuses on ease of management, scale of savings,
integration capabilities with related systems and overall system reliability. These qualitative
attributes translate into certain design characteristics that should be considered in more detail
through a procurement exercise. A network centric design based on these qualitative attributes
is recommended. This network centric approach does not preclude compute and related
communications infrastructure, rather it includes multiple infrastructure platforms to deliver the
best possible scale.
In terms of energy discovery capabilities, the system shall utilize an existing IP-based network to
monitor and control the energy usage of ICT assets. The system shall not rely upon a BMS or
branch circuit monitoring for energy data and power state controls. The network shall serve as
the communications layer and control plane for energy management and will affect control
through the operating systems of ICT assets. In some cases compute monitoring and control
shall be affected through an interface at the chip set level. Figure 7-2 shows the next level of
topological relationship within the energy management system.

© Dubai Design District, All rights reserved. Page 222 of 291

 Figure 7-2: Energy Management System discovery capabilities
The energy management system shall provide discovery benchmarks in order to measure the
efficacy of and power savings control policies that would be enabled. These benchmarks should
be stored within the energy management application and be administered as thresholds that can
be changed as priorities change.

7.5 Energy Metrics

There are currently no adopted standards in the industry that define a Green ICT metric. There
are emerging energy efficiency metrics from industry consortia like The Green Grid and Climate
Savers Computing Initiative that will be referenced in this document.
For the sake of this design specification, there are key metrics referenced that are emerging and
associations of existing metrics that will be referenced. This ensures d3 has flexibility in how it
chooses to measure the success of an energy management system.
The Figure 7-3 below provides an overview of contemporary efficiency metrics that the energy
management system should be able to accommodate.

© Dubai Design District, All rights reserved. Page 223 of 291

 Figure 7-3: Metrics for measuring and reporting energy efficiency of ICT Systems
Another area of the ICT architecture to consider is supporting facilities. The largest opportunity
for energy efficiency in the supporting facilities will be within the cooling systems that support
high-density environments like data centres. These Computer Room Air Conditioning (CRAC)
units will typically require two times the energy requirement of the ICT equipment they support.
The energy management system being specified in this document is not intended to actively
manage CRAC systems but should be able to monitor these systems. The energy management
system should be able to monitor either directly from the CARC unit or through a BMS with a web
services front end. The efficiency metrics that the ICT energy management system should be
able to feed into a BMS are covered in Figure 7-4.

Figure 7-4: Cooling metrics example for ICT energy management

© Dubai Design District, All rights reserved. Page 224 of 291

 In addition to emerging and existing efficiency metrics, the energy management system should
support custom metrics that can serve as Key Performance Indicators (KPI’s) for d3. The system
should allow for both capacity and productivity metric associations. Some examples include:

 Wattage Used (by asset) associated to Server Utilization

 Wattage Used (by asset) associated to Virtual Machines (VM) per Physical Host
 Wattage Used (by asset) associated to individual Administrator
 Wattage Used (by asset) associated to Hardware Domain (network, compute, storage,
other)
 Wattage Used (by equipment rack) associated to data centre Cooling Zone
 Wattage Used (aggregate) associated to department or Business Unit

In later sections of this document, integration capabilities between the ICT energy management
system and BMS are addressed.

7.6 ICT Assets

The energy management system should provide the maximum possible scale of asset coverage
for energy monitoring and control. The energy management system shall span multiple asset
classes, manufacturers and environments. This capability is new in the industry but does exist
and provides more benefit than legacy, single domain energy management systems. A
description of the asset types and classes are included in Table 7-1.
Infrastructure Asset Types
Class
Compute Desktop PC’s, Laptops, Branch Servers, Lab Servers, Data Centre Servers,
Call Managers, Blade Servers, Appliances
Network Branch Switching, Aggregate and Access Switching, Data Centre and Lab
Switching, Routing, Network Appliances, Wireless Access Points, IP Phones
Storage Tape, Disk and Network Attached Storage
Other Specialized Appliances, Point of Sale Devices, Access Controls, Printers
Table 7-1: Typical ICT asset types managed by an ICT energy management system
These asset types will be represented as end point, energy manageable entities within the energy
management system.
The asset types should be compatible with the energy management platform. In case they are
not, there are a few alternatives to monitor their energy:

 Specify procurement of energy management capable assets

 Take provisions to monitor the branch circuits that feed these assets
 Install network manageable power distribution units (PDU’s) for these assets
 Consider using statistical derivation to interpret energy usage of non-communicative
devices through a combination of the ICT energy management system and BMS
metering.

7.7 Communication Protocols

The energy management system should provide a broad capability to aggregate multiple energy
management and communications protocols. Furthermore, the system must be able to provide
an Application Programming Interface (API) into contemporary ICT enterprise management

© Dubai Design District, All rights reserved. Page 225 of 291

 systems. This ensures d3 can derive the maximum benefit from an ICT energy management
system deployment.
The energy management applications that are industry will capture the majority of the protocols
listed in this section. Facilities protocols like ModBUS, LonWorks and BACnet are preferable but
not critical to the energy management system. An interface to these protocols would simplify
integration between an ICT energy management system and a BMS system with a web interface.
This capability will often eliminate the need to provide an additional physical gateway between
the systems.
The energy management application should provide for data normalization and aggregation of
energy data across multiple protocols. Furthermore the system should be capable of setting user
defined thresholds and capacity benchmarks. This will enable d3 to refine the energy
management system over time to improve the accuracy of asset-based energy reporting. Table
7-2 provides an overview of asset classes and the protocols that provide energy reporting and/or
control capabilities.

Infrastructure Energy Capable Protocol

Class
Compute vPro, DCIM, SSH, WMI, IPMI, SNMP, .XML
Network Energywise, SNMP, SSH
Storage SNMP
Facilities Web Services, BACnet, LonWorks, ModBUS
Table 7-2: Typical energy protocols by asset class

7.8 Data Aggregation

In addition to energy discovery and asset association capabilities, the energy management
system should be able to utilize an IP network to aggregate and manage energy data. The
network topology should accommodate for Layer 3 energy management data transport,
accommodating cloud-based functionalities. Furthermore, the data aggregation methodology
should be structured in a parent, child and entity hierarchy (more on this covered in Energy
Domains section).
An energy management system is recommended that can support energy data through its own
database or can feed energy data into another database. This gives d3 the flexibility in its energy
data aggregation and storage strategy.
A data aggregation function is not recommended for facilities energy data. This data should be
fed from and aggregated by a contemporary BMS. In cases where facilities data is relevant to
ICT savings (high-density cooling for example) the energy management system should contain
customizable fields and database support for these facilities assets.
An example of a data aggregation methodology that should be utilized by the energy management
system is shown Figure 7-5 in below:

© Dubai Design District, All rights reserved. Page 226 of 291

 Figure 7-5: Data aggregation hierarchy for energy management data

7.9 Energy Domains

The energy management system recommended for d3 is intended to be an enterprise level
system. This level of system requires a logical management methodology that is standardized
and conducive to scalability. This functionality is critical to a cross-infrastructure domain approach
to energy management of ICT systems. For sake of this document an energy domain is defined
as the following:
A logical grouping of ICT assets based on user defined inputs such as; infrastructure class,
administrator, department and end point use case. Energy domains provide for a data hierarchy
for energy monitoring and broad based control policy administration.
Each domain will need to be set up and administered by d3 or qualified energy management
partner. The structure of these domains should reflect the intent of an energy management
program for d3. If the intent is to save electrical cost and the GHG’s that correlate, then d3 should
structure assets into tiers of criticality so that less critical assets can be powered down when not
needed. If the intent is to provide visibility to the departmental units that d3 Operations support,
then domains should be structured by departmental and administrative assignment. The energy
management system should provide the capability of structuring energy domains by the following
key attributes:

 Domains structured by asset criticality

 Domains structured by asset use case (i.e. web server, lobby, Judge desktop, etc.)
 Domains structured by department and individual administrator
 Domains structured by hardware class (i.e. network, compute, storage, other and
facilities)
 Domains structured by operating system
 Domains structured by application dependency

© Dubai Design District, All rights reserved. Page 227 of 291

 In terms of the interdependence of assets within an energy management system, the key features
and capabilities are as follows:

7.9.1 Parent, Child and Entity Hierarchy

The energy management system should base its energy domain structure on a relational
interdependence model. The hierarchical relationship of these assets should enable scalable
data aggregation, control policy orchestration and search functionality. Starting from the point of
use, an entity would be accessed by and report to a child. The child then reports its energy use
and any connected entities to a parent. A parent is the asset that hosts the energy management
application that supports a collection of energy domains.

7.9.2 Availability Awareness

In this document availability awareness refers to the capability in some energy management
systems to provide an algorithmic capability that shares asset criticality levels within and across
energy domains. This capability allows any power consuming entity to communicate its criticality
level to a child and parent. This linkage between assets ensures that data availability is not
impacted where interdependence exists. For example, if any IP phone is set to never be
shutdown, the edge and core switching that support connectivity for that phone cannot be
shutdown either.

7.9.3 Domain Association

The energy management system being specific should provide the capability to form logical
association between distinct energy domains. These associations should include domains of
both facilities and ICT assets. This association capability should also be part of the energy
management systems reporting functionality. An example of association between domains would
be data centre ICT infrastructure associated to a data centre computer room air conditioning unit
(CRAC).
The features and capabilities of energy domain governance will be critical to the ease of
administration, scalability and risk mitigation of the energy management system. An example of
a topographical view for an energy domain that addresses criticality of assets and associations
between domains is shown in Figure 7-6.

© Dubai Design District, All rights reserved. Page 228 of 291

 Figure 7-6: Energy domains; asset criticality and domain association

7.10 Dependency Mapping

The energy management system should provide user definable fields to associate applications to
energy domains. This is a key feature to mitigate risks related to human error in administering the
energy management system.
It is recommended that d3 consider an application dependency map be created if energy savings
is the biggest priority of the energy management system. Having this map will enable d3 to target
savings across all criticality levels of deployed ICT assets. Figure 7-7 shows an example of
topographical application and process dependency map.

© Dubai Design District, All rights reserved. Page 229 of 291

 Figure 7-7: Typical ICT asset types and support model for energy management

7.11 Control Policies

The energy management system should provide for automated control policies that can be
centrally administered. These policies should be enacted primarily through software commands
issued through the end point devices operating system or chip set. It is a preferable feature that
the energy management system accommodates network controllable, EnergyWise certified
power distribution units (IP addressable, controllable power outlets).
The control policies of the energy management system must provide provisions to quality check
power control capabilities against asset criticality level. Referred to in this document as
Availability Awareness (section 8), the control policies must account for both the power and data
interdependence between controllable entities.
Key policy functions are summarized in Table 7-3.
Control Policy Description Implication
Type
Time-Based Policy enabling regular scheduling Enables energy management for
of power states for energy domains desktops, IP phones, wireless access
and entities. Typically applied to points, printers and other less-critical
office space environments ICT infrastructure
Event-Based Policy executed based on a user- Enables planned load shedding of
defined input. Inputs typically less critical assets based key inputs
relate to thresholds, utilization and like temperature threshold exceptions
utility demand response signals and electrical cost inputs
Location-Based Policy that utilizes smart phone Enables a broad array of human
triangulation and/or access control presence aware energy control
systems to enable an energy policies. Allows administrators to set

© Dubai Design District, All rights reserved. Page 230 of 291

 control state of an entity based on proximity triggers for any ICT
the physical proximity of an environment
administrator
Load-Based Policy that takes input from system Supports improved analytics and
utilization reporting. Compute and electrical savings for dynamic ICT
network utilization statistics are fed environments where virtualization
into the energy management technologies are deployed. Improves
system to better correlate electrical overall virtualization efficiencies
supply with ICT system demand
Table 7-3: Typical energy protocols by asset class

7.12 Reporting
Automated reporting to multiple stakeholder groups should be supported by the energy
management system. These reports should be customizable and provide histogram and
projection fields for energy capacities and related data. Furthermore, reporting capabilities should
include the association of related but distinct metrics like Watts per Virtual Machine.
Many different reporting options have been uncovered in researching this system specification.
While flexibility has been deemed a desirable attribute, there are several organizing principles an
energy management system should have. These reporting principles are listed as follows:

 Reporting should be template based

 Reporting templates should be modular and editable by administrator
 Reporting should be capable of supporting federated reporting to multiple stakeholders
 Reporting should support relational data sets
 Reporting should provide histogram capabilities
 Reporting should provide data extrapolation and projection capabilities
 Reporting should support digital signage dashboard capabilities
 Reporting should support .xml and .html raw data feed capabilities

Figure 7-8 shows an example of a reporting template from a contemporary energy management
platform.

© Dubai Design District, All rights reserved. Page 231 of 291

 Figure 7-8: Reporting example for digital signage and departmental reporting

7.13 Utilization Management

The energy management system shall have the capability to integrate with other ICT
management approaches. The expectation is that key integration points will provide d3 with better
data to make more informed decisions on energy monitoring and control policies.
The most appropriate energy management system for d3 should have utilization monitoring
through interfaces with other ICT management platforms are shown in Table 7-4.
Infrastructure Utilization Metric Description Implication to Energy
Class Management System
Network Typically measured by ports utilized Energy system should be able to
versus ports allocated provide Watts per Port data
Compute Typically measured by a combination Energy system should be able to
of CPU, Memory on I/O. Also provide Watts per Virtual machine
measured by virtual machines per data
physical host
Storage Typically measured by LUN’s utilized Energy system should be able to
versus LUN’s allocated provide Watts per LUN data

All Electrical utilization is typically Energy system should be able to

measured by Watts being used versus provide electrical capacity data for
total Wattage capacity of asset power ICT assets
supplies
Table 7-4: Energy data aligned to ICT system utilization
In general, the energy management system should be able to align systems utilization data to
electrical utilization data. This capability will enable d3 to use the energy management system

© Dubai Design District, All rights reserved. Page 232 of 291

 as an ICT capacity management tool across different infrastructure classes. This enables the d3
ICT Operation to be proactive in provisioning new capacity while managing the efficiency of day-
to-day productivity. Figure 7-9 provides an example of utilization monitoring through a
contemporary energy management system.

Figure 7-9: Systems and electrical utilization monitoring

7.14 Architectural Modelling

While not specifically requested, a tie into procurement criteria is deemed a highly preferable
quality.
The energy system should provide for a grouping of and comparison across different asset
configurations. These different architectural models should be based on either deployed or
proposed to be deployed infrastructure. This implies the energy system must provide a
comprehensive database of ICT assets in use today. This capability will enable d3 to make more
informed decisions on the underlying costs of one architecture over another. Figure 7-10 provides
an example of contemporary energy management system that supports comparisons between
architectures.

© Dubai Design District, All rights reserved. Page 233 of 291

 Figure 7-10 Architectural modelling and comparison considering energy cost

7.15 Building Management System Interface

The energy management system shall interface with the BMS system currently used in d3 and
accommodates facilities assets and the protocols in use. This enables d3 to form associations
between ICT assets and facilities assets, thereby providing more complete data on energy and
GHG savings.
The Siemens Desigo BMS being specified should provide options for a web interface to the ICT
energy management system.

7.16 User Interface

The attributes of the energy management system Graphical User Interfaces (GUI) shall include:

 Modular, widget based interface that can be customized by an administrator

 Can accommodate related data feeds (widgets) into the interface such as BMS data
 Provides multiple graphing options for live data
 Provides for rank-stacking of multiple data sets
 Accommodate multiple administrator account login
 Provides a digital signage presentation interface that can be customized

Figure 7-11 provides an example of a contemporary, enterprise-level energy management

system.

© Dubai Design District, All rights reserved. Page 234 of 291

 Figure 7-11: Sample of an enterprise energy management system GUI

© Dubai Design District, All rights reserved. Page 235 of 291

 8 Leading Building and Energy
Certifications
Leading Building and Energy certifications to consider are: LEED, Green Globes, Estidama,
Emirates Energy Star and ISO.

Here is an overview of some the key certifications:

8.1 LEED
Leadership in Energy & Environmental Design is a green building certification program that
recognizes best-in-class building strategies and practices. To receive LEED certification, building
projects satisfy prerequisites and earn points to achieve different levels of certification.
Prerequisites and credits differ for each rating system, and teams choose the best fit for their
project. In the United States and in a number of other countries around the world, LEED
certification is the recognized standard for measuring building sustainability. Achieving LEED
certification is the best way for you to demonstrate that your building project is truly "green." The
LEED green building rating system developed and administered by the U.S. Green Building
Council, a Washington D.C.-based, non-profit coalition of building industry leaders -- is designed
to promote design and construction practices that increase profitability while reducing the
negative environmental impacts of buildings.

8.1.1 The benefits of LEED certification

LEED certification, which includes a rigorous third-party commissioning process, offers
compelling proof to the clients and the public at large to achieve environmental goals and building
is performing as designed. Getting certified allows taking advantage of a growing number of state
and local government incentives, and can help boost press interest in a project.

© Dubai Design District, All rights reserved. Page 236 of 291

 The LEED rating system offers four certification levels for new construction - Certified, Silver,
Gold and Platinum that correspond to the number of credits accrued in five green design
categories:

 sustainable sites,
 water efficiency,
 energy and atmosphere,
 materials and resources and
 indoor environmental quality

LEED standards cover new commercial construction and major renovation projects, interiors
projects and existing building operations. Standards are under development to cover commercial
"core & shell" construction, new home construction and neighbourhood developments.

8.1.2 Process to achieve LEED certification

The U.S. Green Building Council's LEED site provides tools for building professionals, including:

 Get information on the LEED certification process.

 LEED documents, such as checklists and reference guides. Standards are now
available or in development for the following project types:
o New commercial construction and major renovation projects (LEED-NC)
o Existing building operations (LEED-EB)
o Commercial interiors projects (LEED-CI)
o Core and shell projects (LEED-CS)
o Homes (LEED-H)
o Neighbourhood Development (LEED-ND)
 A list of LEED-certified projects
 A directory of LEED-accredited professionals
 Information on LEED training workshops
 A calendar of green building industry conferences

8.1.3 Tips for Getting LEED Certified:

 Set a clear environmental target. Before starting the design phase of a project, decide
what level of LEED certification is aimed for, and settle on a firm overall budget. Also
consider including an optional higher certification target -- a "stretch" goal -- to stimulate
creativity.
 Set a clear and adequate budget. Higher levels of LEED certification, such as Platinum,
do require additional expenditure and should be budgeted for accordingly
 Stick to your budget and your LEED goal. Throughout out the design and building
process, be sure that the entire project team is focused on meeting your LEED goal on
budget. Maintain the environmental and economic integrity of your project at every turn.
 Engineer for Life Cycle Value to value-engineer a project; examine green investments in
terms of how they will affect expenses over the entire life of the building. Before deciding
to cut a line item, look first at its relationship to other features to see if keeping it will help
you achieve money-saving synergies, as well as LEED credits. Many energy-saving
features allow for the resizing or elimination of other equipment, or reduce total capital
costs by paying for themselves immediately or within a few months of operation. Prior to
beginning, set your goals for "life cycle" value-engineering rather than "first cost" value-
engineering.

© Dubai Design District, All rights reserved. Page 237 of 291

  Hire LEED-accredited professionals. Thousands of architects, consultants, engineers,
product marketers, environmentalists and other building industry professionals around
the country have a demonstrated knowledge of green building and the LEED rating
system and process -- and can assist you in meeting your LEED goal. These
professionals can suggest ways to earn LEED credits without extra cost, identify means
of offsetting certain expenses with savings in other areas and spot opportunities for
synergies in your project improving occupant health and well-being.

8.2 Green Globes

The Green Globe certification is a structured assessment of the sustainability performance of the
travel and tourism businesses and their supply chain partners. Businesses can monitor
improvements and document achievements leading to certification of their enterprises’
sustainable operation and management. The Green Globe Standard includes 44 mandatory core
criteria supported by over 380 compliance indicators. The applicable indicators vary by type of
certification, geographical area as well as local factors. The entire Green Globe Standard is
reviewed and updated twice per calendar year. The Green Globe Standard is based on the
following international standards and agreements:

 Global Sustainable Tourism Criteria

 Global Partnership for Sustainable Tourism Criteria (STC Partnership)
 Baseline Criteria of the Sustainable Tourism Certification Network of the Americas
 Agenda 21 and principles for Sustainable Development endorsed by 182 Governments at
the United Nations Rio de Janeiro Earth Summit in 1992
 ISO 9001 / 14001 / 19011 (International Standard Organization)

Green Globes offers a different approach: one that provides in-depth support for improvements
ideally suited to each project. Building owners and facility managers know their buildings and
operations better than anyone else. Leverage that knowledge with personalized assistance to
produce best practices in sustainable design, construction and operations. Incorporating third-
party assessors available throughout the certification process, forge a partnership that allows
experienced green building project teams to shine and reduces the learning curve for those new
to green building. Green Globes Certification benefits help you:

 Reduce operating costs

 Qualify for tax incentives
 Meet government regulations
 Attract and retain employees
 Increase your property’s marketability

8.2.1 Benefits of Green Globes

 Provide a competitive advantage
 Respected standard for sustainability worldwide
 Achieve highest quality
 Measurable energy & water savings
 Operational efficiency
 International recognition of green practices
 Roadmap to sustainability

© Dubai Design District, All rights reserved. Page 238 of 291

 8.2.2 Process to achieve certification
 Registration and company information and submit the form, you’ll receive an automated
email response confirming your registration
 To guarantee compliance to the highest international standards, a third-party
independent auditor is appointed to work with clients on-site. The international standard
ISO 19011 provides guidance on the management of audit programs, the conduct of
internal and external management systems as well as the competence and evaluation of
auditors. Green Globe has drawn on ISO 19011:2002 in the development of its audit
program.

8.3 Estidama
By Abu Dhabi Urban Planning Council (UPC) is recognized internationally for large-scale
sustainable urban planning and for rapid growth. Plan Abu Dhabi 2030 urban master plan
addresses sustainability as a core principle. Estidama, which is the Arabic word for sustainability,
is an initiative developed and promoted by the UPC. Estidama is the intellectual legacy of the late
Sheikh Zayed bin Sultan Al Nahyan and a manifestation of visionary governance promoting
thoughtful and responsible development. The leadership of Abu Dhabi are progressing the
principles and imperatives for sustainable development, through Estidama, while recognizing that
the unique cultural, climatic and economic development needs of the region require a more
localized definition of sustainability.
Estidama is not just a rating method or something people do, it is a vision and a desire to achieve
a new sustainable way of life in the Arab world. The ultimate goal of Estidama is to preserve and
enrich Abu Dhabi's physical and cultural identity, while creating an always improving quality of life
for its residents on four equal pillars of sustainability: environmental, economic, social, and
cultural. This touches all aspects of life in Abu Dhabi - the way we build, the way we resource,
the way we live, the choices we make - all in an effort to attain a sustainable state of living.
Estidama arose from the need to properly plan, design, construct and operate sustainable
developments with respect to the traditions embedded within the rich local culture on one hand
and the harsh climatic nature of the region on the other. To this end, project owners, developers,
design teams and even residents need to think differently about how they approach the design
and planning process.
Estidama is the first program of its kind that is tailored to the Middle East region. In the immediate
term, Estidama is focused on the rapidly changing built environment. It is in this area that the UPC
is making significant strides to influence projects under design, development or construction
within the Emirate of Abu Dhabi.
Estidama continues to evolve to embrace the rapidly changing concepts for sustainability, and
ground them in the environmental, social, cultural, and economic needs of the GCC region.
Estidama sets the path for the Emirate, its citizens and its residents.
Being a key aspect of the "Abu Dhabi Vision 2030" to drive to build the Emirates to innovative
green standards. The program is not itself a green building rating system like LEED or BREEAM,
but rather a collection of ideals that are imposed in an elective building code type of format. Within
Estidama, there is a green building rating system called the Pearl Rating System that is utilized
to evaluate sustainable building development practices. The Estidama program is mandatory in
Abu Dhabi - all buildings must achieve a minimum 1 Pearl Rating, and all government-funded
buildings must achieve a minimum 2 Pearl Rating.

© Dubai Design District, All rights reserved. Page 239 of 291

 8.3.1 Steps to achieve certification
These are the steps to follow:

Figure 8-1: Process for Estidama Rating

 All certifications are conditional and expire when subsequent stages are reached. For
example a development achieves a design stage rating and reaches the end of
construction. It will then need to submit construction stage documentation to achieve a
construction rating.

8.4 Emirates Energy Star

Emirates Energy Star is an initiative to champion the cause for improving energy efficiency and
reducing the carbon footprint of the UAE. The program, introduced by Etisalat and Pacific
Controls, aims to reduce 20% energy consumed and 20% of carbon footprint of the UAE by 2015.
The program involves retrofitting existing buildings with M2M systems to increase energy
efficiency through Managed Energy Monitoring Services. Emirates Energy Star program
leverages upon Machines to Machines Technology (M2M) will help audit energy consumption,
deploy optimization measures and monitor the consumption over a period of time.
Etisalat and Pacific Controls strategic alliance will leverage upon Etisalat networks and Pacific
Controls Command Control Centre to deliver managed energy services to customers. The
Emirates Energy Star role is to plan, engage and execute Managed Energy Services with existing
building owners across all the Emirates to increase the efficiency of all the existing building stock.
Features:

 Audit energy consumption, deploy optimization measures and monitor the consumption
over a period of time
 Optimize energy consumption - Optimizing the energy consumption of the building
without compromising the comfort level of the occupants not only cuts off the utility bills
but also in gaining recognition in supporting green initiative
 Reducing energy consumption
 Reduce the overall carbon footprint
 Increase the efficiency of the existing buildings
 Optimize your energy consumption, deploy optimization measures and monitor the
consumption over a period of time

© Dubai Design District, All rights reserved. Page 240 of 291

 Benefits:

 Improve customer and staff comfort and satisfaction levels

 Reduce maintenance costs and system failures
 Increase equipment life and building value
 Because building retrofits and other energy efficiency measures help to reduce GHG
emissions that contribute to climate change, joining the Emirates Energy Star program
will also:
o Provide a marketing tool as a sustainable business
o Enhance corporate citizenship and meet corporate social responsibility targets
o Support global climate change initiatives by the UN and UAE
o Help the UAE meet its targets set in the Kyoto protocol
o Reduce the building's, company's and country's carbon footprint

8.4.1 Steps to achieve certification

Emirates Energy Star Rating System "STAR AWARD" comprises five successive levels based
on the energy efficiency improvements achieved through the Emirates Energy Star Program – 1
– 5 Star Programs:

 10% Energy Saving for the first star level

 15% Energy Saving for the second star level
 20% Energy Saving for the third star level
 25% Energy Saving for the fourth star level
 30% Energy Saving for the fifth star level

Besides the obvious cost savings for the end user in the form of lower energy utility bills, the
Emirates Energy Star program will help decrease pollution, water consumption and resultant
waste. Building owners will be able to recover their investment towards the program from the
savings that they make. The payback period for the building owner would be in the range of 18-
24 months depending upon the STAR rating:

© Dubai Design District, All rights reserved. Page 241 of 291

 Figure 8-2: Performance of Emirates Energy Star

8.5 WCCD ISO

An International Organization for Standardization (ISO) standard gives world-class specifications
for products, services, and systems to ensure quality, safety, and efficiency.
ISO 37120 Sustainable Development of Communities: Indicators for City Services and Quality of
Life is the first ISO standard on city metrics. This ground breaking standard is based on a set of
indicators that was developed and extensively tested by the Global City Indicators Facility (The
WCCD's sister organization) and its 250+ member cities worldwide. As a global leader on
standardized metrics, the WCCD has developed the first ISO 37120 certification system along
with the Global Cities Registry™.
Cities can obtain different levels of certification based on the number of indicators reported and
verified according to ISO 37120.

8.5.1 WCCD ISO 37120 Certification Levels

WCCD Certification levels are based on the number of indicators reported by the city. WCCD
offers a wide range of certification levels:

 Aspirational 30-45 Core Indicators

 Bronze 46-59 Indicators (46 Core + 0-13 Supporting)
 Silver 60-75 Indicators (46 Core + 14-29 Supporting)
 Gold 76-90 Indicators (46 Core + 30-44 Supporting)
 Platinum 91-100 Indicators (46 Core + 45-54 Supporting)

© Dubai Design District, All rights reserved. Page 242 of 291

 Figure 8-3: ISO 37120 Certification Levels

8.5.2 Benefits of WCCD ISO 37120Certification

Categorized under 17 themes and 100 indicators for city services and quality of life, ISO 37120
certification will guide your city towards a smart, sustainable, resilient, and prosperous future
armed with independently verified and globally comparable city data. WCCD certification ensures
data reliability with third party verification. There are numerous benefits and applications of ISO
37120 certification in cities, but overall conformity with ISO 37120 will lead to responsible city
building.

Figure 8-4: Benefits of ISO 37120 Certification

© Dubai Design District, All rights reserved. Page 243 of 291

 9 Gap and Impact Analysis
A detailed As-Is Assessment of the ICT systems, MEP Systems and Smart Initiatives was done,
gapsandthis assessment was compared to the requirements listed in the Design Guideline
Document, the detailed gaps identified for the in-building systems in Section 9.1, for the city
systems in Section 9.2, for the d3 IP Network in Section 9.3 and for the smart Services in Section
9.4.

The details of the gap analysis are provided in the sections below.

9.1 In building Systems

9.1.1 ICT Inside Plant
The details of the in-building ICT inside plant gap analysis are included in the table below:
Gap Recommendation
In the common areas of the This document provides clear guidelines to design a
11 buildings of Phase-1, no dedicated Smart Network within the buildings.
network has been
These guidelines need to be shared with the d3 Consultants
provisioned
and the Contractors for compliance.
There is no Wireless Network d3 to deploy Wi-Fi services with location based capabilities.
deployed in Phase 1
There is no ICT NOC The d3 ICT NOC processes need to be created in alignment
processes with the Smart City ICT NOC process provided in this
document.
The Building Management The Building Management System together with all other
System are currently using a building systems should be converged on the d3 Smart
physically separate network Services Network.
deployed by Siemens
For phase-1, it is strongly recommended to upgrade already
existing Building Management System Network, as per the
provided guidelines, to act as the d3 Smart Services Network
For any new phases, it is recommended to build a converged
network for Smart Service needs from day one to enable the
building systems.
The security systems are No recommendations as this network should be separate
currently using a separate according to applicable laws and regulations
network deployed by RED
Solutions®
There are no telecom rooms Allocate telecom rooms in the new buildings for the d3 Smart
for the d3 Smart Services Services Network following the requirements provided in this
Network document.
Figure 9-1: In-Building ICT Gaps

© Dubai Design District, All rights reserved. Page 244 of 291

 9.1.2 Building Systems
The details of the building systems gap analysis are included in the table below:
Gap Recommendation
The provided design It is recommended to use BIM as the common reference
documentation is not using model throughout the building lifecycle.
BIM as the common
reference model
The Smart Meters are not It is recommended to connect the smart meters to the d3
sharing the same network as smart services network. In case it is not possible due to local
the smart services regulations, ensure sharing of data.
The access control, video Since it is not possible for the security systems to share the
surveillance and car parking same network, ensure sharing of data.
are not sharing the same
network as the smart
services
There is no digital signage, Initiate the procurement of the listed systems as per the
interactive kiosks, requirement listed in this document
audio/video system and
solar panels in the current
designs of d3
There is no point of sale, Include the point of sale requirements in the retail tenant
smart home and smart office requirement document
system in the current
Include the smart home requirements in the residential
designs of d3
developers requirement document
Include the smart office in the tenant requirement document
Figure 9-2: Building Systems Gaps

9.2 Municipal Systems

9.2.1 City Wet Utilities
The details of the city wet systems gap analysis are included in the table below:
Gap Recommendation
The Wet Utilities designed Guidelines have been provided within this document for all
today within d3 don’t have existing wet utilities.
any automation planned
d3 Smart City team to ensure the compliance of all the
systems with the provided guideline within reasonable time
and cost implication.
The zero compliance with the Design Guideline Document
will mean zero compliance with the Smart Dubai guideline for
districts.
Figure 9-3: City Wet Utilities Gaps

© Dubai Design District, All rights reserved. Page 245 of 291

 9.2.2 City Dry Utilities
The details of the city dry utilities gap analysis are included in the table below:
Gap Recommendation
Most of the Dry Utilities are No recommendations were provided on these systems in this
to be provided by individual document on the pretext that the services providers can’t
service providers like DEWA, share the Smart Service Network for carrying out their day to
RTA within d3 day services.
A process or a mechanism needs to be developed between
d3 and its service providers to ensure that their infrastructure
is capable of delivering the Smart Services seamlessly.
Currently it has been agreed that most of the service
providers will provide their data for use by d3 using the Data
Virtualization layer.
Figure 9-4: City Dry Utilities Gaps

9.2.3 Outside Plant Network

The details of the city outside plant network gap analysis are included in the table below:
Gap Recommendation
The Outside plant Drawings issued by du provide a view of some of the routes
containments are adequate particularly of the areas where the fibre has been deployed
based on the Parsons Master already. To understand the existing d3 fibre plant it is
Plan, however there is recommended that all the relevant drawings of the fibre and
limited duct detail in these the duct layouts are requested from du or Tamdeen for
drawings further review.
There is no dedicated duct or This document has provided very clear guidelines that need
fibre for use by d3 Smart City to be taken into accounts for creating a dedicated Smart City
Services defined in the Network in the public areas of the district.
Services Catalogue
There is not fibre laid for d3 An allocation of duct from exiting Telecom Infrastructure or
Smart Services in the public dedicating a new service corridor for Smart Services is a
area or within the existing must.
ducting system
This work should be prioritized.
This document has provided a clear guideline for this
requirement. A discussion by d3 Smart Services Team with
du, Parsons and Tamdeen is a must to fulfil this gap.
There is no PoP nor Space for the Smart Services Network PoP needs to be
dedicated telecom rooms for allocated and the room needs to be built ASAP as new
the smart services network Phases are being constructed. This will impact the fibre
network for the Smart Services Network.
No data centre space is The space, power and cooling requirements have been
allocated within or outside defined in this document. d3 Smart Services team needs get
d3 for Smart Services the data centre space allocated so that the necessary back

© Dubai Design District, All rights reserved. Page 246 of 291

 end applications can be deployed in safe and secure
environment
Figure 9-5: City Outside Plant Network Gaps

9.2.4 Other City Systems

The details of the other city systems gap analysis are included in the table below:
Gap Recommendation
Most of the Other City No recommendations were provided on these systems in this
Systems are to be provided document on the pretext that the services providers can’t
by individual service share the Smart Service Network for carrying out their day to
providers like RTA within d3 day services.
A process or a mechanism needs to be developed between
d3 and its service providers to ensure that their infrastructure
is capable of delivering the Smart Services seamlessly.
Currently it has been agreed that most of the service
providers will provide their data for use by d3 using the Data
Virtualization layer.
The other city systems are It is recommended for d3 to share the requirements of the
not yet awarded by d3 other city systems as included in this document.
d3 Smart City team to ensure the compliance of all the
systems with the provided guideline.
Figure 9-6: City Other Systems Gaps

9.3 Smart City ICT Network

The details of the Smart City ICT Network gap analysis are included in the table below:
Gap Recommendation
There is no Smart City This document provides a high level view of d3 Smart City
Architecture within d3 Architecture. However, it is recommended for d3 to define
this Architecture in detail. This architecture will ensure that
new services offered in d3 can easily share data with each
other and with the external world.
There is no Smart Services d3 to start the implementation of its Smart Service Network
Network within d3 as per the guidelines provided within this document
Figure 9-7: Smart City ICT Gaps

© Dubai Design District, All rights reserved. Page 247 of 291

 The details of the smart services gap analysis are included in the table below:
Gap Recommendation
Operation and Maintenance The scope of the facility management company currently
Enhancement, in operation awarded (Al Shirawi) does not cover 100% the scope of the
status, complies partially Operation and Maintenance Enhancement service as
with the definition of the described in the service catalogue.
service.
d3 to increase the scope of the FM company, in due time, by
adding the integration of the FM software to the Siemens
Building Management System.
Integrated Building The Siemens integrated building management system
Management System, in complies functionally with the description of the service as
operation status, complies per the catalogue.
partially with the definition of
However, the system installed is not centralized. There are
the service
three individual servers for the three blocks of the north block.
d3 to connect the three server to have a consolidated view.
40 out of 45 smart services These services need to be further defined and d3 has to
are not planned, have no proceed with their procurement according as needed.
requirements defined and
The priority will be given to the services of group-A as defined
are not awarded.
in the service strategy document.
Within d3 there is no Data and Information sharing methodologies need to be
standards for data and standardized and finalized so that any new services can be
information sharing deployed with ease and desired precision.

© Dubai Design District, All rights reserved. Page 248 of 291

 New backend applications or partner applications should be
chosen keeping in view this requirement.
There is no Service Some functions such as the payment gateway, the geo
Enablement layer location reference and the user authentication and trust are
common services that enable the smart services.
The 45 services need to be further defined to identify the
connection points with the service enablement layer.
The service enablement layer needs to be further defined to
identify all elements.
The 45 services that will be procured from third party vendors
must have the proper interface to integrate with the service
enablement layer.
Figure 9-8: Smart Services Gaps

© Dubai Design District, All rights reserved. Page 249 of 291

 10 DGD Action Plan
The purpose of this section is to inform the developers, consultants and contractors which
sections of this document they need to follow, what are the steps required to validate their designs
and what is the process to follow to get a Smart City Non Objection Certificate (NOC).

The Smart City NOC forces new contractors and developers to adhere to the guidelines included
in this document.

10.1 Relevant Sections

The table below identifies the relevant sections of the Design Guideline Document related to each
stakeholder type:
Section Section Heading

Infrastructure
Number

Consultant

Consultant
Developer
Tamdeen

Building
1 Background d3

2 Introduction

3 Smart City Architecture

4 ICT Guidelines for Building Systems in d3

5 ICT guidelines for Municipal Systems in d3

6 ICT Network Infrastructure guidelines for d3

7 Green ICT Guideline

8 Leading Building and Energy Certifications

10 DGD Action Plan

© Dubai Design District, All rights reserved. Page 250 of 291

 10.2 Smart City No Objection Certificate
10.2.1 Design and Construction NOC
During the design phase of any building or district, a design validation and construction NOC must
be received from the d3. The following information and documentation is required:

 Completed design NOC application form

 Plan drawing of affected area
 Detailed building floor drawings showing equipment room positions, layouts, and cable
containment systems
 Schematic drawing for each technology being deployed
 Single line diagram for each technology being deployed
 Hardware and Software specifications particular for items that focus on automation and
convergence

All of the above should be submitted in two hard copies and one up-to-date soft copy (AutoCAD
format) for the NOC to be processed. In case that the drawings are initially rejected, the
resubmission should include the first five bullet points above and an updated softcopy.
Incomplete submissions should be returned to the applicant.
Any modification or changes in the approved drawing will void the NOC. The
consultant/contractor will need to resubmit for a new NOC.

10.2.2 Material NOC

Prior to the installation of the any building system, a material no objection certificate must be
received from d3.
The following documentation is required in order to process the material no objection certificate:

 Copy of approved design and construction drawings

 Design brief and summary sheet
 Vendor system performance warranty and 3rd party certificate of compliance
 Certificate of authorization of installer
 Products Catalogue (technical product description)

10.2.3 NOC Validity

The d3 Smart City NOC remains valid until any changes are proposed by the contractor.
d3 reserves the right to cancel any issued NOC in the event of any inconsistent changes to the
approved SCS or cabling containment system. In the event that an NOC is cancelled, the
consultant is required to resubmit the drawings in order for a new NOC to be issued.

10.2.4 Site Inspections

d3 management reserves the right to make periodic site inspections to verify the working practices
of the installer during the installation phase.

© Dubai Design District, All rights reserved. Page 251 of 291

 10.2.5 Handover and Acceptance
After any work completion, SCS should request the following documents as part of the handover
and acceptance procedure:

 Completion certificate issued by consultant

 Copies of approved site inspection forms (if applicable)
 As-built drawings in hard and soft copy (AutoCAD) including rack elevations and
schematic diagram
 Hardcopy of all cable test results
 Copy of manufacturer’s warranty certificate
 One master key for all the telecom rooms which may require access by d3 staff should
be made available and handed to d3

10.2.6 Sub-Contracting
It is important to note that as part of the Design Validation and NOC process the following criteria
must be strictly followed:

 The Main Contractors can only Sub-Contract scope to a Specialized Contractor for a
particular system or technology provided the sub contractor’s trade license clearly
includes that in its activity list.
 The Sub-Contractor (Specialized Contractor) can under no circumstance further sub
contract it scope either in part or fully to any other sub-contractor.

© Dubai Design District, All rights reserved. Page 252 of 291

 11 Appendix–A Smart City Case Studies
11.1 Summary of Smart Cities
The following table provides a summary view of the alignment of various Smart Cities around the
world, against the focus areas as perceived by d3:
Smart City Smart Smart Smart Smart Smart Smart Smart
Economy Mobility Environment Government People Infrastructure
Living
Barcelona

Mississauga

Rivas, Spain

Songdo,
South Korea

Amsterdam

Copenhagen

Nice, France

Delhi-
Mumbai
Industrial
Corridor
Table 11-1: Smart City Alignment against d3 focus area

11.2 Barcelona, Spain

“Connected City” Improves Quality of Life, Stimulates Economy
City of Barcelona uses Wi-Fi network and location information to increase service levels and
create great experiences.

11.2.1 Challenge
The City of Barcelona has been the capital of Spain’s Catalonia region since the third century
A.D. Current city leaders face 21st-century challenges. They want to revitalize the city. Stimulate
the economy. Provide a great quality of life that attracts businesses, residents, and tourists. Earn
a high spot on lists of the world’s most liveable cities. Reduce carbon footprint. And deliver
government services at lower cost.
The Barcelona City Council knew that technology could help achieve these goals. “We want to
use the Internet to improve the daily lives of citizens,” says Manuel Sanroma, Chief Information
Officer for Barcelona City Council.

© Dubai Design District, All rights reserved. Page 253 of 291

 The City Council was inspired by today’s “Internet of Everything.” Their vision: Create new
connections between people, process, data, and things.
Imagine being able to connect to your work network from a public park, and then meet a friend
for coffee or shopping. Imagine finding everything you need as a tourist, such as bus schedules
and nearby restaurants and entertainment, at touchscreen kiosks conveniently located around
the city. Imagine finding and reserving a parking space on your smartphone. Imagine if city
workers could monitor parking meters, streetlights, and even garbage bins over the network
instead of driving around and consuming fuel.
To make the vision real, the city needed three kinds of technology: A reliable, easy-to-manage
Wi-Fi network. A way to know the location of people and things connected to the network and
different kinds of sensors.

11.2.2 Solution
All of these things are happening today as part of the city’s Smart City project. “We are using
technology to make our social dream possible,” says Tony Vives, Deputy Mayor for Urban Habitat,
Barcelona City Council. “Our goals are economic sustainability, social sustainability, and
environmental sustainability.”
The City of Barcelona’s visionary Mayor, Xavier Trias, launched the project by creating a new
department called Urban Habitat. It combines urban planning, environment, ICT, transport, and
infrastructure. The first task was to expand existing outdoor Wi-Fi coverage, making it citywide.
The Barcelona Free Wi-Fi Network had to deliver a great user experience, all the time. So the city
decided to work with Cisco®. The network is being built in phases. The first phase is complete,
in Passeig de Born, the city’s historic Gothic area. Approximately 800 wireless access points
mounted on lampposts provide coverage everywhere in the area.
Already, quality of life has improved in four ways. First, residents and tourists can use their mobile
devices to browse the web, check email, or work. They can even stay connected on buses.
Second, city services are delivered more efficiently. City employees can make smart decisions
by gathering information from wireless sensors over the network. They can see temperature, air
quality, pedestrian traffic, open parking spaces, and more. Citizens can view some of the same
information from their smartphones.
Third, city planners have a better understanding of where people go and how they long they stay.
The Cisco Connected Mobile Experiences (CMX) solution counts the number of smartphones
and tablets in different areas to create color-coded maps. City planners use the location
information to plan development and transportation.
Finally, visitors enjoy new experiences that keep them coming back to the city. They can look up
today’s events on touchscreen kiosks at bus stop. They can find and reserve parking spaces from
their smartphones. When planning a picnic, they can check out air quality in different parts of the city.
Soon they’ll be able to receive personalized shopping offers on their smartphones as they pass
by stores.
Based on the enthusiastic response to Barcelona Free Wi-Fi, the City Council is expanding it to
more neighbourhoods. And more bus stops are being converted to smart bus stops with
touchscreen kiosks.

11.2.3 Results
The City of Barcelona’s Smart City projects have attracted attention around the world. The city
received the European Capital of Innovation (iCapital) prize for “introducing the use of new

© Dubai Design District, All rights reserved. Page 254 of 291

 technologies to bring the city closer to citizens1.”And CNNMoney named Mayor Xavier Trias one
of the world’s 50 greatest leaders2.
Improved Quality of Life
Getting around the city is easier now, and more fun:

 Connected Buses: Residents and visitors can stay connected while riding the bus, for
work or entertainment.
 Connected Bus Stops: Touchscreen monitors at certain bus stops provide up-to- date
bus schedules, maps, locations for borrowing city-owned bikes, and local businesses
and entertainment. “Smart bus stops change the typical experience of wasting your time
waiting for a bus,” says Sanroma. 

 Connected Parking: Studies show that 40 percent of traffic in city centres is caused by
drivers looking for a place to park. Finding parking is no longer a chore. The first of ten
districts now has embedded sensors in parking spaces. Residents can install a free map
application on their smartphone or tablet to see an available space, say, one block
ahead. Then they just tap to reserve the space until they arrive, and pay the fee with the
same application. As they linger over dinner, they can renew without having to walk back
to their car. “Putting sensors in parking spots results in less traffic,” Vives says. “This
makes the city more liveable, and makes people happier.” 


More Efficient Government Services

The City Council is taking advantage of the Wi-Fi network to work more efficiently:

 Smart Parking: The sensors in parking spots send an alert to city officials when the
meter expires. Parking revenues are expected to increase. Later the city might introduce
variable parking fees based on demand.
 Smart Waste Management: Sending trucks to empty trash containers before they are full
increases costs and carbon emissions. But waiting too long can make neighbourhoods
unsightly and endanger public health. Now the city is conducting a pilot to make
collection routes more efficient. Wireless sensors on trash containers indicate how full
they are. The collection company sends the drivers to the fullest containers first. The
application also shows the temperature in different areas of the city, valuable information
for route planning on hot days. When the program is used citywide, the City Council
expects to save 10 percent on waste collection. That will free up tens of thousands of
dollars annually for other city services.
 Smart Street Lighting: Keeping lights off in daylight hours lowers energy bills. And
making sure lights come on when it’s dark helps to create a safer environment. The City
Council lowered energy bills by installing LED streetlights that employees control over
the Barcelona Free Wi-Fi network. Smart street lighting is expected to save US$47
million over 10 years. The estimate includes lower energy bills, lower costs for LED
lighting, and less labour replacing the lights because they last longer.
 Smart City Planning: Now city planners understand where people go and how they get
there. This insight helps them create smart bus schedules that keep residents happy.
They also know where to assign foot patrol officers so that visitors feel safe.

Boost for Local Merchants, from New Retail Experiences

During the Internet of Things (IoT) World Forum held in Barcelona in October 2013, a Cisco
partner demonstrated a smartphone application that creates new retail experiences. As you pass
by restaurants and stores, you see “digital graffiti” on your device, such as coupons or specials.
To encourage retailers and advertisers to participate, the city plans to share revenues. 


© Dubai Design District, All rights reserved. Page 255 of 291

 Economic Development
The City Council estimates that smart buses will create $28 million in value over 10 years. That
total includes advertising revenues, increased ridership, and more spending by riders once they
arrive at their destination. Similarly, smart parking will generate an expected $53 million, from
better enforcement of parking limits and variable pricing.
Revitalization has made the city more attractive to new businesses. City leaders expect that
boosting Barcelona’s liveability ranking will help to attract 1500 new startup companies, creating
an estimated 44,000 new jobs.

11.2.4 Technical Implementation

Connected Buses: In the pilot, Cisco wireless access points on buses connect to ruggedized
Cisco switches. The switches provide power over Ethernet. A Cisco router aboard the bus, built
to withstand shock and vibration, connects to the LTE cellular network. Passengers can keep
their connection even when the vehicle enters a new wireless coverage zone.
Environmental Monitoring: If you wanted to catch up on email at the IoT World Forum in 2013,
you could open a browser application to view a map showing the lightest, quietest locations. The
data, collected by Smart Citizen Kits from Barcelona FabLab, was “crowd sourced.” Kits in
conference rooms measured applause, showing audience appreciation. People who took tours
of Barcelona’s Smart City projects wore other kits on necklaces. Cisco CMX noted the location of
the kit and superimposed the sensor readings on maps of the venue.

© Dubai Design District, All rights reserved. Page 256 of 291

 11.3 Mississauga, Canada
Transforming to an engaged and connected city
The City of Mississauga leverages the Internet of Everything to improve services, reduce costs,
and drive efficiency with real-time data.
“The Internet of Everything provides tangible service improvements and actionable information
that we can use every day to deliver and improve our services.”
- Shawn Slack, Director Information Technology and Chief Information Officer,
City of Mississauga
Your city is growing. Budgets aren’t. You can view ICT as a cost centre, or connect systems,
people, and processes to drive efficiency. What do you do?

11.3.1 Challenges:
 Provide open and accessible government
 Enable decisions through research and analytics
 Create a connected and engaged workforce
 Improve services through innovation

Economic opportunity and a reputation as “Canada’s safest city” have boosted the City of
Mississauga’s population to nearly 800,000 residents, and it’s growing fast. To support this
growth, Mississauga’s ICT strategy established goals to improve services and drive operational
efficiencies using the Internet of Everything—the intelligent connection of people, process, data,
and things.
“Just about every piece of equipment the city buys has the ability to connect to a wireless
network,” says Shawn Slack, director ICT and CIO. “Snowploughs, buses, fire trucks, HVAC units,
and traffic lights are all capable of transmitting real-time data. Collecting and using that data to
make better decisions will enable more responsive and efficient operations.”
The city is enhancing its Advanced Traffic Management System to make real-time traffic system
changes to reduce congestion and prioritize Transit and Emergency Response. In the future, this
will allow for prioritization of Snow Operations vehicles.

11.3.2 Solutions:
 Built a private fibre network using Cisco routing, switching, and security solutions
 Launched citywide wireless network using Cisco controllers and access points

The Internet of Everything gives us visibility across our people and systems.
Real-time decisions improve public service and public safety “The Internet of Everything enables
the collection of data from sensors and cameras, which can be used to improve and accelerate
service delivery,” says Slack. The results? Traffic can be monitored in real time allowing signal
and traffic movement changes in response to accidents, construction, or other issues. Flood-
response decisions can be made and public communications and operations can be put into
action immediately. All city operations field staff have mobile access to service work orders in the
field with real-time information access to enable quick and accurate maintenance decisions. In
the future, traffic signals could allow snowploughs to pass through intersections without stopping,
reducing service time, vehicle wear and tear, and fuel consumption.

© Dubai Design District, All rights reserved. Page 257 of 291

 More timely communication with the public in the past, the city was challenged to quickly notify
the public about road closures, storm damage, flooding, and other events. Now, it can post near
real-time updates to its website.
Supporting adoption of new technologies the city now has a formal BYOD policy and paperless
initiatives, supported by the 10GbE wireless network. City leaders and employees are becoming
more mobile. “Within the next few years, we’ll require less office space while exponentially
improving productivity,” says Slack.
Reducing costs through efficiencies
The Internet of Everything will help the city achieve service objectives and also drive efficiencies
and savings.
Partnering for success
The city will continue working with Cisco and OnX, a Cisco Gold Partner, for network design and
enhancements. “Cisco and OnX are extensions of our team,” says Slack. “They help us realize
the benefits of the Internet of Everything faster.”

11.3.3 Results
 Allows operations teams and emergency services to respond faster
 Enables new services while keeping ICT budget flat
 Improves public safety with immediately actionable information

Building the city of the future

The city plans to gradually add more sensors and devices to improve visibility, efficiency, and
management agility. “We’ll be able to automate certain field services, connect people with real-
time information, and introduce more self-service options via our website,” says Slack. “The
Internet of Everything is having a very positive business impact on our city.”

© Dubai Design District, All rights reserved. Page 258 of 291

 11.4 Rivas, Spain
11.4.1 The Rivas Digital City Project
The Project was launched in March 2004, and different stages have since been undertaken. The
starting point was a situation in which none of the city council buildings were interconnected. Each
building had to rely on an ADSL connection for data and connection to the public voice telephony
network. This meant that the Internet connection was very slow, the availability of systems was
very low and offered only minimum security, the cost of communications between municipal
offices was very high, and there was no capacity for controlling energy or water consumption.
There was also room for improvement in terms of access control at the offices in question. In
short, there was a long road ahead, but the support of the city's administrators, and the creation
of the Concejalía de Telecomunicaciones (Department of Telecommunications) made the launch
of the project possible. It was aimed not only at solving the problems experienced at that time,
but also at allowing future initiatives in the municipality to be supported without the need for
changes to the IP network platform.
The most suitable solutions were sought throughout, in each of the areas involved, so as to ensure
the success of the innovation project and the implementation of the new technologies throughout
the municipality. The city council subsequently extended this network to the Educational
Community, through the Rivas@duca project, which was to provide more than 14 secondary
schools and 2 primary schools with WiFi access and internet connections in all classrooms.
From a technological perspective, the project can be divided into the following blocks:
Data Processing Centres: The creation of a principal and backup Data Processing Centre has
allowed us to consolidate the municipal applications and databases, as well as the servers and
data storage facilities. Updating these systems entailed the optimisation of resources such as
servers, storage, software license management, integrity, security and the availability of data and
applications. From the point of view of the city's citizens, the process allowed us to offer our
services from any municipal building, improving response times and leading to a reduction in the
amount of investment needed in terms of equipment, by optimising the use of existing equipment.
Metropolitan Fibre Optic IP Network: One of the first activities entailed the interconnection of the
62 municipal offices using fibre optics and a Gigabit IP network. Each of the offices has Ethernet
network connections. The structure of the Multiservice network is such that it provides a high rate
of availability and very low latency, as well as a multicast platform for the reception of Rivas
TVNet.
Metropolitan WiFi and WiFi MESH IP Network: As a backup to the wired metropolitan network,
all municipal buildings have been provided with access to the network through a WiFi network
with a range of over 8 km2. Likewise, a WiFi MESH network has been deployed throughout the
municipality, in order to extend the network from the buildings to the streets and to allow municipal
employees to enjoy the same functionality inside and outside of municipal offices. Initial work is
also underway on the connection of all elements of the city that can be managed remotely to this
network (public lighting, irrigation of parks, street furniture, etc.). The platform for services based
on localisation (LBS) is already available. It will allow a new model of services to be deployed in
the near future, allowing access to applications by municipal employees through any WiFi device,
located anywhere within the city or in the active municipalities, through RFID.
Unified Communication System: The process of migrating the former conventional telephony
systems to a modern IP telephony platform is halfway in the municipality, allowing the integration
of multiple services in the platform. IP telephony, instant messaging (IM), voicemail, dual-band
GSM telephony, the TETRA radio system, an IP public announcement system and the 010 call
centre are operational and integrated. This means that any municipal employee (civil defence,
police, maintenance, sports, etc.), regardless of the type of terminal available to them and their

© Dubai Design District, All rights reserved. Page 259 of 291

 location within the city, can communicate with any of his/her colleagues, without worrying about
the type of device available to that person. It is also more economical, as all such communication
is internal.
Outdoor IP Video Surveillance: A video surveillance system has been deployed throughout the
city, for the control of traffic and adjacent zones. The cameras, using analogue and digital
technology, are providing the control centre with images through IP connections, wired or
wireless. This approach to video surveillance is permitting the much more rapid, economic and
efficient deployment of cameras wherever they are required within the municipality. In addition,
the control of the traffic light network is IP integrated, which, together with the cameras and
sensors fitted beneath footpaths, ensures more efficient management of the traffic circulating in
the city of Rivas.
“This commitment to technology began with the deployment of a physical infrastructure based
on single-mode fibre optics, with a Multiservice Network infrastructure. As we can see from the
diagrams, with the multitude of services implemented and yet to be deployed, and savings to be
made and improved efficiency in terms of energy, we have only just begun”.
D. Carlos Ventura Quilón, Director of the Department of Telecommunications.
Integral Security System: Rivas has decided to tackle security in municipal buildings in an integral
and integrated fashion, ensuring that every building has the following: access and attendance
control, visitor control, the generation of passes, CCTV, digital recording, anti-intrusion system,
interphone, watchman supervision and fire detection. This approach has provided the city council
with a centralised security management system, ensuring identical security measures in all
municipal offices, all of it integrated over the IP Network.
IP Automation of Building: One of the priorities of the Rivasecópolis project has been to improve
the use of energy and water resources. To this end, 10 municipal buildings are already equipped
with programmable logic controllers (PLCs) integrated in the IP network. Together with the
centralised SCADA system, the PLCs allow the management and operation in real time of all
processes used in buildings: air conditioning, lighting, water, power, gas, access control, public
lighting, equipment in sporting facilities, etc. This is leading to an improvement in the management
of buildings, a significant reduction in energy consumption, early detection of water or gas leaks
and malfunctions in any subsystems, among others. It is also bringing an improvement in the
efficiency of the buildings in question, a reduction in CO2 emissions and a decrease in the monthly
expenditure of the municipality. The process of incorporating the other municipal buildings into
this model is gradually being undertaken, as improvements are implemented. Apart from the 36
UPS, real time monitoring of breakdowns, alarms, etc., has also been implemented.
Traffic and Traffic Light Control: Regulation and control using the traffic light system meets the
dual objective of increasing road safety and optimising the cost of the production process.
Through the interconnection of the traffic light control system and the traffic optimisation network,
readings can be taken using statistical samples that relate total journey times, measured in terms
of the number of vehicles per hour. This system allows the efficiency of the regulation system to
be ascertained. It can be expected to increase as total journey times for a given capacity fall.
THE PROJECT IN FIGURES
 CURRENT SICTUATION AS AT AUGUST 2008
The city council belongs to the Community of Madrid, in Spain, and has a population of over
65,000 inhabitants. It covers an area of over 6,000 hectares, and 72% of its surface is occupied
by a protected natural area. Its population is very young, with more than 52% aged under 35
years, and 73.7% of the population has access to the Internet. It is located to the southeast of
Madrid, and is one of the most innovative municipalities in terms of the application of information
technologies and communication systems using IP technology.
The following data give an overview of what the project represents:

© Dubai Design District, All rights reserved. Page 260 of 291

  Municipal offices: 62
 Number of users/employees: 658 municipal users and 22 mixed companies, plus over
1,000 WiFi users in educational and cultural centres
 Buildings connected to the network: 62
 IP managed buildings: 10
WiFi MESH coverage: 8 km2
 IP telephone terminals: 640
 WiFi telephones: 22
010 Call Centre agents: 12
 VoIP terminals (analogue): 380
IP Communicators: 100
 42 Localisation tags PDAs for mobility: 50
 TETRA terminals: 330 + 15 in vehicles
 Dual-band GSM terminals: 45
 IP public address systems: 12 centres IPCCTV cameras: 20 VIPXI IP cameras, 52 VIPX
226 IP cameras and 80 5 Divar IP cameras. 359 cameras in total. WiFi access points:
more than 530 internal points
 WiFi MESH access points: 100
Access Control Points: 232 CPU access control and
more than 500 doors, card readers and access to car parks, among others.
 Traffic Light Control: more than 15 controlled traffic light centres, reducing Co2
emissions, etc.
 IP automation of lighting and climate: 280 data points

“Rivas Ecópolis will continue to grow gradually. In the coming years we will continue to implement
the plans set forth and the campaign to promote the dissemination of information and enhance
the visibility of results obtained, in order to improve awareness among citizens. To this end, the
Rivas Ecópolis will be based on environmental sustainability, citizen participation and new forms
of governance, in a new approach to three different aspects of the realities of modern living:
environmental science, citizenship and technology. Our aim is to ensure that every new project
should be developed in line with these new technologies”.
D. José Ramón Martínez – Coordinator of Rivas Ecópolis

11.4.2 Benefits
The principal benefits of the implementation of this project, based on an IP network platform as
an element of integration for all services, are the considerable reduction of all implementation
and maintenance costs, through the elimination of duplicate costs, thereby ensuring lower
overall costs for the network infrastructure, the simplification and reduction of administration and
maintenance costs, the optimisation of the cost of transferring extensions and line costs; rented
and commuted alike. Furthermore, unified IP networks with integrated voice, data and video
technology allow a wide range of applications to be installed, increasing productivity and
controlling consumption, offering high value added to the municipality and protecting
investments already made in future extensions and aimed at meeting the demand for new
services.

PROJECT BENEFICTS AND RETURN ON INVESTMENT

The establishment of this project and the improvement of services throughout the municipality of
Rivas Vaciamadrid have led to notable savings in investments.

 The energy efficiency programs have brought a saving of 35% and more than 1200 tons
per annum in energy consumption, and more than 1800 tons in air conditioning.
 A reduction of more than 3000 tons in CO2 emissions, thanks to traffic light control.

© Dubai Design District, All rights reserved. Page 261 of 291

  A reduction in the cost of telephone and other online services has led to savings of 50%,
or 300,000 Euros per annum for Telephony and Communications.
 The implementation of the new network infrastructure has resulted in savings of 50% on
global costs.
 The savings made in the municipality in terms of communications, water consumption,
lighting, the optimization of services to the citizen have been significant. In fact, it is not
unreasonable to say that expenditure in the municipality is currently the same as in
2005; the difference is that many more services are being offered, while the payroll of
the municipality has grown by around 50%.

FUTURE PLAN FOR EXPANSION AND THE DEVELOPMENT OF NEW SERVICES

The municipality is refusing to conform to traditional methods. It is constantly in search of
innovation in all of its activities. To this end, IP management systems will be provided for all
remaining buildings, covering technical services, inventory and the control of the municipality's
street furniture, as well as the remodelling and centralisation of management of all public lighting,
the regulation of light intensity in order to reduce costs, and referencing and documenting all
municipal archives and the software for object management.
The meshed network will be used as a means of communication for water meters and automatic
irrigation systems, the waste collection system, ascertaining whether itineraries have been
properly observed, internet for local buses, pollen levels in the city, pollution, etc...
 Future
buildings will be fitted with the latest technology from the start, as these projects already include
the specifications of all of the subsystems described above, to be executed during construction.
Rivas Digital 21.10 is seeking to bring about the increase in quality required for all administration.
CICTs are here to stay, and we need to seize the opportunities they offer, in order to ensure that
the benefits are enjoyed by all citizens, without exceptions. The involvement of social and
economic agents and the participation of citizens in the affairs of the city council are fundamental
to the success of this project”.
D. Marcos Sanz – Councillor for Territorial Policy, Public Works and Infrastructures and
Telecommunications

© Dubai Design District, All rights reserved. Page 262 of 291

 11.5 Songdo, South Korea
11.5.1 Business Need
 Ambitious urban development project in South Korea
 Desire to build a true Smart Connected City
 Need for environmental economic and social sustainability
 Give residents flexible access to information and services in their homes, school,
workplace and transportation
 Enhance the quality of life

11.5.2 Solution
All systems connected through IP network including:

 Security cameras
 HVAC
 Elevators
 Lighting
 Transportation
 ICT systems in the city and the community

11.5.3 Benefits
 Resident can experience life in a connected city at home work school
 First world, the first residential complex completed at Songdo sold out all of their 1596
units in the same week they went on sale
 All home systems accessible on one panel through mobile devices
 All residents also accessible through in-units panels or smart mobile devices such as
cell phones
 Connected services in work environment. Ability to management systems from central
location and connect many location through video conference

© Dubai Design District, All rights reserved. Page 263 of 291

 11.6 Amsterdam
Amsterdam built a broadband platform for service delivery to achieve social, economic, and
environmental sustainability.

11.6.1 Challenges
 Meet aggressive sustainability goals for reducing energy usage and CO2 
 emissions
 Create environment attractive to residents and businesses for economic sustainability
 Reduce city costs

11.6.2 Solution
 A citywide broadband network creates the foundation for widespread connectivity for
more than 140,000 homes and businesses
 A network of Smart Work Centres help reduce or eliminate commuting while enabling
workers to access their full corporate resources

11.6.3 Benefits
 Reduced office space by 40 percent, saving 10 million Euros in leasing 
 costs alone
 Eliminated equivalent of 3428 tons of CO2
 Launched pilot projects spanning smart work centres, healthcare, smart living, mobility,
and sustainability services

© Dubai Design District, All rights reserved. Page 264 of 291

 11.7 Guldborgsund
With a population of more than 63,000, Guldborgsund is southeast of Copenhagen and includes
six municipalities, covering approximately 900 km2.

11.7.1 Challenges
 Government services needed to cover a large geography and six municipalities
 Difficulty in providing services locally to all residents
 Needed to reduce costs while retaining connection with residents and local presence

11.7.2 Solution
 Cisco Remote Expert Smart Solution for Government Services in five locations

11.7.3 Benefits
 Expertise available to all residents at multiple local services centres
 Maintained service levels, while reducing headcount, travel, and transport expenses
 Residents are enthusiastic about service quality and how it is delivered

© Dubai Design District, All rights reserved. Page 265 of 291

 11.8 City of Nice
The Cote d’Azure has 1.3 million inhabitants in 42 cities spread throughout the French Riviera.
Nice is the fifth largest city in France, with 535,000 inhabitants.

11.8.1 Challenges
 Wanted to develop a new government model and sustainable city reference, while
embracing ICT as part of the solution
 Needed to improve public services for local residences while bringing administrative
services close to the community

11.8.2 Solution
 • Cisco Remote Expert Smart Solution for Government Services installed in a
 local shopping mall (called "SPOT MAIRIE")

11.8.3 Benefits
 More than 30 services available to residents
 Improved customer service through face-to-face contact with an agent as well as
extended hours (same as mall hours)
 Residents claim it is easy to use, immediate, and a better experience than a phone-
based solution
 Agents state they can provide wider and more in-depth services to residents

© Dubai Design District, All rights reserved. Page 266 of 291

 11.9 Delhi Mumbai Industrial Corridor
The Delhi-Mumbai Industrial Corridor Project is an ambitious project aimed at developing
industrial zones spanning across six states in India which will spur economic development in the
region and support the growth of new and existing industries.

11.9.1 Challenges
 US$90 billion mega infrastructure project spanning 6 Indian states and 436,486 square
kilometres
 1,483 Km high-speed dedicated railway and 6 lane highway across 6 states and 24
cities, 4,000 MW power plant, 3 seaports, 6 airports, and additional connectivity with the
existing ports

11.9.2 Solution
 Develop a portfolio of Smart+Connected public and private services for 2 cities in Phase
1 and 2 cities in Phase 2
 Designed the converged digital infrastructure, and a viable service operating model and
financial model to enable the affordable and realistic provisioning of services to all
sections

11.9.3 Benefits
 Inclusive growth key to sustainable development
 Doubled employment potential, tripling industrial output, and quadrupling exports from
the region over five years

© Dubai Design District, All rights reserved. Page 267 of 291

 11.10 King Abdullah Economic City (KAEC)
As part of an ambitious program to elevate Saudi Arabia’s place as an investment destination,
KAEC will help diversify the oil- based economy by bringing direct foreign investments, and create
up to one million jobs for the young population (40% of whom are under 15).

11.10.1 Challenges
 KAEC is in the Western Region of Saudi Arabia 168 sq. km. 

 Green-field development comprised of sea port, industrial park, central business district,
educational district, residential zones and resorts 

 Phase 1 development is 16 square kilometres of the MEGA City

11.10.2 Solution
 Engage Cisco Advisory Services to design a Smart City with the network as the platform
to enable and deliver the Smart City services
 Develop a prioritized list of smart services, and a corresponding financial model and
business case to attract investors

11.10.3 Benefits
 Development of a portfolio of Smart City services providing an improved user
experience, increased revenue, reductions in operating costs, and enhanced safety and
security
 The Smart City features serve to attract new businesses, create jobs and encourage
residents to locate in the City

© Dubai Design District, All rights reserved. Page 268 of 291

 12 Case Study with quantitative analysis
Wells Fargo’s Corporate Properties Group

12.1 Executive Summary

In 2010, Wells Fargo & Co. completed what would soon be called one of the smartest buildings
in America by re-evaluating the decades-old development approach. The Duke Energy Centre
(DEC) is a 1.5 million square foot, 48 story multi-tenant office tower that is headquarters for Duke
Energy Corporation and serves multiple tenants including Wells Fargo, KPMG, Deloitte and
others.
The bank and its predecessor, Wachovia Corporation, set out to make this building the measure
for a modern, sustainable and operationally cost-efficient building while creating a next generation
occupant experience. They realized that in order to accomplish this, they could not build and
manage it in the traditional way. However, it still had to be on time and on budget, and efforts to
change the process would face the ultimate financial and risk evaluation during the height of the
economic crisis. This scrutiny was compounded by the substantial cultural resistance to change
in the real estate and construction industry.
The bank and its project partners--Childress Klein Properties, Intelligent Buildings, LLC and Cisco
Systems--upended “construction-as-usual” and worked with 16 different building systems controls
companies to groom all of them onto a common Cisco backbone and empower a new way of
managing the building. This approach would set the building ahead of its peer buildings in multiple
measurable ways, which included:

 Reduced capital and operational cost structure

 Mitigated change order, schedule and operational risks
 Simplified building management
 Built in scalability, reliability and flexibility
 Improved occupant experience and choices

Even with the inclusion of these powerful benefits, the physical changes in the building itself were
minor, affecting only the method that control systems connect vertically between floors, while also
reducing the number of connections to the main server. Ultimately, the changes not only saved
capital expenses, but also resulted in less than 0.5% of the project cost.

12.1.1 Building Highlights

 1.5 MM square feet, 48 stories with 23 acres of below-grade parking
 Multi-tenant office tower that serves as headquarters for Duke Energy Corporation and
other Fortune 500 Corporations
 Owner: Wells Fargo & Co

12.1.2 Challenge
 Reduce risks from building technology changes with current-day approach
 Build in long term cost-efficiency and flexibility for property management and occupants
 Budget, schedule and contracts already set

© Dubai Design District, All rights reserved. Page 269 of 291

 12.1.3 Solution
 Eliminate overlapping, disparate ICT cabling and networking with single backbone
 Require controls contractors to focus on core strengths and leverage backbone for
connectivity
 Continuously commission and adapt to experience and operational cost requirements

12.1.4 Results
 22 percent reduction in energy costs, almost $700,000 lower capital expense, and lower
risk
 Superior tenant experience, control and satisfaction
 Complete system interoperability without compromising independent functionality and
service

12.2 Background
Bob Bertges, Executive Vice President in Wells Fargo’s Corporate Properties Group, sought to
use the development of the Duke Energy Centre to create a new model for future development
and operations that raised the bar not only for Wells Fargo, but for the entire industry. Curt Radkin,
Senior Vice President and Sustainability Strategist for Wells Fargo Corporate Properties Group,
was the executive in charge of developing the building, leading the new process and making the
critical decisions to change from the old development approach.
"There is no more rigid industry segment than real estate development, so we knew even though
we were driving the process, we could meet resistance at many points along the way, both
internally and externally. This is a decades-old process and culture that resists change despite
technology and the economy."
- Curt Radkin, SVP Wells Fargo Corporate Properties
With the property being on a fast track, most major building systems and design had already been
determined in early schematic and design development. The building itself was already 14 stories
completed from bedrock when the intense "smart building" evaluation began. While somewhat
late in the process, it was nevertheless helpful to have real numbers for comparison of any
potential changes, given a schedule that was already firm. Potential design and construction
tweaks would have to be cost and schedule neutral or better.
Under Wells Fargo leadership, Intelligent Buildings developed the strategy and technology
standards, along with the risk and financial analysis for the new design. Intelligent Buildings also
developed and supported the value proposition and business case for the controls contractors.
Childress Klein validated the impact on construction budget, schedule, and future operations, as
well as oversaw any changes on site. As both the developer and the property management
company, Childress Klein was able to credibly determine both the job site issues and the life cycle
impact. Cisco Systems provided real estate networking expertise, design and solutions for all
building system connectivity requirements.
At this juncture, the team determined that the controls systems such as HVAC, lighting, security,
metering and others would have the most impact on operational costs and would also share
common ICT characteristics. However, since the building was already out of the ground, this
meant that vendors and controls manufacturers had been selected and contracts had been let.
Thus the contractors would need to agree that the changes would be as good for them as they
would be for Wells Fargo. Like the recession itself, working with vendors already under contract
would also prove to be a tall test of any change from the legacy approach.

© Dubai Design District, All rights reserved. Page 270 of 291

 12.3 Common Characteristics
Wells Fargo, Intelligent Buildings, LLC and Childress Klein observed that the building controls
systems for the DEC such as HVAC, lighting, metering, elevators etc. had all changed significantly
in recent years and now utilized nearly identical information technology networking as part of their
basic functional requirements. Hence, the traditional plans showed multiple, overlapping,
redundant infrastructure including conduit, cable, networks, servers etc. Additionally, the ICT
infrastructures varied in design, level of security and quality. The disparate network problem was
due to the older divisional design and development process and thinking.
The ICT requirements of such separated systems show a consistent trend in the controls
manufacture marketplace that has forced developers, managers and the support vendors to take
on a growing amount of ICT responsibility in design, development and operations.
An example of the ICT nature of controls systems is Lutron lighting controls solutions, which now
include a prescriptive option and documentation for “Ethernet by Others” indicating that their
system can be “plugged in” to a building backbone shared by other systems. Their system
requires ICT connectivity as a commodity point-to-point communications function but it is not
important that Lutron self-perform something that is not their core business or skill set. This also
reflects Lutron’s awareness of the broader strategic realities for owners and managers and their
willingness to partner with companies like Cisco for seamless networking and interoperability.
As a similar example, the Siemens building automation system required connectivity of all floor-
level controllers and the master server at the base of the building. However, that large networking
design, implementation and management was only a requirement for the system and not part of
the HVAC and mechanical controls functionality. They were clear that the system only needed
secure, reliable networking and nothing proprietary to the controls system.
This held true for the elevator system, daylight harvesting, water reclamation, parking, barrier
gate, exterior lighting, security and other systems as well.

12.4 Risks
This shift in domain expertise requirements (ICT networking necessary for all controls systems)
has far outpaced the capabilities of traditional design, construction and operations practices and
support services. Supporting traditional controls systems through the implementation of
substandard, disparate and incompatible networks can create a variety of risks for owners and
managers: increases in maintenance expenses, operational costs, and capital costs for future
add-ons, the risk of more system down time, and an inability for systems to work together.
Understanding this, Wells Fargo was able to react with a quick shift in planning that would redefine
how they now approach design changes, construction and management processes for building
technologies. Childress Klein was equal to the change task, working with Intelligent Buildings,
LLC, to creatively engage property management and ICT staff in the development process. By
doing so, they added critical ICT capabilities while maintaining sensitivity to all of the downstream
operational impacts.

12.5 Solution
The new design approach centred on helping controls contractors (for the aforementioned
systems HVAC, lighting, elevator, metering, security, etc.) remain focused on their skill sets, while
allowing the ICT networking experts to focus on the controls contractors' ICT networking systems
aspects. As such, Cisco Systems was called upon to design and install a building-grade backbone
network as part of their “Smart + Connected” real estate solution. The Cisco solution would be
accompanied by open communications protocols and the Tridium middleware product that in
combination would lower maintenance costs and enable easier interoperability.

© Dubai Design District, All rights reserved. Page 271 of 291

 All of the 16 controls systems companies agreed that a neutral, secure backbone was the most
reliable, flexible approach for the owner and that it would not compromise their performance,
profit, warranties or service quality. Cisco ensured that all connectivity requirements would be
met and network performance would exceed any individual system need, while staying within the
planned cost of each system’s separate infrastructures. The Cisco backbone leverages air blown
fibre optic lines, along with copper cabling, flexible patch panels and secure enclosures for all
equipment and terminations.
This neutral, standards-based backbone accommodates a myriad of systems regardless of
manufacturer or type. Vendors will only need to be able to connect to a standard office-type
network similar to ones that allow for printer sharing, email and Internet access in any standard
office environment. This approach is increasingly common practice and has been endorsed by
most major controls systems manufacturers in HVAC, lighting, security, video surveillance,
parking and others.
"In my view, I perceive the converged network as far more reliable than the sum of the reliability
of the non-converged networks."
- Jim Patterson, Regional Director of Facility Management, CKP

12.6 Results
12.6.1 Vendor Impact
The controls systems contractors and manufacturers all complied with the solution albeit for
different reasons. Some were anxious about cost or schedule overruns, yet prepared because
they understood the realities of ICT. Others were willing to make the systems change since ICT
was not core to their value. Still others were relieved since ICT networking exceeded their internal
capabilities. In every case, they were able to provide a cost deduct for their now unnecessary
networking, validate warranties, and service their systems both remotely and onsite.
A converged building network did not change what contractors and manufacturers do as their
core competency. In other words Cisco would not design, sell or service elevators, chillers,
boilers, lighting systems, parking systems or electrical metering. Rather, those vendors made a
very slight adjustment in their design and installation to exclude the non-core aspects of their
product that relate to ICT. For example, when installing HVAC controls systems there is vertical
connectivity between floor-level controllers down to servers - all of which are commodity ICT
connectivity linking “Point A” to “Point B” and initially have no impact on the functionality and
control of the system.
Representatives quote and comments as follows:
“We were encouraged and inspired by the process at the Duke Energy Centre. This helped us
move more affirmatively towards the reality that every system, including ours, does not need a
silo’d infrastructure. We have responded to this by institutionalizing this as an option for any of
our clients. Whether you have 16,000 ballasts that are all addressable and dimmable-- like the
Duke Energy Centre -- or a smaller number, the information technology realities have forever
changed the way controls systems will be designed, installed and managed.”
- Brian Daskurdus, Director Global Energy Lutron Lighting Controls
"We are experts in building automation and energy solutions for some of the largest and most
complex buildings in the world. Our systems, like nearly all other building automation systems,
require servers and vertical networking for connectivity and functionality. With a reliable, secure
Cisco network, we were able to stay focused on our core business and simply leverage the
connectivity on each floor for communication between the many different integrated components
of our system."

© Dubai Design District, All rights reserved. Page 272 of 291

 - Brian Beebe, Area Manager Siemens Industry, Inc.
“It is clear to us that common ICT infrastructure is the current-day approach to design,
development and management of buildings. Our Niagara Framework is the essence of
convergence at a device and protocol level so a network backbone is natural and efficient for our
solution, as well as the entire building. This combination lowers operational cost and enhances
the occupant experience.”
- Mark Petock, Global VP Marketing Tridium Corporation

12.6.2 Operational Impact

The operational impact was immediate and ongoing because of the standards, open protocols,
scalability and flexibility introduced by the change in systems approach. Each of the floors has
the same technology configuration right down to the fabricated metal enclosures which helps
managers keep order and manage vendor policy. Since each system is linked through the
network and software, the building can continuously adapt to new experience desires or
operational cost issues. Secure remote access means that vendors can more easily service and
update systems and property managers can monitor and adjust systems from anywhere.
Leveraging ICT staff to ensure proper design, installation and management greatly increases
building system reliability and service issue resolution by eliminating a complex variable.
Additionally, management staff will have more service options in the future, longer system life and
lower service costs due to the elimination of proprietary vendor protocols and service contracts.

12.6.3 Financial Impact

The financial impact during construction was minimal. Ultimately the areas under consideration
for change, which were building systems controls networking, represented less than 0.5% of the
project cost. Nevertheless, the project saved almost $700,000 (see Appendix A) by eliminating
16 disparate networks and implementing one reliable, robust, secure backbone even when having
to request deducts after contract awards. This has lowered the capital cost structure of all future
system additions or enhancements since these systems will only need to plug into the existing
backbone for full building connectivity and access.
The interoperability and control gained have allowed the building to continuously reduce energy
and operational costs. For example, Wells Fargo/Childress Klein Properties conducted a detailed
lighting control study on seven Wells Fargo floors and through control changes and output
trimming have realized additional 20-25% energy efficiency from the lighting system. This
reduction will produce energy savings of $1,100 per year or over $60,000 per year if implemented
throughout the building. Results of this study are being shared with other tenants in the building
in hopes of driving lighting energy efficiencies on all floors.
The building is now preparing for continuous commissioning analytics allowing it to lock in savings
and participate in utility demand response load shedding programs. Easy Access to data and
granular control of every system are essential to these benefits.

© Dubai Design District, All rights reserved. Page 273 of 291

 Figure 12-1: Summary of Construction Budget

[Link].1 Environmental Sustainability

In addition to overall financial and operational benefits, convergence efficiencies along with other
design features provide environmental sustainability results that contributed to its LEED Platinum
status.

[Link] Conclusion
The trends for real estate development and management include controlling systems of all types,
such as HVAC, lighting, security, metering, and elevators, with converged network connectivity.
This approach presents both risk and opportunities to owners and managers. Most important is
to then acknowledge and plan around the risk/opportunity reality as well as the limitations of the

© Dubai Design District, All rights reserved. Page 274 of 291

 traditional support vendors. Doing so will prevent the predictable rise in maintenance and
operational expenses, help better manage energy and utility costs, improve rentable space and
order in the reduction of closets and mechanical spaces, and reduce risk of extended downtime
and finger pointing when multiple vendors manage multiple networks.
Convergence of building systems onto a single network presents an opportunity to create
interoperability inside the building and more dynamic interaction with electrical grid and other
major utilities as well as creating a “data driven” building. In the world of “big data”, the real estate
industry and our individual buildings have significant opportunity to capture, analyse and act on
data as a profound low-cost, high value way of driving down operational costs.

Figure 12-2: Total Cost Savings

© Dubai Design District, All rights reserved. Page 275 of 291

 12.7 Cisco Bangalore Building 14 (Banyan)
12.7.1 Background
Cisco Smart+Connected Communities offers a solution by using intelligent networking capabilities
to weave together people, services, community assets, and information into a single pervasive
solution. Constituents of Smart+Connected Communities have access to information and
services, with solutions for their home, schools, transportation, and more. “Smart+Connected”
leverages the network as the platform to help transform physical communities to connected
communities.
Booz & Company is a thought leader in the use of ICT for smarter and efficient urbanization.
Consequently, Cisco requested Booz & Company to conduct an independent examination of a
pilot implementation of S+CC. Cisco chose Building-14 (christened "Banyan") in its Globalization
East campus in Bangalore, India for a pilot implementation of the S+CC concept. The
implementation comprised of the in-building component of the S+CC offering - Smart +
Connected Real Estate (S+CRE).

12.7.2 Banyan - S+CC Pilot Implementation

Cisco chose Building-14 (christened "Banyan") in its Globalization East campus in Bangalore,
India for a pilot implementation of the S+CC concept. The implementation comprised of the in-
building component of the S+CC offering - Smart + Connected Real Estate (S+CRE).
The S+CC implementation in Banyan has three components:

 Community+Connect leverages real-time information and applications to provide a

comprehensive set of in-building services for a safer, healthier, more sustainable work
environment. This can span to a wide variety of ubiquitous services including healthcare,
education, government, etc. for residents and businesses in a connected community.
 Community+Exchange is a back-office operations centre that helps with the day-today
operations and management of Banyan. In a larger community, this solution scales to
enable information sharing and collaboration across a community’s ecosystem of
government agencies and private sector partners.
 Both Community+Connect and Community+Exchange are facilitated by the underlying
Cisco Service Delivery Platform (SDP). The SDP consists of advice and infrastructure
layer that enables Cisco and non-Cisco devices to interact with one another once
connected over IP, a services layer that provides end users with an easy-to-use, intuitive
interface of service offerings, and a middleware or platform layer that connects all the
different smart and non-smart devices (Cisco and third party applications) to the network
in a standardized, open way.

Booz & Company has conducted a review of the benefits of the S+CC solutions implemented in
Banyan. Our review indicates that the Banyan implementation presents the potential for benefits
across the "triple bottom line": economic, environmental and social benefits:

12.7.3 Economic Benefits

Economic benefits accrue in the form of reduced building lifecycle costs. In Cisco's Building-14,
S+CRE has shown the potential to reduce annual operating costs by 10% to 15% driven by lower
energy consumption and efficient building management.

© Dubai Design District, All rights reserved. Page 276 of 291

 Figure 12-3: Connected Real Estate Break Even

S+CRE connects HVAC and other devices over IP. This allows the operator to dynamically alter
building operating parameters based on occupancy, environmental and other considerations. For
example, an operator can automatically adjust temperature and switch off lights during
unoccupied hours based meeting room bookings within the ICT system. These features can
contribute to ~8 to 10% reduction in energy consumption.
Efficient facilities management also contributes significantly to savings realization. Cisco's Energy
Dashboard allows real-time trending and analysis of system performance, thereby enabling early
detection of faults and anomalies. Although the building data had not stabilized enough for Booz
& Company to gauge this saving.
Based on actual performance, we believe that this solution could result an additional 4% to 5%
reduction in annual energy consumption. Automation also enables reduction in number of
technical staff, leading to further savings.
Further economic benefits exist in the form of increased equipment life to the tune of 20 to 25%
due to lower usage.

© Dubai Design District, All rights reserved. Page 277 of 291

 Figure 12-4: Typical Cost Reduction by using Convergence

12.7.4 Environmental Benefits

Reduced energy use leads to reduction in GHG emissions. Based on estimates of GHG intensity
of electricity fed to Banyan, a ~26% reduction in Carbon Dioxide emissions is possible. Savings
from automated detection of pipe leaks, dripping taps, taps left running, running toilets etc. could
reduce Banyan water consumption, potentially to the tune of ~10%.
Cisco's "Green Aware" uses S+CRE technologies to gather, analyse and display real time
building energy use data on digital signage across the facility. This enhances employee
understanding of the solutions operating in Banyan. A large proportion of Banyan occupants are
aware of the environmental friendly initiatives underway at the Cisco campus, and over 80%
attributed their environmental friendly behaviour to this enhanced awareness.

12.7.5 Social Benefits

Much has been written about the intangible benefits of green/intelligent buildings. Use of day light
harvesting, outdoor views, better temperature and lighting, and improved work environment
contribute to staff productivity and sense of well-being.
Rigorous studies conducted by ASHRAE indicate a 5-7% productivity gain due to better
environmental controls. In order to validate this, Booz & Company interviewed employees in
Banyan regarding their perception of the work environment Banyan provides, and its potential
impact on productivity. The findings were encouraging:
67% of the interviewed occupants indicated productivity gains of >5% compared to their previous
work space (modern however non-intelligent buildings). While this is not conclusive, it is certainly
indicative of the value driven by social benefits and staff productivity gains that provide a
significant upside to the benefits case.

© Dubai Design District, All rights reserved. Page 278 of 291

 In summary, tangible benefits exist. Our analysis indicates a breakeven timeframe of 7- 10 years1
purely based on economic savings. Inclusion of productivity benefits can significantly accelerate
breakeven. Assuming conservative productivity gains of 5% based on ASHRAE benchmarks,
breakeven can occur in the first year of implementation.

12.7.6 In Conclusion
Urbanization as a phenomenon is inevitable. The methods adopted by developed economies
today lead us down an environmentally unsustainable path. S+CC not only provides a model for
a low carbon lifestyle but also makes economic sense. Solutions implemented in Banyan have
demonstrated the potential of reducing annual operational expenditure by 10 to 15%. However,
S+CC should not be looked at in isolation from intangible benefits it can deliver. Banyan
implementation indicates that communities using the network as the platform to plan, build, and
manage day-to-day operations will gain significant new efficiencies in every aspect of community
life: enhancing productivity among residents / employees, and improving availability and access
to public services. While pure economic benefits yield a 7-10 year break-even, including
productivity benefits makes a very attractive case. Implementation requires aligning incentives for
stakeholders, increasing awareness and adopting new business models.

Figure 12-5: Comparative view of validated savings

© Dubai Design District, All rights reserved. Page 279 of 291

 13 Smart Services Mapping To Endpoints
Systems
The 45 Smart services presented in the Services Catalogue by prepared by d3 Smart City Team
can be mapped into three generic categories of systems that have endpoints:

 In-Building Systems: These systems are restricted within the buildings. These can be
provided to the Contractors who are responsible for the construction of the buildings.
These can be private developers of d3 appointed contractors for the buildings
constructed by d3
 City Wet Systems: These systems are responsible for Municipal services that are
necessary within the district in the public areas and most of the times have an impact on
the service corridors. These services, most of the time, are responsibility of the City
Developer and or Service Provider’s System: These systems are relevant for the Smart
Services and are very important from the Smart City Services Perspective.

This table also shows which of the services needs end points for deployment in addition to the
back end applications. Ones that don’t need end points can be delivered by the backend system
in the Data Centre. The table show the integration required in case any of the service need more
than one technology platform to provide that service.
In-Building Systems City Wet City Other Systems
Systems

El. Vehicle Charging Station

Digital Signage and Kiosks
Endpoint Required (Y/N)

Multi-Function Sensors
Car Parking System
Video Surveillance

Weather Station

Vehicle Tracking
Lighting Control

Connected Bus
Access Control

Water System
HVAC Control

Garbage Bins
Storm Water

Lighting Pole
Audio/Video

Smart Home
Point of Sale
Solar Panels

Traffic Light

Bus Shelter
Metering

Irrigation

Sewage
Service
Ref

x
Advanced Parking
Management

Yes
1

x x
Management
Visitor

Yes
2

© Dubai Design District, All rights reserved. Page 280 of 291

 7 6 5 4 3
Energy Analytic System BIM based facility Intelligent Transport System Smart roads, bridges and Traffic
Optimization management tunnels infrastructure Management

No No Yes Yes Yes

© Dubai Design District, All rights reserved.

x

x
x

x
x

Page 281 of 291

 13 12 11 10 9 8
Digital Integrated Tenant On Technology Experience Operation and Maintenance Extended Privileges Personal Dashboard
Credential Boarding System Showcase Enhancement

No No Yes No No No

x
x

© Dubai Design District, All rights reserved.

x
x
x
x
x
x
x
x
x x
x
x
x
x
x
x
x
x
x
x
x

Page 282 of 291

x
 20 19 18 17 16 15 14
Waste Management Storm Water Sewage Smart Irrigation Incentivized Recycling Network Enabled Electric
Management Water Water Program Utility Metering Vehicle
Power
Yes Yes Yes Yes No Yes Yes
and
Charging

© Dubai Design District, All rights reserved.

x

x
x

x
x

Page 283 of 291

 25 24 23 22 21
Consolidated Personal BIM/GIS based integrated Water Management Role Based Energy Smart Lighting Pole
Control digital experience Management

Yes No Yes No Yes

x
x

© Dubai Design District, All rights reserved.

x
x
x

Page 284 of 291

 30 29 28 27 26
Smart Home Visual Communication Integrated Building Security Service Community Information
(digital signs) Management System Integration Services and Portal

Yes Yes No No No

© Dubai Design District, All rights reserved.

x

Page 285 of 291

 36 35 34 33 32 31
Digital Shared Resources Location Analytics Wi-Fi Connect Way finding mobile Interactive Services
Wallet/Cashless (People Counting) app (kiosks)
Payment
Yes Yes No No No Yes

© Dubai Design District, All rights reserved.

x
x
x

Page 286 of 291

 42 41 40 39 38 37
Connected Bus Solar Roofs Building Information d3 Augmented Reality Loyalty program Targeted Advertising
Modelling Tour

Yes Yes No No No No

© Dubai Design District, All rights reserved.

x
x
x

Page 287 of 291

x
 x x x
Smart Bus Shelter

Yes
43
Autonomous Cars

No
44

x x
Smart Working
Spaces

Yes
45

Table 13-1: List of Smart Services; their categorization and integration map

© Dubai Design District, All rights reserved. Page 288 of 291

 14 Glossary
d3 Dubai Design District
DCP Delivery Collaboration Portal
ICT Information and Communications Technology
KPIs Key Performance Indicators
PD Project Director
PM Project Manager
S+CC Smart Connected Communities
SME Subject Matter Expert
TBC To Be Confirmed

© Dubai Design District, All rights reserved. Page 289 of 291

 This communication contains general guidelines only, and none of Dubai Design District FZ-LLC,
TECOM Investments FZ-LLC, its member firms, or their related entities (collectively, the “d3
network”) is, by means of this communication, rendering professional advice or services. No entity
in the d3 network shall be responsible for any loss whatsoever sustained by any person who
relies on this communication.

ABOUT Dubai Design District

Dubai Design District, (d3), one of the TECOM Group’s communities, is a destination dedicated
to design. The chosen home for the region’s growing collective of creatives, artists and designers,
d3, has fast become the hub for inspiration and innovation. Created to answer the growing need
from the industry, d3 provides businesses, entrepreneurs and individuals from across the design
value chain with a thriving community where they can collaborate, create and inspire.

ABOUT TECOM Group

TECOM Group, a member of Dubai Holding, is a strategic business enabler contributing to the
realisation of Dubai’s economic aspirations by creating sector-focused communities and
innovative business solutions that enable business success.

TECOM Group’s 11 business communities reinforce Dubai’s position as a global hub for business
and commerce, and have attracted companies and talent from around the world including industry
leaders such as Google, CNN, DELL and Unilever. Covering seven vibrant industry sectors,
TECOM’s business communities offer a home in the region to over 5,100 companies ranging from
start-ups to multinational corporations employing 76,000 creative workers.

TECOM Group is a committed partner in the government’s efforts to realise the Dubai Plan 2021,
transform Dubai into a global innovation hub, and become the smartest city in the world.

© Dubai Design District, All rights reserved. Page 290 of 291