acknowledgements - dubai design district · acknowledgements dubai design district (d3) would like...

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

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.


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: [email protected] Version: 2.0 – Public Release Copyright: Dubai Design District, 2016


Table of Content 1 Purpose of the Document ................................................................................................... 9

2 ICT Master Plan ................................................................................................................ 10

2.1 Smart City Architecture ............................................................................................... 10

2.2 Smart City Passive Network ....................................................................................... 12

2.2.1 Outside Plant Corridors ....................................................................................... 12

2.2.2 OSP Space Requirements .................................................................................. 14

2.2.3 Fibre Design Requirements ................................................................................. 14

2.3 Smart City Converged IP Network .............................................................................. 15

2.3.1 Network Design Considerations .......................................................................... 16

2.3.2 Hierarchical Network Design ............................................................................... 18

2.3.3 Smart City Network High Level Design ................................................................ 22

2.4 Smart City Wireless Network ...................................................................................... 23

2.4.1 WLAN Functional Requirements ......................................................................... 25

2.5 Data Center ................................................................................................................ 27

2.6 Command and Control Center (CCC) ......................................................................... 27

3 ICT Infrastructure and Sensor Networks ........................................................................... 28

3.1 Potable Water Network (PWN) ................................................................................... 28

3.2 Sewage Waste Network (SWN) .................................................................................. 30

3.3 Storm Drainage Network (SDN) ................................................................................. 31

3.4 Fire Fighting Network (FFN) ....................................................................................... 33

3.5 Irrigation Water network (IWN) ................................................................................... 35

3.6 Electrical Distribution Network .................................................................................... 37

3.7 Street Lighting ............................................................................................................ 38

3.8 Traffic Lights ............................................................................................................... 39

3.9 Weather Station .......................................................................................................... 40

3.10 Outdoor Multifunction Sensors ................................................................................ 42

3.11 Connected Bus ....................................................................................................... 44

3.12 Electric Vehicle Charging Stations (EVCS) ............................................................. 45

3.13 Bus Shelter ............................................................................................................. 47

3.14 Connected Garbage Bins ........................................................................................ 48

3.15 Advanced Parking Management ............................................................................. 50

3.16 Pumping Stations Management .............................................................................. 51

3.17 Outdoor Digital Signage .......................................................................................... 52

3.18 Solar Power Generation .......................................................................................... 54

4 ICT In-Building Systems ................................................................................................... 57

4.1 Electrical Guideline ..................................................................................................... 57

4.1.1 Power distribution system .................................................................................... 57

4.1.2 Smart City Structured Cabling Networks.............................................................. 58


4.1.3 Generator Monitoring and Control ....................................................................... 58

4.1.4 Uninterrupted Power Supply (UPS) ..................................................................... 60

4.1.5 Lighting System (Internal, external) ..................................................................... 61

4.1.6 Elevators and Escalators ..................................................................................... 63

4.1.7 Building Management System ............................................................................. 65

4.1.8 Garbage chute and bins ...................................................................................... 66

4.1.9 Digital Signage .................................................................................................... 68

4.1.10 Audio visual and projectors/Video conferencing .................................................. 69

4.1.11 Advanced In-building car parking and Guidance management system ................ 72

4.1.12 Office Automation (Workplace management, Blinds control, etc.) ....................... 74

4.1.13 Smart metering – Electrical.................................................................................. 76

4.1.14 Interactive Kiosks ................................................................................................ 79

4.2 Communication Systems Guideline ............................................................................ 80

4.2.1 Mobile Service Coverage .................................................................................... 80

4.2.2 Telephone/ Internet / TV ...................................................................................... 80

4.2.3 Public Address System / Paging .......................................................................... 80

4.3 Life Safety Systems Guideline .................................................................................... 81

4.3.1 Fire alarm, Detection and voice evacuation system ............................................. 81

4.3.2 Central battery lighting system ............................................................................ 83

4.3.3 Firefighting (hose reel, sprinkler, FM 200, deluge) ............................................... 83

4.4 Mechanical Detailed Guideline ................................................................................... 83

4.4.1 District cooling Stations in building ...................................................................... 83

4.4.2 Air conditioning System ....................................................................................... 85

4.4.3 Ventilation system (Supply, extract, smoke management) ................................... 87

4.4.4 Potable Water Management ................................................................................ 89

4.4.5 Drainage (waste water/Grey water/sewage) ........................................................ 91

4.4.6 Irrigation Water Management .............................................................................. 93

4.4.7 Smart Metering – Cooling/ Water/ Gas ................................................................ 95

4.5 Smart City ICT In-building Guideline ........................................................................... 96

4.5.1 Smart City ICT Physical Infrastructure Guideline ................................................. 96

4.5.2 Smart City Converged IP Network ..................................................................... 117

4.5.3 Smart City Wireless Network ............................................................................. 117

5 ICT Tenant Fit-Out .......................................................................................................... 118

5.1 Apartment / Villa Consolidation Point (ACP) ............................................................. 118

5.2 Office Consolidation Point (OCP) ............................................................................. 118

5.3 Retail Consolidation Point (RCP) .............................................................................. 119

6 Standards and Refrence Documents .............................................................................. 119

6.1 Strategic Level Smart City Standards ....................................................................... 120

6.2 Process Level Smart City Standards ........................................................................ 120


6.3 Technical Specifications ........................................................................................... 120

6.4 The BSI smart cities portfolio .................................................................................... 120

6.4.1 Level 1 leadership guides .................................................................................. 121

6.4.2 Level 2 process frameworks .............................................................................. 121

6.5 Work of other standards bodies ................................................................................ 122

6.6 Standards Publications ............................................................................................. 123

6.7 d3 Specific Reference documents. ........................................................................... 123

7 Appendices ..................................................................................................................... 125

7.1 General Guiding Principals ....................................................................................... 125

7.1.1 The Network as the Platform ............................................................................. 125

7.1.2 Convergence of the ICT Infrastructure ............................................................... 125

7.1.3 Transformation/Service Delivery ........................................................................ 131

7.1.4 Automation of processes and systems .............................................................. 132

7.1.5 Easy Accessibility .............................................................................................. 132

8 Glossary ......................................................................................................................... 133


List of Figures Figure 2-1 Smart Services Enterprise Architecture .................................................................. 10

Figure 2-2 A sample view of a 12 Way Duct Bank ................................................................... 12

Figure 2-3 Elevation view of a typical manhole ........................................................................ 13

Figure 2-4 Functional Segmentation of the Converged Network ............................................. 17

Figure 2-5 Hierarchical Design Model ..................................................................................... 18

Figure 2-6 Access Layer of Hierarchical Design Model ........................................................... 19

Figure 2-7 Distribution Layer of Hierarchical Design Model..................................................... 20

Figure 2-8 Block Aggregation method of connecting access to distribution switches ................ 21

Figure 2-9 Core Layer of Hierarchical Design Mode ............................................................... 21

Figure 2-10 Smart City Network High Level Design ................................................................. 23

Figure 2-11 Mobility High Level Architecture ........................................................................... 24

Figure 2-12 A typical Wireless Access Point Connectivity for Inside and outside the buildings.

................................................................................................................................................. 26

Figure 3-1 Potable Water Network Logical Architecture ........................................................... 28

Figure 3-2 Sewerage Network Logical Architecture ................................................................. 30

Figure 3-3 Storm Drainage Network Logical Architecture ........................................................ 32

Figure 3-4 Fire Fighting Network Logical Architecture............................................................. 33

Figure 3-5 Irrigation Network Logical Architecture .................................................................. 35

Figure 3-6 Electrical Distribution Logical Architecture .............................................................. 37

Figure 3-7 Street Lighting Logical Architecture ....................................................................... 38

Figure 3-8 Traffic Lights Logical Architecture ........................................................................... 40

Figure 3-9 Weather Station Logical Architecture ...................................................................... 41

Figure 3-10 Outdoor Multifunction Sensors Functional Blocks ................................................. 42

Figure 3-11 Connected Bus Logical Architecture .................................................................... 44

Figure 3-12 EVCS Logical Architecture .................................................................................. 45

Figure 3-13 Bus Shelter Architecture ...................................................................................... 47

Figure 3-14 Connected Bins Architecture ............................................................................... 49

Figure 3-15 Advanced Parking Management Architecture ...................................................... 50

Figure 3-16 Pumping Station Management Architecture ......................................................... 51

Figure 3-17 Outdoor Digital Signage Architecture .................................................................... 53

Figure 3-18 Solar Power Generation Architecture .................................................................... 55

Figure 4-1 Power Distribution Logical Architecture .................................................................. 57

Figure 4-2 Generator Monitoring and Control Logical Architecture ......................................... 59

Figure 4-3 Uninterrupted Power Supply Logical Architecture ................................................... 60

Figure 4-4 Lighting Control Single Line Diagram ..................................................................... 62


Figure 4-5 Elevator and Escalator Logical Architecture............................................................ 64

Figure 4-6 Connected Garbage Bins Logical Architecture ....................................................... 67

Figure 4-7 Digital Signage Logical Architecture ....................................................................... 69

Figure 4-8 Audio Video Single Line Diagram .......................................................................... 71

Figure 4-9 Advanced Parking Management Architecture ........................................................ 72

Figure 4-10 Metering Single Line Diagram .............................................................................. 77

Figure 4-11 Interactive Kiosk functional Architecture ............................................................... 79

Figure 4-12 Fire Alarm Logical Architecture .............................................................................. 82

Figure 4-13 District Cooling Logical Architecture ..................................................................... 84

Figure 4-14: HVAC Control Single Line Diagram ...................................................................... 86

Figure 4-15 Ventilation System Logical Architecture ................................................................ 88

Figure 4-16 Potable Water Network Logical Architecture .......................................................... 89

Figure 4-17 Sewerage Network Logical Architecture ................................................................ 91

Figure 4-18 Sewerage Network Logical Architecture ................................................................ 93

Figure 4-19: Conduit Usable Area and Factors Affecting It ..................................................... 100

Figure 4-20: Typical Horizontal Pathways and Containment Systems .................................... 102

Figure 4-21: Pictorial Representation – Conduits .................................................................... 103

Figure 4-22: Pin/Pair Assignment ........................................................................................... 107

Figure 4-23: Typical Sleeve and Slot Installations ................................................................... 108

Figure 4-24: FTTx Architecture for a typical group of Towers.................................................. 110

Figure 4-25: Tight Buffered Fibre Optic Cable ........................................................................ 113

Figure 4-26: Scope of Standard 607 for Telecom Grounding .................................................. 115

Figure 4-27: Example of Bonding as Per ANSI/TIA-607-B ...................................................... 116

Figure 4-28: Example of Bonding as Per ANSI/TIA-607-B ...................................................... 117

Figure 6-1 Standards for developing Smart City Standards .................................................... 120

Figure 6-2 Smart City Standards mapped to the Smart City Process framework .................... 122

Figure 6-3 International Smart City standardization activities .................................................. 123

Figure 7-1 Data Virtualization ................................................................................................. 127

Figure 7-2 Virtual View Layered Architecture .......................................................................... 128

Figure 7-3 Integration Platform .............................................................................................. 129

Figure 7-4 API Management Platform ..................................................................................... 129

Figure 7-5 Benefits of API Management ................................................................................. 130

Figure 7-6 Benefits of API management ................................................................................. 130

Figure 7-7 Creating a Value Chain and Ecosystem ................................................................ 131

Figure 7-8 Smart City Maturity Model ..................................................................................... 132


List of Tables Table 2-1 Typical Smart City Architectural Framework ............................................................ 11

Table 2-2 Service Corridor Requirements for Smart Services ................................................... 13

Table 2-3 Last Mile Fibre Core Counts .................................................................................... 15

Table 4-1: Smart City Floor Consolidation Room Recommended Size ..................................... 97

Table 4-2: Maximum Capacity Containment- U/UTP Cat6 Cables .......................................... 101

Table 4-3: Maximum Capacity Tray Containment- U/UTP Cat6A/Class EA Cables ................ 101

Table 4-4: Maximum Capacity Trunking Containment- U/U/UTP Cat6A/Class EA Cables ...... 101

Table 4-5: Conduit Trade Sizes .............................................................................................. 103

Table 4-6: Cable Types for Horizontal Cabling ....................................................................... 104

Table 4-7: Specifications of Cat6 cable ................................................................................... 105

Table 4-8: Specification of Cat6A Cable ................................................................................. 105

Table 4-9: Specs for Multilayer Cable Trays for Vertical Risers with 40% Fill Ratio ................ 110

Table 4-10: Minimum Separation Distance from Power Source .............................................. 111

Table 4-11: Fibre Backbone specifications ............................................................................. 112

Table 6-1 d3 Specific Reference Documents .......................................................................... 124


1 Purpose of the Document

This purpose of this document is to provide developer guideline for building infrastructure for a Smart City and buildings within the city. This document can be used as an addendum to a standard developer guidelines that the Construction Industry has been using in the past. The main purpose of this document is to ensure ICT enablement wherever possible to ensure that the City and building infrastructure is Smart enough to ensure that new and innovative services can be deployed within the city with ease and speed. Deploying such services shall ensure that the visitors, tenants, and employees have a unique and better experience within the district. The objective of writing this document is to facilitate the design and construction work for different stakeholders within a Smart City who are responsible for their respective disciplines. This document can be used by different entities and user types (See Note). The following are some, of the entities or user types that shall use the document:

1. Master Planners and Consultants for creating Smart City ICT Master Plans, Concept and Detailed Designs for Infrastructure

2. Contractors for reference, tendering, and procurement 3. Systems Integrators for understand the integration needs and ensuring proper

configuration of Smart Services 4. Vendors for supplying hardware, software and licenses 5. Telecom and Utility Service Providers for understand connectivity, integration and data

sharing 6. Smart City Services team for reference

This document shall ensure that the infrastructure developed within the development meets or exceeds the Smart Dubai’s Vision to deliver Smart Services within the district. It is important to note that the infrastructure is built such that the KPIs defined by Smart Dubai can be met and achieved using Smart Infrastructure within the district. For the sake of clarity the reader must note that the references against each item listed in the Smart Dubai KPIs of this document are actual items listed in the Smart Dubai KPI Document (Smart Dubai District Blueprint V1.4.pptx). This document is written keeping in view the different guidelines published by various standard’s bodies relevant to Smart Cities around the world and Smart Dubai recommendations. This document can be treated as a living document and in due course of time these guidelines will be revised and reissued. Note: This document is a subset of the more comprehensive ICT Masterplan for Smart Cities - Design Guideline which can be referred to for more details.


2 ICT Master Plan

This section of the document provides a quick overview of the Smart City Architecture and provides guidelines of the community wide infrastructure layer details like utility corridors, fiber connectivity, network connectivity and spaces such as network consolidation, data center, command and control.

2.1 Smart City Architecture In order to implement ICT infrastructure within a Smart City it is important to take an architectural approach rather than plan and deploy infrastructure on a per service basis. Adopting the architectural approach will help transform the development into a connected community that assists in:

Realizing sustainable economic growth

Enabling environmental sustainability through resource management and operational efficiencies

Enhancing quality of life

The architecture provides a consistent, reusable and scalable framework and a set of building blocks to build the Smart and Connected Infrastructure within the development. In addition, a good architecture enables you to achieve the right balance between IT efficiency and business innovation. An eight layered Architectural Framework for implementing ICT infrastructure for Smart Cities is shown in Figure 2-1. The Smart City ICT Enterprise Architecture is based on some of the leading IT and Telecom architectures and frameworks. Some of the most important ones are: TOGAF, SOA, eTOM, ITIL, BICSI, ANSI/TIA, Uptime Institute.

Figure 2-1 Smart Services Enterprise Architecture

Once detailed this architecture will help provide the current and the futures Smart Services within the development. While each layer will have its own detailed architecture and needs to be defined


in detail, this document will however, briefly explain the functionality of each layer. This will ensure that the Smart Services defined in Section 3 work seamlessly.

Layered Technology

Description Reference Example

Business Layer Architecture

Provides a business model describing the government services and relationships to internal and external entities. The model will represent business functions, workflows, data, events, organization and governance models

Business needs and requirements

Access and Presentation Layer Architecture

Serves as container for local tools and applications, enables end user access to the infrastructure, and provide mechanics to access applications running on the servers

Web Browser, email client, desktop application, mobile application

Application Layer Architecture

Provides the realization of business needs and requirements as software solutions. Major enabler of service oriented architecture approach

Business Applications: CRM, KM, HR, Finance, Collaboration System applications: Web server, application server, database server, and infrastructure

Data Layer Architecture

Defines the data and information that support program and business line operations

Meta data, data model and structure for business applications, i.e. for HR applications personnel data

Integration Layer Architecture

Enables integration of the business applications and access to the required data throughout the service oriented infrastructure

HR web services, finance web services, authentication and authorization web services

Infrastructure Layer Architecture

Provides a target (logical) environment and describes the technical infrastructure required to deliver integrated services

Cable Plant, Network, network devices like routers and multiplexers, and computers

Operations Layer Architecture

Provides a model to support the deployment and delivery management of modern smart and connected services that integrate business processes across multiple entities, requiring an evolution of traditional approaches to operations and service management

Business transactions between entities such as help desk, configuration management, program management, software development

Security Layer Enables Aspire to build a consistent and effective security environment. The Security Architecture contains service definitions that are driven by business objectives and accordingly enabled by applications and the underlying technical infrastructure

Single sign on, authentication, SSL, authorizations, provisions

Table 2-1 Typical Smart City Architectural Framework


2.2 Smart City Passive Network A strong foundation for any Smart City is laid once its passive infrastructure is designed and implemented at the very beginning during the master planning phase. In many instances it is only an afterthought resulting in huge CAPEX spends, and Civil works that are a source of huge disruptions and inconvenience to the city dwellers. The Smart City Passive Network presents 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. This layer is crucial for the deployment of the identified Smart Services listed in the Service Catalogue and will also be scalable enough to accommodate future Smart Services in due course of time. The following section will provide the functional requirements and necessary guidelines for building the Smart City Passive Network.

2.2.1 Outside Plant Corridors

The exterior communications cabling pathways is required to provide a city wide distribution system (manholes and duct 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 one manhole 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:

1. Man holes 2. Hand holes 3. Conduits 4. Inner-ducts 5. Duct banks

The Figure 2-2 and Figure 2-3 below are examples of a duct bank and a manhole:

Figure 2-2 A sample view of a 12 Way Duct Bank


Figure 2-3 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:

1. Placing and joining cables 2. Pulling cables 3. Splicing 4. Maintenance and operation equipment

Manholes must be equipped with:

1. A sump 2. Corrosion-resistant pulling irons 3. Spare Cable racks (grounded per applicable electrical code or practice) 4. Ladders (grounded per applicable electrical code or practice)

Manholes should be constructed in such a way that they:

1. Are capable of supporting the heaviest anticipated street traffic weight 2. Are reasonably waterproof 3. Provide sufficient racking space for the ultimate number of cables and other equipment

that requires permanent anchorage

Different types of roads within the development will have different duct sizes. The table below provides guidance on the sizes.

S. No Different Road Sizes Necessary Service corridor for Smart

Services

Manhole types

1 61 mt. to 43 mt. Road 75 cm - 4 Way D54 – 100 mm duct

JRC 4 or JRC 12(If Service Corridor can be more than 75 cm)

2 36 mt. to 25 mt. Road 75 cm 2 Way D54 – 100 mm duct

JRC 4 or JRC 12(If Service Corridor can be more than 75 cm)

3 16 mt. to 8 mt. Road 50 cm 2 Way D56 – 50 mm duct

JRC 4. Only if required.

Table 2-2 Service Corridor Requirements for Smart Services


2.2.2 OSP Space Requirements

OSP Spaces are small environmentally secure control rooms designed to host communications network equipment and fibre cabling distribution. Communication Network Consolidation point is a transit point that connects different network components and services together using certain communications design principles around passive and active system connectivity. The different types of spaces necessary for delivering services within a Smart City are as follows:

2.2.2.1 Primary Fibre Consolidation (PFC)

For d3 the PFC room will contain Backbone fibre for the entire district, Distribution fibre for the surrounding neighbourhoods, and/or, 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 PFC room for d3 shall be 6 x 4 mt. (24 sq. meters). It is necessary to have a dedicated plot for this purpose. Alternatively, 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. However, for maintaining redundancy at least two such rooms will be required within the development. The room must be located centrally so as to ensure cost effective use of fibre infrastructure.

2.2.2.2 Secondary Fibre Consolidation (SFC)

For d3 the SFC room 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 SFC room for d3 shall be 5 x 3 mt. (15 sq. meters). It is necessary to have a dedicated plot for this purpose. Alternatively, it can also be co-located within a d3 owned building. The Secondary Consolidation Point can act as the distribution for up to 5 buildings provided the buildings are below G+10 floors.

2.2.2.3 Building Consolidation Room (BCR)

Building Consolidation Room will serve either a single building or a few adjacent buildings. BCRs will mainly host IP Access or data equipment. They will also host fibre optics OSP Access links and ODFs as well as cable patching gear. The BCRs shall also have well designed environmental conditions including cooling, humidity, air flow, power distribution, UPS, cable containment systems and Inside Plant (ISP) cabling.

The BCRs will contain Distribution and Access fibre of the building itself and for some of the neighbouring buildings. 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 Building Consolidation rooms will only have racks that aggregate the fibre from the building Floor Consolidation 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 Building Consolidation rooms for d3 shall be 4 x 3 mt. (12 sq. meters). It is necessary 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.

2.2.3 Fibre Design Requirements

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


1. Fibre to the Node/Neighbourhood (FTTN) 2. Fibre to the Cabinet (FTTCab) or Fibre to the Curb (FTTC) 3. Fibre to the Building (FTTB) 4. Fibre to the Home (FTTH) or Fibre to the Premises (FTTP)

The FTTx design offers complete flexibility to support open system physical architectures, which can easily accept passive or active upgrades. 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:

1. First, a capability to connect as many subscriber edge devices as possible gradually as the city grows

2. Second, a long term presence of physical fibre between the different type of plots and Consolidation rooms 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 2-3 below shows the required 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 Community Centre) 8

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 2-3 Last Mile Fibre Core Counts

2.3 Smart City Converged IP Network 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 necessary to build a hierarchical network design 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.


2.3.1 Network Design Considerations

The network infrastructure should ensure the following requirements

2.3.1.1 Scalability

Due to 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.

2.3.1.2 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:

1. Additional Bandwidth 2. Additional Ports or Slots 3. Additional Features

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.

2.3.1.3 Resiliency

Resiliency should be built at every layer of the entire network. This includes redundant connectivity and redundant modules. The network has to carry delay sensitive services like voice and video. The maximum acceptable round trip delay for such services should not exceed 150ms. All the uplinks should be designed to work in active-active mode. Fast convergence techniques should be deployed in the network to achieve high resiliency.

2.3.1.4 Availability

Availability would depend on many factors as given below. The network must be able to provide such functionality.

1. Failure of the Active components 2. System-level redundancy 3. Link Bundling technologies 4. Loop Free Network Connectivity

2.3.1.5 Functional Segmentation

Distinct Functional blocks like Data Centre, WAN and Internet should be connected to the core as shown in the Figure 2-4 below.


Figure 2-4 Functional Segmentation of the Converged Network

2.3.1.6 Routing Protocol

The fact that the Smart City Network has to support different types of traffic like voice, video and data and the large number of endpoints and network devices will be installed to provide the services, it is necessary to pay attention to the choice of using right routing protocols. For security reasons the network needs to segment and separate different traffic types and as such it is necessary to choose a routing protocol that scalable, reliable and has fast convergence capabilities.

2.3.1.7 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. An uptime of 99.99% uptime is necessary 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:

1. Loss 2. Delay 3. Delay variation (Jitter).

2.3.2 Hierarchical Network Design

The architecture of the network for a Smart City should be a hierarchical design laid out in different layers as follows:

1. Core 2. Distribution 3. Access

This hierarchical model shall help to design a modular network topology using scalable “building blocks” that allow the network to meet evolving business needs. The

Figure 2-5 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. The hierarchical design segregates the functions of the network into these separate building blocks to provide availability, flexibility, scalability, and fault isolation.

2.3.2.1 The Access Layer

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.


Figure 2-6 Access Layer of Hierarchical Design Model

The access layer shall provide port connectivity to the endpoints for the smart city services. The access layer shall provide the connectivity to the

1. Indoor and Outdoor Wireless Access points 2. BMS system endpoints 3. Interactive Kiosks 4. Digital Signage 5. Different City wide Sensors or IP Sensor Gateways

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 Smart City Services listed in the Services Catalogue. It is necessary 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. It is necessary, 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. 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.

2.3.2.2 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 apply packet manipulation if required. Availability, load balancing, QoS and provisioning are the important considerations at this layer. Some of the salient features of distribution layer include:


1. Aggregates wiring closes (access layer) and uplinks to core 2. Protects core from high density peering and problems in access layer 3. Route summarization, fast convergence, redundant path load sharing 4. Protocol support to provide first hop redundancy 5. The distribution layer can be summarized as the layer that provides policy-based

connectivity

Figure 2-7 Distribution Layer of Hierarchical Design Model

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. For tall buildings the distribution equipment shall be placed in the FCRs or in the BCRs 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 place in the PFC room It is necessary that the distribution switches be placed in the SFC, PFC room depending on the design requirements. All the uplinks from the access switches in the building shall consolidate in this distribution switch. 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 implies that a total aggregate bandwidth 35 Gbps traffic will be consumed on these uplinks. Further applying a 1:5 over subscription means that total 7 Gbps bandwidth will be consumed on the uplinks connecting the distribution switches to the core switches. Multiple buildings within the block ranging from 4 to 5 buildings use one building to aggregate the several buildings of the block. This option necessitates that the access vertical backbone fibre


from the buildings can be extended to the one of the Building Consolidation Rooms (BCRs). It implies that enough fibre capacity is made available between the BCRs of each building to the BCR of the block aggregation building. Cross Connect facility must be provided in the MTRs to support the concept. Figure 2-8 below provides a view of this connectivity option. To reduce the CAPEX, block wise distribution can also be considered. All the buildings 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 2-8 Block Aggregation method of connecting access to distribution switches

2.3.2.3 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.

Figure 2-9 Core Layer of Hierarchical Design Mode


The core layer includes several functions such as the following: Backbone for the network - connects network building blocks

1. Performance and stability versus complexity ( less is more in the core) 2. Aggregation point for distribution layer 3. Separate core layer helps in scalability during future growth 4. 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. It is necessary that core switches be places within the Primary Consolidation 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 the same campus.

2.3.3 Smart City Network High Level Design

Based on the Hierarchical Design guidelines the Smart City Network High Level Design is shown in the Figure 2-10 below.


Figure 2-10 Smart City Network High Level Design

2.4 Smart City Wireless Network Similar to the Smart City IP Network, the wireless network shall be a mandatory 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 services could also use Wireless LAN. In addition, the same Wireless LAN services can be extended outside of the buildings in the open areas within the Smart City. Figure 2-11 below gives a high level view of Mobility Architecture of the Wireless LAN. The top layer of the architecture that is composed of the applications run on the Mobility platform using Wireless LAN. Most of the wireless 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 over Wireless LAN. Network access elements of the Architecture use open protocols to carry the services for the applications to be deployed.

FLR SW - 1

FLR SW - 2

FLR SW - 3

FLR SW - n

Campus Access SW

Fib

er

Fib

er

Typical Bldg 1

FLR SW - 1

FLR SW - 2

FLR SW - 3

FLR SW - n Fib

er

Fib

er

Typical Bldg 2

FLR SW - 1

FLR SW - 2

FLR SW - 3

FLR SW - n Fib

er

Fib

er

Typical Bldg n

Campus Aggregation for Buildings

Campus Access SW

Campus Access SW

Campus Aggregation for

Public Area Services

Fiber Fiber

AREA SW - 1

Fib

er

Fib

er

AREA SW - 2

AREA SW - 3

AREA SW - 4

48 Cores SM FOC between PFC-1 sand PFC-2

Wireless Controller

Primary Fiber Consolidation (PFC) - 1

Wireless Controller

Campus Aggregation for Buildings

Campus Aggregation for

Public Area Services

4 Cores

4 Cores

4 Cores

4 Cores

4 Cores 4 Cores Fiber

2 Cores from each area

2 Cores from each area

Primary Fiber Consolidation (PFC) - 1


Figure 2-11 Mobility High Level Architecture


2.4.1 WLAN Functional Requirements

In order to deploy a ubiquitous WLAN within the smart city the following design guidelines need to be followed. A high level Wireless network connectivity inside the buildings and outside is shown in the Figure 2-12 below:

1. The Wireless Access Points (WAP) need to deploy in each building lobby and the common areas of the buildings.

2. The WAP must support PoE functionality and must connect to the Floor Access Switch. 3. All common areas in the building that include the entrance lobbies and lift lobbies on each

floor must have WAPs installed to provide Wi-Fi coverage 4. Typical coverage area of a WAP must be between 30 mt. to 50 mt. per WAP depending

on density of users and the amount of obstruction between the WAP and the user. Please note that this is a guidance for planning purposes only. For actual deployment it is necessary to carry out a detailed RF survey to identify the exact location of the placing the WAP and also determining the total number of WAPs.

5. For outdoor WLAN a Wi Mesh design needs to be adopted. 6. For each hop the Latency must be less than 10ms per Hop and typically must be between

1-3 milliseconds. 7. A maximum of 8 hops can be possible between two MAPs. However, for achieving good

performance and availability only 3 to 4 hops are recommended. 8. A maximum of 20 MAPs can be connected per RAP 9. The distance between a RAP to MAP must be between 90 mt. to 150 mt 10. The RAP can be placed on tall buildings mobile network towers if possible to get a clear

line of sight to the MAPs 11. The distance between one MAP to another must be between 75 mt. to 150 mt. 12. The MAPs can be placed on the rooftops of low height buildings, facades of buildings or

smart poles. 13. Each map must have a coverage area of about 75 mt. MAP should not exceed 12m height

above street 14. The Indoor and the outdoor WLAN must be integrated and be managed by one common

set of management, security and mobility applications in the Data Centre.


Figure 2-12 A typical Wireless Access Point Connectivity for Inside and outside the buildings.

FLR

SW -

1

FLR

SW -

2

FLR

SW -

3

FLR

SW -

n

Cam

pus A

cces

s SW

Fiber

Fiber

Typi

cal B

ldg

1

FLR

SW -

1

FLR

SW -

2

FLR

SW -

3

FLR

SW -

n

Fiber

Fiber

Typi

cal B

ldg

2

FLR

SW -

1

FLR

SW -

2

FLR

SW -

3

FLR

SW -

n

Fiber

Fiber

Typi

cal B

ldg

n

Cam

pus A

ggre

gatio

n fo

r Bui

ldin

gs

Cam

pus A

cces

s SW

Cam

pus A

cces

s SW

Cam

pus

Aggr

egat

ion

for

Publ

ic Ar

ea Se

rvice

s

Fiber

Fib

er

AREA

SW

- 1

Fiber

Fiber

AREA

SW

- 2

AREA

SW

- 3

AREA

SW

- 4

48 C

ores

SM FO

C be

twee

n PF

C-1

sand

PFC

-2

Prim

ary F

iber

Co

nsol

idat

ion

(PFC

) - 1

Cam

pus A

ggre

gatio

n fo

r Bui

ldin

gsCa

mpu

s Ag

greg

atio

n fo

r Pu

blic

Area

Serv

ices

4 Co

res

4 Co

res

4 Co

res4

Core

s

4 Co

res

4 Co

res

Fiber

2 Co

res f

rom

ea

ch a

rea

2 Co

res f

rom

ea

ch a

rea

Prim

ary F

iber

Co

nsol

idat

ion

(PFC

) - 1

Root

AP

Mes

h AP

Mes

h AP

Wire

less

Co

ntro

ller

Wire

less

Co

ntro

ller

Wire

less

Co

ntro

ller

Wire

less

Co

ntro

ller

Root

AP

Mes

h AP

Mes

h AP

Indo

or W

irele

ss

Conn

ectiv

ity

Outd

oor W

irele

ss

Conn

ectiv

ity


2.5 Data Center A Data Centre is required for hosting different Smart Services applications platforms, networking equipment, security infrastructure, Data Virtualization platform, different building system and command and control backend applications. Based on the proposed Smart Services for the development in 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. mt. 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. The Data Centre can be built internally within the development or can be hosted outside the development at a co-location site with a Data Centre Services Provider.

2.6 Command and Control Center (CCC) The d3 CCC, the Contact Centre as well as the Data Centre work 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 CCC space can be provided in any of the buildings within the development and must be purpose built to meet the requirements of a modern CCC. A minimum of 204 Sq. mt. space is required for the CCC


3 ICT Infrastructure and Sensor Networks

This section provides the guidelines of the city infrastructure that provides services to the entire community outside of the residential or commercial buildings.

3.1 Potable Water Network (PWN) Potable Water Network

The PWN 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. Within each building it is mandatory to measure different water quality parameters as listed in this table below:

This system is mandatory for TECOM infrastructure developer and Private Developers

This system is relevant in Design, Construction and Operation phases

This system shall follow the six general guiding principles as described in section 7.1

Functional blocks:

Figure 3-1 Potable Water Network Logical Architecture

List of Parameters to be monitored

1. Flow 2. Pressure Level 3. pH value : (To be monitored on the DEWA entry to the District and at each building

entrance) 4. Valve Status & Control 5. Pollution Level 6. Flood Level 7. Toxic Level 8. Pump Motor Status & Control 9. Leakage

Technical Requirements: 1. Get secure connectivity to the d3 Smart City Network 2. Use the d3 Smart City Network instead of a standalone network 3. Open all necessary ports and provide all access credentials necessary forSmart City

Applications Integration

a. RDBMS b. NoSQL c. Web Services d. Big Data (Hadoop)


e. JMS messaging

4. Expose/Publish key APIs required by the d3 network using one of the following access modes:

a. Representational State Transfer (RESTful) APIs b. Simple Object Access Protocol (SOAP) APIs c. JavaScript Object Notation (JSON) APIs d. Have Extensible Markup Language (XML) APIs

The list of smart services that this system enables, includes:

1. Community Information Services and Portal 2. Building Information Modelling 3. Personal Dashboards 4. Water Management

Reference Standards

1. As per the DEWA guidelines 2. ISO 11348-3:2007 3. ISO 14046:2014 4. WHO drinking water guidelines 5. UAE.S GSO 1904:2009 6. BS 3506 (1969)

Responsibility

1. TECOM Infrastructure Developer and Contractor

KPIs

1. Fall of pressure between two adjacent sensors (must not be more than 30%) 2. Leak detection accuracy (to be identified within 200 to 300 mt.) 3. Potable Water System outage (Must not exceed .01 %) 4. Ph value to be maintained at 6.6 to 7.3 5. Pollution and toxicity measurement as per WHO guidelines for water quality

Smart Dubai KPIs

1. I2.1.1 Progress degree of ICT usage in the protection of main city water resources count by ratio of urban water resources under protection with ICT measures

2. I2.1.2 Effect of flood control monitoring by means of ICT measures count by ratio of flood that cause no fatal damage or huge loss due to early warning with ICT

3. I2.1.3 Proportion of water pollution control by means of ICT measures count by ratio of water pollutant resources under automatic inspection

4. 12.1.5 Proportion of toxic substances monitoring by means of ICT measures count by ratio of highly dangerous toxic substance sources under control with the help of ICT

5. I6.2.1 Coverage of installation of road sensing terminals count by number of road sensors per kilometer in overall urban road coverage

6. I6.4.1 Drainage system management with ICT measures count by number of sensors per kilometer in overall urban drainage system

7. I6.4.7 Improvement of underground pipelines and spatial integrated administration with ICT measures / count by ratio of digital documented and spatial integrated administration of underground pipelines among all underground network


3.2 Sewage Waste Network (SWN) Sewage Waste Water Network

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

This system is mandatory for TECOM infrastructure developer


This system shall follow the six general guiding principles as described in Section-7.1

Functional blocks:

Figure 3-2 Sewerage Network Logical Architecture


1. Flow

2. Level Measurement

3. pH Value

4. Conductivity Measurement

5. Sludge Level Measurement

6. Leakage Detection

7. Gas formation

Technical Requirements: 1. Get secure connectivity to the d3 Smart City Network 2. Use the d3 Smart City Network instead of a standalone network 3. Open all necessary ports and provide all access credentials necessary for Smart City

Applications Integration:

o RDBMS o NoSQL o Web Services o Big Data (Hadoop) o JMS messaging

4. Expose/Publish key APIs required by the d3 network using one of the following access modes:

o Representational State Transfer (RESTful) APIs o Simple Object Access Protocol (SOAP) APIs o JavaScript Object Notation (JSON) APIs o Have Extensible Markup Language (XML) APIs


1. Community Information Services and Portal 2. Building Information Modelling,


3. Personal Dashboards, 4. Waste Management

Reference Standards

1. BS 3506 (1969) 2. BS EN 752-4: 1998, BSI 3. ISO 559:1991 4. ISO 1452-1 to 5:2009 5. ISO 4435:2003

Responsibility

1. TECOM Infrastructure Developer and Contractor

KPIs

1. Ensure sewage pipes are filled no more that (%age of Capacity) 2. Sewage system does not overflow more than (Certain number of times per year) 3. Leak detection accuracy (to be identified within 200 to 300 mt.) 4. Gas levels are monitored and maintained within certain limits

Smart Dubai KPIs


2. I6.3.1 Waster discharge management with ICT measures Count by number of sensors per kilometer in overall waste network

3. I6.3.2 Improvement of waste water recycling with ICT measures Count by ratio of water recycled this year with the help of ICT surveillance or management by means of ICT measures count by ratio of highly dangerous toxic substance sources under control with the help of ICT


5. 16.4.7 Improvement of underground pipelines and spatial integrated administration with ICT measures / count by ratio of digital documented and spatial integrated administration of underground pipelines among all underground network

3.3 Storm Drainage Network (SDN) Storm Drainage Network

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




Functional blocks:

http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?ics1=93&ics2=25&ics3=&csnumber=4648



Figure 3-3 Storm Drainage Network Logical Architecture


Flow

Level Measurement

pH Value

Pollutant Level (such as Oil Level Measurement)

Flood Level

Leakage Detection

Technical Requirements:

Get secure connectivity to the d3 Smart City Network

Use the d3 Smart City Network instead of a standalone network

Open all necessary ports and provide all access credentials necessary for Smart City Applications Integration:


Expose/Publish key APIs required by the d3 network using one of the following access modes:



Community Information Services and Portal

Building Information Modelling,

Personal Dashboards,

Waste Management,

Reference Standards

As per Dubai Municipality Guidelines

ISO 24511:2007

BS EN 752-4: 1998, BSI

BS 3506 (1969)

BS EN 752-4: 1998, BSI

ISO 559:1991

ISO 1452-1 to 5:2009

ISO 4435:2003




Responsibility

TECOM Infrastructure Developer and Contractor

KPIs

1. Number of times the storm water system got over flooded 2. Storm water draining efficiency (Ratio of Amount or water cleared to time take to clear) 3. Storm water system does not overflow more than (Certain number of times per year) 4. Leak detection accuracy (to be identified within 200 to 300 mt.) 5. Process storm-water inspection and modelling data. 6. Identify pipes requiring frequent cleaning as well as those at greatest risk of hydraulic

deficiencies and structural failure

Smart Dubai KPIs







3.4 Fire Fighting Network (FFN) Fire Fighting Network

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 Defence (DCD) specifications




Functional blocks:

Figure 3-4 Fire Fighting Network Logical Architecture



Flow

Pressure Level

pH Value

Tank Level

Hydrant Clearance (pref. by CCTV Analytics)

Leakage detection












Water Management,

Reference Standards

As per Dubai Civil Defence

NFPA 1971, Standard on Protective Ensembles for Structural Fire Fighting and Proximity Fire Fighting, 2013 edition.

ISO 6182

ISO 6184

ISO 11348-3:2007

ISO 14046:2014

Responsibility


KPIs

1. Fall of pressure between two adjacent sensors (must not be more than 30%) 2. Leak detection accuracy (to be identified within 200 to 300 mt.) 3. Fire Fighting Water management personnel productivity. (No of employees per number

of subscribers serviced)


4. Fire Fighting Water System outage (Must not exceed .01 %)

Smart Dubai KPIs




3.5 Irrigation Water network (IWN) Irrigation Water Network

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.




Functional blocks:

Figure 3-5 Irrigation Network Logical Architecture


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













Water Management,

Reference Standards

Standards issued by Dubai Municipality

ISO/TC 23/SC 18

ISO/TR 8059:1986

United Nations. Global Sustainable Development Report – Executive Summary: Building the Common Future We Want. New York: United Nations Department of Economic and Social Affairs, Division for Sustainable Development. 2013. http://sustainabledevelopment.un.org/globalsdreport/, last viewed November 2014

Responsibility


KPIs

1. Fall of pressure between two adjacent sensors (must not be more than 30%) 2. Leak detection accuracy (to be identified within 200 to 300 mt.) 3. Irrigation Water management personnel productivity. (No of employees per Sq. Mts area

of Irrigated land) 4. Irrigation Water System outage (Must not exceed .01 %) 5. Pollution and toxicity measurement as per WHO guidelines for water quality 6. Irrigation water Management System accuracy (Measure how many times the system

changed water schedules based on automatic moisture conditions and weather conditions)

Smart Dubai KPIs





3.6 Electrical Distribution Network Electrical Distribution Network

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.

This system is mandatory for TECOM/DEWA infrastructure developer



Functional Blocks

Figure 3-6 Electrical Distribution Logical Architecture


Voltage

Current

Power Factor

Consumption


As per DEWA issued guidelines




Energy Management,

Reference Standards

As defined by DEWA

IEC 61970: Common Information Model (CIM) / Energy Management

IEC 61850: Power Utility Automation

IEC 61968: Common Information Model (CIM) / Distribution Management

IEC 62351: Security

IEC 62056: Data exchange for meter reading, tariff and load control


IEC 61508: Functional safety of electrical/electronic/programmable electronic safety-related systems

Responsibility


KPIs

1. Electricity outage (Must not exceed .01 %) 2. Maintain Steady Voltage (Must maintain voltage within .02% on higher or lower side) 3. Accurately be able to measure consumption online at any time on consumer level and

building level 4. Predict with accuracy potential changes in consumption profile and provide alerts to

consumers 5. Detect power theft and detect and equipment failures with 80 to 90% accuracy

Smart Dubai KPIs

1. Electricity supply system management with ICT measures count by ratio of electricity supply systems under management with ICT help (Smart Grid)

3.7 Street Lighting Street Lighting

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 mounting devices like wireless outdoor access points, CCTV cameras and other sensors for automation.




Functional blocks:

Figure 3-7 Street Lighting Logical Architecture


Ambient LUX levels

Energy consumption


Fault Status












Energy Management,

Reference Standards

As per RTA guidelines

Responsibility


KPI’s

1. Street Lighting System outage (Must not exceed .01 %) 2. Increased Energy savings and reducing energy use by 25% 3. Increase the life span of the bulb by making use of dimming functionality 4. Increase efficiency by streetlights dimming up to 70% uncommonly used places like

empty parking lots 5. Increase efficiency streetlights dimming up to 30% to 40%, dimming for well-trafficked

roadways and neighbourhood streets in order to keep areas secure

Smart Dubai KPIs

6. I6.4.2 Street Lighting & signal system management with ICT measures count by number of sensors per kilometers in overall street lighting system

3.8 Traffic Lights Traffic Lights


Traffic light and traffic management system is provided by RTA. 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.

This system is mandatory for TECOM infrastructure developer but deployed by RTA



Functional blocks:

Figure 3-8 Traffic Lights Logical Architecture


Fault Status

Traffic Flow


As per RTA issued guidelines

Reference Standards

As defined by RTA

ISO/TC 204 - Intelligent transport systems

Responsibility


KPI’s

1. Traffic Lighting System outage (Must not exceed .01 %) 2. 100% accuracy of pin pointing defective or inoperative traffic lights 3. Traffic light efficiency (Maintain max green time at junctions) 4. Accurately provide online traffic congestion and route selection to road users

Smart Dubai KPIs

1. I6.4.2 Street Lighting & signal system management with ICT measures count by number of sensors per kilometers in overall street lighting system

3.9 Weather Station Weather Station

Fault Status

Traffic Flow

Remote

Measurement and

Control Field

Devices

d3 Command and Control

Center (CCC)

Centralized Management

d3 IP Network

Typical Measurement and/

or Control Parameters


Weather stations are portable or fixed devices that can be placed within d3 to provide a very realistic weather conditional prevalent with d3 at any moment of time. One or several such stations can be placed within 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 recent 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.




Functional blocks:

Figure 3-9 Weather Station Logical Architecture


Temperature

Humidity

Wind Direction

Wind Speed

Rainfall










Smart City Experience

Temperature

Humidity

Wind Direction

Wind Speed

Rainfall

Remote

Measurement and

Control Field

Devices


Center (CCC)


d3 IP Network




Reference Standards

ISO 17713-1:2007

ISO 16622:2002

ANSI/CEA 2009-B-2010,

Responsibility


KPIs

1. Online Dashboard available to public providing real time data to help residents take decisions during extreme weather conditions

2. Provide update on weather conditions every 30 min 3. Weather condition reporting efficiency (Ratio of Number of weather sensors to total

area)

3.10 Outdoor Multifunction Sensors Outdoor Multifunction Sensors

The Outdoor 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




Functional blocks:

Figure 3-10 Outdoor Multifunction Sensors Functional Blocks


Gaseous Air Pollution

Dust cum Suspended Air Pollution

Road Flooding

Noise Level












Reference Standards

EN 61000-6-1:2001

EN 61000-6-3:2001

EN 50082 -1: 1997

EN 50081 -1: 1992

Responsibility


KPIs

1. Online Dashboard available to public providing real time data to help residents take decisions during extreme weather conditions

2. Increase noise measurement efficiency by converting noise level (in decibels) into an industry standard (4-20mA) output, which can in turn be fed directly into a SCADA-type control system

3. Reporting efficiency (Ratio of Number of different sensors to total area) 4. Provide update from each sensor every 30 min

Smart Dubai KPIs

1. I4.1.4 Convenience of smart traffic information administration and service. Count by ratio of convenience expression about smart traffic in paper/online interview

2. I4.2.2 Penetration of ICT for natural disaster. Count by number of various sensors per square kilometer in disaster-prone regions

3. I4.2.3Publication rate of natural disaster alert Count by ratio of disasters that is alerted ahead of time each year

4. I2.1.4 Proportion of air pollution monitoring by means of ICT measures. Count by number of air quality sensors per square kilometer

5. I2.1.5 Proportion of toxic substances monitoring by means of ICT measures. Count by ratio of highly dangerous toxic substance sources under control with the help of ICT

6. I2.1.6 Proportion of noise monitoring by means of ICT measures. Count by number of noise sensors per square kilometer

7. I6.2.1 Coverage of installation of road sensing terminals. Count by number of road sensors per kilometer in overall urban road coverage


8. I3.1.8 Improvement of traditional industry with ICT Count by ratio of GDP improvement due to technology upgrade

3.11 Connected Bus Connected Bus

The 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 community data.




Functional blocks:

Figure 3-11 Connected Bus Logical Architecture


Geo-Location

CCTV Camera

Interactive Digital Sign

Ticketing System












Connected Bus

Reference Standards

As defined by RTA

U.S. Federal Transit Administration standards

Responsibility


KPI’s

Improve customer experience for public transportation users

Increase use of public transportation reducing carbon footprint (Measure no of passengers riding per bus)

Increased Safety and security by live monitoring of the Bus using CCTV

Wi-Fi Service adoption rate (Ratio of users using Wi-Fi within the bus to the total number of passengers in the bus at any time.

Smart bus services adoption rate (Ratio of people using the bus within the development to the number of residents plus number of employees working within the development

3.12 Electric Vehicle Charging Stations (EVCS) Electric Vehicle Charging Stations (EVCS)

The electric vehicle power and charging initiative consists of installing charging stations for electric vehicles within d3 community. 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.

This system is mandatory for TECOM infrastructure developer but deployed by RTA



Functional blocks:

Figure 3-12 EVCS Logical Architecture


Geo-Location

CCTV Camera

Smart Meter

PoS + Payment Gateway












Energy Analytic System Optimization

Reference Standards

As defined by DEWA

IEC 62196 Mode 1, 2, 3

SAE J1772/2009

J2836

J2847

J2847

J2894

CHAdeMO

Responsibility


KPIs

1. Monitor Charging Stations adoption rate (Ration of number of cars charging to the total residents and employees registered with the region)

2. Monitor charging station efficiency rate (Measure the number of cars charging to number of power units used)

3. Provide carbon footprint reduction figure on a daily, weekly and monthly basis

Smart Dubai KPIs

1. I2.2.2 Level of industrial electricity usage (per GDP) with ICT measures. Count by ratio of average industrial electricity (including charging electricity driven vehicles) Consumption saved this year compared with last year

2. I2.2.5 Level of fossil fuel usage with ICT measures (per GDP). Count by ratio of average industrial fossil fuel consumption saved this year compared with last year

3. I4.1.4 Convenience of smart traffic information administration and service. Count by ratio of convenience expression about smart traffic in paper/online interview

4. I5.3.2 Appliance of smart community services. Count by ratio of communities that is assisted with smart community services


5. I6.2.1 Coverage of installation of road sensing terminals. Count by number of road sensors per kilometer in overall urban road coverage

3.13 Bus Shelter Bus Shelter

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 .




Functional blocks:

Figure 3-13 Bus Shelter Architecture


Geo-Location

CCTV Camera

Interactive Digital Sign

Light Control

HVAC Control

People Count

Bus Arrival / Departure













Reference Standards

As defined by RTA

Responsibility


KPIs

1. Bus Shelter footfall (Ratio of number of people using the bus within the development to the number of residents plus number of employees working within the development)

2. Wi-Fi Service adoption rate (Ratio of number of users using Wi-Fi within the bus to the total number of passengers in the bus at any time)

3. Increase use of public transportation reducing carbon footprint (Measure no of passengers riding per bus)

4. Increased Safety and Security by live monitoring of the Bus using CCTV 5. Reduce energy consumption by 25% using automation of the lighting and cooling

control 6. Increase user experience by providing real time location of the Bus 7. Provide analytic reports to the Transport authority for number of users at peak hours 8. Provide analytic reports to the Transport authority for the busiest hours 9. Provide analytic reports to the Transport authority to monitor energy consumption to

attain higher energy efficiency.

3.14 Connected Garbage Bins Connected Garbage Bins

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. Exception: Hazardous Waste from Hospitals, Clinics, research labs and industries




Functional blocks:


Figure 3-14 Connected Bins Architecture


Waste Level in the bin

Geo-Location of the bin

Odour









Waste Management

Community Information Services


Reference Standards

As defined by Dubai Municipality

Responsibility


KPIs

Garbage collection efficiency (Garbage bins to be emptied before they reach 80% capacity)

Garbage collection personnel productivity. (No of employees per number of garbage bins)


Turnaround Time to emergency call-out. (Average time taken to respond to emergencies)

Optimize logistic resources while reducing collection and delivery costs by up to 25% in the earlier years

Optimize operational efficiency by sending efficient routes directly to drivers

3.15 Advanced Parking Management Advanced Parking Management

Advanced Parking Management will be deployed within d3 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 and provide information on available parking spots. Correlation of sensors will enable the generation of meter violations.

This system is mandatory for TECOM infrastructure developer and



Functional blocks:

Figure 3-15 Advanced Parking Management Architecture


Sensors on parking spots

New generation parking meters

Parking Analytics







o Representational State Transfer (RESTful) APIs o Simple Object Access Protocol (SOAP) APIs o JavaScript Object Notation (JSON) APIs

Parking Analytics

Parking Spot Sensor

Remote

Measurement and

Control Field

Devices


Center (CCC)


d3 IP Network

Typical Sensor or End Point

Parking Meter


o Have Extensible Markup Language (XML) APIs


Advanced Parking Management

Visitor Management

Traffic Management

Reference Standards

As per authority guidelines

Responsibility


KPIs

1. APM Efficiency: Average time taken by user to park the car 2. Parking space efficiency: Monitor the amount to time the parking space is not used 3. Accurately provide online parking space availability information on map to increase

efficiency

Smart Dubai KPIs

1. I1.2.3 Proportion of business based on GIS (location, navigation etc.). Count by ratio of social, governance and enterprise businesses that utilize GIS based services

2. I6.2.2 Coverage of parking guidance systems. Count by ratio of parking lots under automatic guidance

3. I3.1.8Improvement of traditional industry with ICT. Count by ratio of GDP improvement due to technology upgrade

3.16 Pumping Stations Management Pumping Stations Management

Pumping Stations wherever deployed with d3 either for potable water, drainage water, storm water, and firefighting hydrant must be provided with control systems that provide the functionality and the data that can be used to improve the availability of pumps, pumping stations. These provide a simple way to reduce not only the risk of downtime and flooding, but also maintenance and energy costs.




Functional blocks:

Figure 3-16 Pumping Station Management Architecture


List of Parameters to be monitored and controlled

Hydraulic data

Pump speed

Pump on/off

Energy usage









Energy Management

Water Management


Reference Standards

Responsibility


KPIs

Accurately provide data every 30 min interval

Pumping System Management Efficiency: Monitor flooding incidents over a period of time.

Pumping System outage (Must not exceed .01 %)

3.17 Outdoor Digital Signage Digital Signage

In d3, visual communication will be possible through outdoor digital displays and video walls. The aim is to communicate to the visitors, tenants and employees of d3. Digital content will range from text, to images, to full-motion audio and video. The outdoor Digital Screens can be mounted on the smart poles and need to be ruggedized and hardened for harsh weather conditions.


Exception:

Fixed Directional signage

Parking signage

Service room Signage

This system is mandatory for TECOM This system is optional for Private Developer



Functional Requirements:

There minimum requirements include:

o Environmentally Protected Digital Sign at critical locations in the public areas particularly next to Main Entrance of each building

o Next to each pedestrian crossing on each side o At the entrance of each bus shelter o After every 300 meter on the median of the major roads

The outdoor digital signs shall be used to display:

o Emergency notification and evacuation routes o Advertising o Building energy dashboard o Entertainment and Art o Bus routes and timings

Functional Blocks:

Figure 3-17 Outdoor Digital Signage Architecture









Visual Communication

Shared Resources

Digital Signage Client

Content Delivery Client

Remote

Measurement and

Control Field

Devices


Center (CCC)


d3 IP Network


Digital Signage Terminal


Smart Working Spaces

Traffic Management

Energy Dashboards

KPIs

1. Revenue from Advertisements per screen 2. Downtime for each Digital Screen not be more than .01%

Reference Standards

ITU-T H.781

Responsibility


3.18 Solar Power Generation Solar Power Generation

HH Sheikh Mohammed bin Rashid Al Maktoum, Vice President and Prime Minister of the UAE and Ruler of Dubai has called for solar panels to be installed on every roof in Dubai by 2030, as part of the Emirates vision to produce 75% of its energy from clean sources by 2050. To get there in time, the Dubai Clean Energy Strategy 2050 also calls for interim targets of 7% of solar power by 2020, and 25% by 2030. DEWA’s Shams Dubai solar program is based on the principle of ‘net metering’. This allows customers to install solar panels to produce their own power, to reduce their electricity bill every month. Any surplus electricity not used immediately is sold back to the grid at the same price, and at the end of the month only the net amount is billed to the customer. Should a customer produce more energy in one month than he / she has consumed, DEWA allows rolling over these KWhs to the next month. To achieve this target within d3 certain unused areas like the medial spine between the roads can be used to generate solar power using Photo Voltaic Cells.

This system is Mandatory for TECOM. Can be deployed as a roof top solution of building Cladding.





o Land for holding Photo Voltaic Panels. The area is directly proportional to the amount of Solar Power to be generated. The central spine between the roads is an ideal space to use

o Solar Power Generation room that will house the DC/AC inverter, PC Combining Switch gear and controller, Typical size of this room should be a minimum 4 mt x 4 mt in size

o The solar farm can be a fixed direction panels or can be fitted with tracking system to follow the sun for achieving maximum generation.

o DC/AC inverters directly proportional to the generated capacity are required to convert the DC power generated by Solar Panels to AC power that can be either connected directly to the load or can be fed back to the power grid

Functional Blocks:

http://www.arabianbusiness.com/solar-panels-on-every-roof-by-2030-dubai-s-13-6bn-clean-energy-drive-613779.html


Figure 3-18 Solar Power Generation Architecture









Solar roofs

Energy Management

Energy Dashboards

Smart Dubai KPI

Solar power generation efficiency (Power generated against total power consumed)

Solar power system outage to be within 0.1%

Sent out efficiency: Energy sent out to grid / Energy generated

Reference Standards

Photo Voltaic (PV) Modules :

Standard Test Condition (STC) PERFORMANCE

o IEC 60904-2 (I-V ) o IEC 60891 ( TEMP & INTENSITY CORRECTIONS)

DESIGN QUALIFICATION

o IEC 61215 (MON & MULTI CRYSTALLINE SILICON) o IEC61646( THIN FILM) o IEC 62108( CONCENTRATOR)

Monitor hydraulic data

Control Pump Operations like

stop, start and speed variation

Remote

Measurement and

Control Field

Devices


Center (CCC)


d3 IP Network



SAFETY

o IEC 61730 (ALL MODULES)

SALT, MIST AND CORROSIVE

o IEC 61701

PV BoS SYSTEMS:

EFFICIENCY / PERFORMANCE

o IEC 61683 (PCU) o IEC 62093( CHARGE CONTROLLERS & MPPT )

ENVIRONMENTAL

o IEC 60068 2 (1,2,14, 30)

STORAGE BATTERIES

o IEC 61427 (ALL TYPE BATTERIES) o IS 1651 o IS 13369

CABLES, SWITCH/ CIRCUIT BREAKERS/ CONNECTORS

o IEC 60947 PART I,II & III o EN 50521 o IEC 60189, IS 694, IS1554, IS/ IEC 69947

PV SYSTEMS :

Jn. BOXES/ ENCLOSURES

o IEC 2208 o IP 65 / IP 21

SPV SYSTEM DESIGN

o IEC 62124

INSTALLATION PRACTICES

o IEC 60364 o IEC 61727

DEWA Codes

Responsibility



4 ICT In-Building Systems

4.1 Electrical Guideline

4.1.1 Power distribution system

Power Distribution Network

All buildings within d3 need to be monitored at the Main Distribution Board, of the building, Floor Distribution boards and the individual DBs of residences or offices.

This system is mandatory for TECOM Building developer. This system is mandatory for all type of buildings residential, commercial, mixed use and purpose built building like hospitals, schools etc. This system is optional for Private Developer. However, to enhance customer services the developer can extend the d3 service into their facility as a managed service



Functional Blocks

Figure 4-1 Power Distribution Logical Architecture


Voltage

Current

Power Factor

Consumption


As per DEWA issued guidelines




Energy Management,

Reference Standards

As defined by DEWA





IEC 62351: Security



Responsibility

TECOM Building Developer and Contractor

Private Building Developer and Contractor

KPIs




Smart Dubai KPIs


4.1.2 Smart City Structured Cabling Networks

Please refer to section 4.5.1 for details.

4.1.3 Generator Monitoring and Control

Generator Monitoring and Control

All Generators if available within any building within d3 needs to be monitored for Energy Management

This system is mandatory for TECOM Building developer. This system is mandatory for all type of buildings residential, commercial, mixed use and purpose built building like hospitals, schools etc. This system is optional for the Private Building Developers



Functional Blocks


Figure 4-2 Generator Monitoring and Control Logical Architecture


Voltage

Current

Power Factor

Consumption

Generator control ON/OFF



Energy Management,

Reference Standards

As defined by DEWA




IEC 62351: Security



Responsibility



KPIs




Smart Dubai KPIs



4.1.4 Uninterrupted Power Supply (UPS)

Uninterrupted Power Supply

All UPSs if available within any building within d3 needs to be monitored for Energy Management




Functional Blocks

Figure 4-3 Uninterrupted Power Supply Logical Architecture


Voltage

Current

Power Factor

Consumption



Energy Management,

Reference Standards

As defined by DEWA




IEC 62351: Security




Responsibility



KPIs




Smart Dubai KPIs


4.1.5 Lighting System (Internal, external)

Lighting Control System

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.




List of Control 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.

Sensors such as lux level, motion detectors


Lighting control modules for switching and dimming

Single Line Diagram of the Lighting Control Systems

Figure 4-4 Lighting Control Single Line Diagram





o RDBMS o NoSQL


o Web Services o Big Data (Hadoop) o JMS messaging





Energy Management,

Reference Standards

DALI contained in BS EN 60929:2006

DMX 512 maintained by ESTA

LON specified by ANSI/CEA

BACnet as per ASHRAE/ANSI

Responsibility



KPIs

1. Energy Consumption per light 2. Lamp efficiency : Energy consumed to Lux Levels 3. Lighting management personal productivity. (No of employees per street lights

serviced) 4. Fault detection accuracy on per lamp basis 5. Fault detection accuracy on circuit or line

4.1.6 Elevators and Escalators

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, and Modbus and can integrate with the other building systems.







o The system should support 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.

Figure 4-5 Elevator and Escalator Logical Architecture








List of Services that this system enables:


Energy Management

Reference Standards

EN 81-40:2008

ISO 22201:2009

EN 60947-4-1 :2001

EN 60950:2006


Responsibility



KPIs

1. Energy Consumption per lift or elevator 2. Lift of Escalator Efficiency: (Ratio of people carried to Energy consumed ) 3. Personal productivity. (No of employees per lift and Escalator) 4. Fault detection accuracy

4.1.7 Building Management System

Building Management System

Building Management system enables d3 to form associations between ICT assets and facilities assets, thereby providing more complete data on energy and GHG savings. 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

Building management should provide options for a web interface to the ICT energy management system.



This system shall follow the six general guiding principles as described in Section- 7.1

Functional Requirements: 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

Building management should provide options for a web interface to the ICT energy management system.










Integrated Building Management System

Community information Services and Portal

Operations and Maintenance Enhancement

Building information modelling

Energy Management

Reference Standards

ISO 16484-5:2012

Responsibility

TECOM Building Developers and Contractors

Private Building Developers and Contractors

4.1.8 Garbage chute and bins

Garbage Chute and Bins

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.





The wireless bin sensors automatically measure container fill levels hourly and send updates to the Web portal via GSM cellular communications.

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:

o Provide pick up alerts to waste collection company based on bin fill levels o Provide remote location of bins and the collection distances o Update service information from waste collection companies

Figure 4-6 Connected Garbage Bins Logical Architecture









Waste Management

Community Information Services


Reference Standards

As defined by Dubai Municipality

Responsibility


Private Infrastructure Developer and Contractor

KPIs

Waste Level in the bin

Geo-Location

Mobile Network

Operator

Or

City WiFi


Center (CCC)


d3 IP Network



1. Garbage collection efficiency (Garbage bins to be emptied before they reach 80% capacity)

2. Turnaround Time to emergency call-out. (Average time taken to respond to emergencies)

3. Optimize logistic resources while reducing collection and delivery costs by up to 25% in the earlier years

4. Optimize operational efficiency by sending efficient routes directly to drivers

4.1.9 Digital Signage

Digital Signage

In d3, visual communication will be possible through indoor digital displays and video walls. The aim is to communicate a message to the visitors, tenants and employees of d3. Digital content will range from text, to images, to full-motion audio and video. Exception:

Fixed Directional signage






o One digital sign in the lobby of each building o One digital sign at each floor level o Small form factor digital sign at each meeting room

The lobby digital signs shall be used to display:

o News and events o Emergency notification and evacuation routes o Advertising o Scheduling o Building energy dashboard o Entertainment and Art o Directional Signage

The floor digital signs shall be used to display:

o News and events o Emergency notification and evacuation routes o Advertising o Scheduling o Building energy dashboard o Entertainment and Art

The meeting room digital signs shall be used to display:

o The schedule of the meeting room o The name of the person who reserved the room

Functional Blocks:


Figure 4-7 Digital Signage Logical Architecture










Interactive Services

Shared Resources


Smart Dubai KPI

Revenue from Advertisements per screen

System outage (Must not exceed .02 %)

Reference Standards

ITU-T H.781

Responsibility



4.1.10 Audio visual and projectors/Video conferencing

Audio Visual and projectors/Video Conferencing

Digital Signage Client

Content Delivery Client

Remote

Measurement and

Control Field

Devices


Center (CCC)


d3 IP Network


Digital Signage Terminal


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. Exception: Digital Signage






o Small form factor Digital Screens at the entrance doors of the rooms define above o Projectors or Digital Screens of adequate size depending on the size of the room o Controllers o Speakers o Management Centre or connect to the management centre of d3









Figure 4-8 Audio Video Single Line Diagram




Shared Resources


KPI



Reference Standards

IEC 60065

IEC 60574

IEC 60849

IEC 60958

IEC 60950

Responsibility



4.1.11 Advanced In-building car parking and Guidance management system

Advanced Parking Management and Guidance Management

Advanced Parking Management will be deployed within 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.




Functional blocks:

Figure 4-9 Advanced Parking Management Architecture


Sensors on parking spots

New generation parking meters

Video camera with analytics


Parking Analytics

Parking Spot Sensor

Remote

Measurement and

Control Field

Devices


Center (CCC)


d3 IP Network


Parking Meter









Advanced Parking Management

Visitor Management

Traffic Management

Reference Standards

There are no specific standards available as of today for Office Automations. However, the following should be applied wherever necessary

General Standards of ICT elements need to be applied

General Standards of MEP systems need to be applied

As defined by local agencies

Responsibility



KPIs

1. APM Efficiency: Average time taken by user to park the car 2. Parking space efficiency: Monitor the amount to time the parking space is not used 3. Accurately provide online parking space availability information on map to increase

efficiency

Smart Dubai KPIs

1. I1.2.3 Proportion of business based on GIS (location, navigation etc.). Count by ratio of social, governance and enterprise businesses that utilize GIS based services

2. I6.2.2 Coverage of parking guidance systems. Count by ratio of parking lots under automatic guidance

3. I3.1.8Improvement of traditional industry with ICT. Count by ratio of GDP improvement due to technology upgrade


4.1.12 Office Automation (Workplace management, Blinds control, etc.)

Office Automation

Office automation offers a variety of ways to schedule, locate, and collaborate in an office space. The aim is to provide functionality to book the rooms, schedule meetings in advance and provide automation functionality in the offices using the web client.




Functional Requirements :

Outlook Add-in o Outlook add-in (compatible with Versions 2007, 2010, and 2013) Conference

rooms across the enterprise. o Ability to add custom locations. o Ability to request equipment and other resources for the room. o Integration with Outlook calendar to provide a single view of meetings and

appointments. o Ability to edit, update, and delete meeting room reservations. o Ability to resolve conflict or meeting rooms for recurring meetings by booking

multiple rooms as necessary (without duplication)

Web Client Based o Using a web-based interface, end users can specify various meeting parameters,

such as start and end time, meeting type, subject, location, etc., in an intuitive manner.

o Users to mark a meeting as confidential to prevent displaying the meeting subject on digital signage.

o Users can also add Web conferencing sessions to meetings o The system should generate a list of rooms available based on the parameters

specified. o Users can add and invite both internal and external attendees to the meeting. o Users can set preferences for time zones and primary location.

IP Phone Based o Unplanned, or instant bookings of meeting spaces should be supported from IP

phone present in the room. o IP phones display the list of meetings in the given space prominently.

Room Confirmation

Early Release:

Instant Confirmation

Meeting Extension: Users can choose to extend meetings if the room is available beyond the scheduled end time through IP phone.

Users can control HVAC for the meeting space o HVAC can be turned on and off by defining occupancy status. o Users can also set room temperature to values chosen from those specified by

the administrator.

Lighting Control o Users can control individual and multiple light systems in the meeting space. o Lights can be turned on and off.


o Users can also set the brightness of the lights

Blind Control o Users can control individual and multiple blind systems in the meeting space. o Blinds can be raised, lowered, and paused at any level.

A/V Equipment Control o Users can control projector and projector screen (single and multiple) in the

meeting space. o Projector can be turned on and off. o Projector screen can be raised, lowered, and paused midway in its space. o Room mode facility to control lights, blinds, projector and projector screen

through a single action.

Fault Reporting o Users can report problems or issues in the meeting space. o Reports can be integrated with customer’s trouble-ticketing system. o In absence of trouble-ticketing system integration, cases from IP phones are

communicated to a preconfigured email address.

Broadcasting Messages to Digital Signage o Users can broadcast messages from IP phones to digital signage for the meeting

space. o Users can broadcast emergency notifications, such as evacuation, fire drill, etc. o Users can broadcast green advisor notifications (for example, green tips, energy

consumption data, etc.).









Smart Workspaces

KPIs

1. System outages (Must not exceed .02 %) 2. Office work space usage efficiency to be maintained at 70%

Reference Standards

There are no specific standards available as of today for Office Automations. However, the following should be applied wherever necessary


General Standards of ICT elements need to be applied

General Standards of MEP systems need to be applied

Responsibility



4.1.13 Smart metering – Electrical

Smart Metering - Electrical

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 Smart Meters need to be installed in each building to monitor the consumption for each home or office.

This system is mandatory for TECOM Building developer. This system is mandatory for all type of buildings residential, commercial, mixed use and purpose built building like hospitals, schools etc. This system is mandatory for Private Developer.



List of Parameters to be monitored:

Electricity usage on the incoming power lines to homes or offices and also at the entry point in the buildings

Single line diagram


Figure 4-10 Metering Single Line Diagram












Energy Management,

KPIs

1. System outages (Must not exceed .02 %) 2. Electricity outage (Must not exceed .01 %) 3. Accurately be able to measure consumption online at any time on consumer level and



Smart Dubai KPIs


Reference Standards

As defined by DEWA

IEC 62056

IEC 61850

IEC 60870

IEC 61968 CIM

ANSI C12.9

DLSM/COSEM

IEEE 802.15.4

IEEE 19.1.2 PHY

MBus

ISO 27001

Responsibility




4.1.14 Interactive Kiosks

Interactive Kiosks

The Interactive Kiosk service consists of strategically located kiosks around the d3 community enabling tenants and visitors to locate restaurants, access directories, find their way, ask for a taxi and even talk to a remote attendant. The d3 Interactive Kiosks initiative is an essential part of the tenants’ and visitors’ experience, for it will provide a content delivery mechanism for multiple features and services. The interactive Kiosks must adopt the Accessibility requirements to ensure use by differently abled individuals

This system is mandatory for TECOM Building developer. This system is mandatory for all type of buildings residential, commercial, mixed use and purpose built building like hospitals, schools etc. This system is optional for Private Developer. However, to enhance customer services the developer can extend the d3 service into their facility as a managed service.



Functional blocks:

Figure 4-11 Interactive Kiosk functional Architecture

Functional Requirements: The Interactive Kiosk Should meet the functional requirements:

Integration with peripherals including webcams, magnetic card readers, barcode scanners, optical scanners, and printers

Integration with the infra-red Remote Control

SIP client support for two-way video calls

Embedded video encoder card for HD video conferencing between two Interactive Kiosk Client devices

Encoder driver that enables video snapshots and 1080p streaming

Debugging console for troubleshooting

Custom web-based application platform for touchscreen interactive applications

Fanless design, providing for reliable and quiet operation

Interactive multimedia support with multiple video outputs

Wi-Fi, Ethernet, and Bluetooth enabled





o RDBMS o NoSQL o Web Services

Remote

Measurement and

Control Field

Devices


Center (CCC)

Content Management

d3 IP Network d3 IP

Network


Interactive Screen

Digital Media Player


o Big Data (Hadoop) o JMS messaging




Interactive Services (Kiosks)

Way finding mobile app


Reference Standards

As per local authorities

Responsibility


Private building Developer and Contractor

4.2 Communication Systems Guideline

4.2.1 Mobile Service Coverage

In order to have adequate mobile service coverage within the buildings it is necessary to have the in building mobile coverage system. This system has to be built strictly as per the guidelines provided by du and Etisalat.

4.2.2 Telephone/ Internet / TV

The typical service provider service like telephone, internet and TV are to be provided within the building by the local service providers. The telecom spaces and telecom Structure Cabling systems are to be built by the developers and the contractors as per the guidelines of du and Etisalat

4.2.3 Public Address System / Paging

Public address system / Paging

The Public Address 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.

This system is mandatory for TECOM Building developer. This system is mandatory for all type of buildings residential, commercial, mixed use and purpose built building like hospitals, schools etc. This system is optional for Private Developer.













Shared Resources


KPI


Reference Standards

EIA 160 Sound Systems

EIA-101 Amplifiers for Sound Equipment

SE-103 Speakers for Sound Equipment

SE-104 Engineering Specifications for Amplifiers for Sound Equipment

NFPA 70 National Electrical Code (NEC)

IEC 60849

Responsibility



4.3 Life Safety Systems Guideline

4.3.1 Fire alarm, Detection and voice evacuation system

Fire alarm, Detection and voice evacuation system

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.

Figure 4-12 Fire Alarm Logical Architecture


As per Dubai Civil Defence issued guidelines


Security Service Integration


Reference Standards

As defined by Dubai Civil Defence

Responsibility

Infrastructure Developer and Contractor

KPIs

1. Adherence to Dubai Civil Defence Fire and Life safety code of practice 2. Regular testing of fire-fighting equipment such as fire pumps

Battery Status

Smoke

Heat

Cause/Reason status

Remote

Measurement and

Control Field

Devices


Center (CCC)


d3 IP Network



3. 24x7 equipment functioning 4. Accurate & timely reporting 5. Notification of an emergency as per Civil Defence requirements and timelines in

seconds. 6. Fire pumps and controllers are to be designed and installed in accordance with NFPA20

& NFPA750 water mist standards latest edition. Pumps shall be designed and sized with 110% pumping capacity and their performance shall not fluctuate by greater than ±5%.

7. Records maintained for fire drills and actual emergency response

4.3.2 Central battery lighting system

The Central battery lighting system is necessary for ensuring that the lighting is available to the users during emergencies when normal power is not available. This system must be built as per the guidelines of Dubai Civil Defence.

4.3.3 Firefighting (hose reel, sprinkler, FM 200, deluge)

The firefighting systems within d3 buildings must be built as per the guidelines of Dubai Civil Defence. There are no requirements from Smart Services Perspective on firefighting systems except for the water management of Fire Fighting network as defined in Section 3.4

4.4 Mechanical Detailed Guideline

4.4.1 District cooling Stations in building

District Cooling System

The District Cooling system provides the Chilled water for HVAC systems within the building. The use of District Cooling system provides efficient use of utilities like water, electricity, space in addition to sustainability streamlined maintenance and operations. The district cooling systems are provided within d3 by Empower.




Functional Blocks


Figure 4-13 District Cooling Logical Architecture


Flow

Pressure Level

Valve Status and Control

Chilled water Temperature inlet

Chilled water Temperature outlet










Building Information Modelling

Reference Standards

ANSI/AHRI 550/590

As defined by EMPOWER

Responsibility



KPIs

1. System outages (Must not exceed .02 %)


2. Chilled water supply outage (Must not exceed .05 %) 3. Accurately be able to measure consumption online at any time on consumer level and


consumers 5. Detect chilled water theft and detect and equipment failures with 80 to 90% accuracy

Smart Dubai KPIs

1. Chilled water supply system management with ICT measures count by ratio of electricity supply systems under management with ICT help (Smart Grid)Ensure metering accuracy

2. Service quality and reliability 3. Power and water efficiency 4. Appropriate sizing as per needs

4.4.2 Air conditioning System

Air Conditioning System

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. The HVAC System has two distinct set of equipment. 1. The HVAC Systems 2. The HVAC Control System The focus of this guideline is only the HVAC Control Systems and not the HVAC Systems




List of Control Devices 1. Direct Digital Controller (DDC) 2. Thermostat 3. IP-Gateway 4. Management stations (Centralized in CCC) 5. User thin / thick clients 6. HMI Interface (Portable Operator Terminals and handhelds

Single Line Diagram of the HVAC Control Systems


Figure 4-14: HVAC Control Single Line Diagram










Energy Analytic System Optimisation


Network Enable Utility Metering

Reference Standards

Maintain air quality as per ASHRAE standard 62.1-200762.1-2007 Ventilation for acceptable indoor air quality

(Reference ISO 6242-2:1992 standards)

Adaptability of the system to changing environment leading to energy efficiency and reduction in operational costs.

Responsibility



KPIs

1. (Standards ISO 16343:2013 Energy performance of buildings -- Methods for expressing energy performance and for energy certification of buildings)

2. Maintain machinery downtime targets (0.1% to 2.5%) 3. Quality and speed of response 4. Controlled labour costs 5. Reporting of HVACs that have set points that deviate from standards

Smart Dubai KPIs

1. Electricity supply system management with ICT measures count by ratio of electricity supply systems under management with ICT help (Smart Grid)Ensure metering accuracy


4.4.3 Ventilation system (Supply, extract, smoke management)

Ventilation System

The buildings with d3 need to maintain Ventilation using mixed mode or mechanical systems




http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?ics1=91&ics2=140&ics3=30&csnumber=12519


Functional Blocks:

Figure 4-15 Ventilation System Logical Architecture


Fan Speed and Control

Pressure

Smoke









Energy Analytic System Optimisation


Security Service Integration


Reference Standards

Maintain air quality as per ASHRAE standard 62.1-200762.1-2007 Ventilation for acceptable indoor air quality

(Reference ISO 6242-2:1992 standards)

Adaptability of the system to changing environment leading to energy efficiency and reduction in operational costs.

Local bodies like Municipality, Civil Defense

Responsibility


Fan Speed and Control

Remote

Measurement and

Control Field

Devices


Center (CCC)


d3 IP Network



http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?ics1=91&ics2=140&ics3=30&csnumber=12519



KPIs

1. (Standards ISO 16343:2013 Energy performance of buildings -- Methods for expressing energy performance and for energy certification of buildings)

2. Maintain machinery downtime targets (0.1% to 2.5%) 3. Quality and speed of response 4. Controlled labour costs 5. Reporting of HVACs that have set points that deviate from standards

Smart Dubai KPIs

1. Electricity supply system management with ICT measures count by ratio of electricity supply systems under management with ICT help (Smart Grid)Ensure metering accuracy


4.4.4 Potable Water Management

Potable Water Network

The in building Water management system shall consist of a centralized system that manages the distribution of water within the buildings within d3 and identifies operational status, incidents (such as leakages, etc.) and generates alerts for responsible maintenance teams. Within each building it is mandatory to measure different water quality parameters at the entry level or at the building water storage tank as listed in this table below




Functional blocks:

Figure 4-16 Potable Water Network Logical Architecture



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












Water Management

Reference Standards

As per DEWA guidelines

Responsibility



KPIs

1. Fall of pressure between two adjacent sensors (must not be more than 30%) 2. Leak detection accuracy (to be identified within 200 to 300 mt.) 3. Water management personnel productivity. (No of employees per number of

subscribers serviced) 4. Portable Water System outage (Must not exceed .01 %) 5. Ph value to be maintained at 6.6 to 7.3 6. Pollution and toxicity measurement as per WHO guidelines for water quality


Smart Dubai KPIs



3. I2.1.3 Proportion of water pollution control by means of ICT measures count by ratio of water pollutant resources under automatic inspection

4. 12.1.5 Proportion of toxic substances monitoring by means of ICT measures count by ratio of highly dangerous toxic substance sources under control with the help of ICT



4.4.5 Drainage (waste water/Grey water/sewage)

Sewage Waste Water Network

The in building Drainage shall be a used to carry waste water coming out from the buildings within d3 into the centralized SWN system of the development that manages the collection of waste water in accordance with applicable Dubai Municipality guidelines. Exception:




Functional blocks:



Flow

Level Measurement

pH Value

Conductivity Measurement

Sludge Level Measurement


BCC Chemical Analysis

Leakage Detection












Water Management

Reference Standards

As per Dubai Municipality Guidelines

Responsibility



KPIs

Decrease in number of incidents of internal sewer flooding for properties that have flooded within the last one to three years. (Measure is number of incidents)

Total leakages measuring the sum of distribution losses and supply pipe losses in mega litres per day.

The total number of pollution incidents (categories 1 to 3) in a calendar year emanating from a discharge or escape of a contaminant from a sewerage company asset.

Performance of sewerage assets to treat and dispose of sewage in line with the discharge permit conditions imposed on sewage treatment works. (Measure as percentage)

Smart Dubai KPIs



3. I6.3.2 Improvement of waste water recycling with ICT measures Count by ratio of water recycled this year with the help of ICT surveillance or management by means of ICT


measures count by ratio of highly dangerous toxic substance sources under control with the help of ICT


5. 16.4.7 Improvement of underground pipelines and spatial integrated administration with ICT measures / count by ratio of digital documented and spatial integrated administration of underground pipelines among all underground network

4.4.6 Irrigation Water Management

Irrigation Water Measurement

DEWA strongly recommends not to use the Potable water for Irrigation purposes. In case there are any such irrigation requirements within the building or within its boundary it is necessary to use the recycled water from the nearest community Waste Management System.

This system is mandatory for TECOM Building developer. This system is mandatory for all type of buildings residential, commercial, mixed use and purpose built building like hospitals, schools etc. This system is optional for Private Developer.



Functional blocks:



Flow

Level Measurement

pH Value

Conductivity Measurement

Sludge Level Measurement

BCC Chemical Analysis

Leakage Detection













Water Management

Reference Standards

Standards issued by Dubai Municipality

ISO/TC 23/SC 18

ISO/TR 8059:1986

United Nations. Global Sustainable Development Report – Executive Summary: Building the Common Future We Want. New York: United Nations Department of Economic and Social Affairs, Division for Sustainable Development. 2013. http://sustainabledevelopment.un.org/globalsdreport/, last viewed November 2014

Responsibility



KPIs

Decrease in water usage based on total effective amount of water used compared to reference / historical data

Increase in production yield based on irrigation water use efficiency (kg of produce per meter3 of water applied)

Controlled energy usage

Maintain soil water status within the optimum range for maximum potential yields

Reduction in irrigation water lost as drainage and runoff

Smart Dubai KPIs





4.4.7 Smart Metering – Cooling/ Water/ Gas

Smart Metering – Cooling / Water / Gas

For all commercial and Residential buildings within d3 it is necessary the Smart Metering is enabled as per the guidelines of the Utility Provider. While the Smart Meters will be provided by the Utility providers the Developer and the Contractors have to ensure that the distribution network of the utility within the building have sufficient provisions for ensuring installation of the Smart Meters





Resource consumption by the Residential or Commercial users.












Water Management

Reference Standards

As per corresponding Utility Provider guidelines

As defined by DEWA

IEC 62056

IEC 61850

IEC 60870

IEC 61968 CIM


ANSI C12.9

DLSM/COSEM

IEEE 802.15.4

IEEE 19.1.2 PHY

MBus

ISO 27001

Responsibility



KPIs

1. System outages (Must not exceed .02 %) 2. Electricity outage (Must not exceed .01 %) 3. Accurately be able to measure consumption online at any time on consumer level and



Smart Dubai KPIs


4.5 Smart City ICT In-building Guideline

4.5.1 Smart City ICT Physical Infrastructure Guideline

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 as defined in Section 7.1 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. 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 telecommunications 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.5.1.1 Smart City ICT Rooms

4.5.1.1.1 Building Consolidation Room (BCR)

This room is similar to the Main Telecom Room of the telecom provider. This room consolidates the fibre from the floors and from the Primary or Secondary Fibre Consolidation Rooms. For d3 the Building Consolidation Room 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 3 mt. (12 sq. meters). It is necessary 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.

4.5.1.1.2 Floor Consolidation Room (FCR)

The Floor Consolidation is similar to Floor Telecom Room. The Floor Consolidation Room will house all the Smart City building fibre back bone 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 Floor Consolidation Room 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-1: Smart City Floor Consolidation Room Recommended Size

4.5.1.1.3 Floor Enclosures (FE)

The Floor Enclosure is a relatively small, passive only enclosure, which caters to areas not accessible from the Floor Consolidation Room directly. Floor Enclosures generally house cable terminations and cross connections. The Floor Enclosures can be used when only passive components and limited active equipment will be installed on the floor. The Floor Enclosure should serve an area not greater than 335 square meters (3,600 square feet). The Floor Enclosure 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


4.5.1.1.4 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 Building or Floor Consolidation Rooms, 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. Two-core fibre cable from the Smart City Main Consolidation Room or 2 x Cat 6 or higher cables from Floor Consolidation Room 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 Primary or Secondary Fibre Consolidation Points. In the interest of saving space within the apartment it is necessary 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.

4.5.1.1.5 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 Building Consolidation Room/Floor Consolidation Room, 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. Four-core (Two for day one use and two for future) fibre cable from the Building Consolidation Room or 4 Cat 6 or higher cables from Floor Consolidation Room must be terminated in the OCP. In the interest of saving space within the apartment it is necessary 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.

4.5.1.1.6 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


on patch panels/IDC modules, two or four core fibre cable from Building Consolidation Room/ Floor Consolidation Room, 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. Four-core (Two for day one use and two for future) fibre cable from the Building Consolidation Room or 4 Cat 6 or higher cables from Floor Consolidation Room must be terminated in the RCP. In the interest of saving space within the apartment it is necessary 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.

4.5.1.2 Smart City 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 Smart City 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:

Smart City spaces

Smart City pathways

Smart City cables

Connecting hardware

Grounding system

Smart City equipment


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

4.5.1.2.1 Horizontal Distribution System

4.5.1.2.1.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.

Figure 4-19: 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 (mm)

Trunking Size (mm) Number of Unshielded Twisted 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-2: 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-3: Maximum Capacity Tray Containment- U/UTP Cat6A/Class EA Cables

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






150mm x 150mm 230 U/UTP Cables Table 4-4: 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.


Figure 4-20: Typical Horizontal Pathways and Containment Systems

4.5.1.2.1.2 Horizontal Conduits and Spacing

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

Outlet locations are permanent

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-21: 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 necessary 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 (mm)

Fill Area (mm2) # of Cat 6 cables

¾” / 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

Table 4-5: Conduit Trade Sizes

4.5.1.2.1.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

50/125 micron Fiber Multimode

Cable

90 meters

Table 4-6: 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.

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-7: Specifications of Cat6 cable

Table 4-8: 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.

4.5.1.2.1.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.

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 necessary when number of UTP cable terminations is less than 48.

IDC CAT6 or beyond patch panel is necessary in the TR and MTR, especially when the total number of UTP cable terminations is more than 48.

4.5.1.2.1.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 which 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-22: 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.

Face plates should be dual white PVC plated.

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.


4.5.1.2.2 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

4.5.1.2.2.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.

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-23: 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.

4.5.1.2.2.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).

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-24: 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.

Fiber 12-Core Cable (Outside diameter 5.8 – 6.0 mm)

Cable Tray Size for Indoor Cable (mm)

5 cable 75 x 50

7 cable 100 x 50

10 cable 150 x 50

20-25 cable 300 x 50

30-35 cable 450 x 50

40-45 cable 600 x 50 Table 4-9: Specs for Multilayer Cable Trays for Vertical Risers with 40% Fill Ratio

4.5.1.2.2.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 proximity to open or non-metal pathways

130 mm 300 mm 600 mm

Unshielded power lines or electrical equipment in proximity to grounded metal conduit pathway

65 mm 150 mm 300 mm

Power lines enclosed in a grounded metal conduit (or equivalent shielding ) in proximity to grounded metal conduit pathway

50 mm 150 mm 300 mm

Transformers and electric motors 1000 mm 1000 mm 1000 mm

Fluorescent lighting 300 mm 300 mm 300 mm Table 4-10: 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.

4.5.1.2.2.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:

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 OM3/4

SM

Campus Backbone of 155 Mbps (megabytes per second)

1300 2000 2000 Not a Standard

Campus Backbone of 1 Gbps

1300 550 5000


(gigabytes per second)

Building Backbone of 1 Gbps

300 300 Not a Standard

Building Backbone of 10 Gbps

850 300/550 Not a Standard

Table 4-11: 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.

4.5.1.2.2.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.

4.5.1.2.2.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 Gbits/sec and 100 Gbits/sec, which is why this technique was selected by IEEE 802.3 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 Fibbers. 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 Mb/s to 10 Gbps, Fibre Channel from 1 GB/s to 10 GB/s, and ATM/SONET/SDH from OC-1 to OC-192.

4.5.1.2.2.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






Figure 4-25: Tight Buffered Fibre Optic Cable


4.5.1.2.2.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.

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-26: 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,

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-27: Example of Bonding as Per ANSI/TIA-607-B


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

4.5.2 Smart City Converged IP Network

The Smart city Converged IP network within the building follows the same architecture as defined in Section 2.3 above. For details please refer to the same section.

4.5.3 Smart City Wireless Network

The Smart city Wireless Network within the building follows the same architecture as defined in Section 2.4 above. For details please refer to the same section.


5 ICT Tenant Fit-Out

In order to provide office tenants access to the Smart City Services within their facility or enable tenant to outsource some of the office management services to d3 it is important to establish physic network connectivity within the d3 Smart Services network. To fulfil this requirement a Tenant Consolidation Point is proposed for different user types either in residential or commercial space. The following are the three different types of consolidation points within the buildings.

5.1 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 Building or Floor Consolidation Rooms, 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. Two-core fibre cable from the Smart City Main Consolidation Room or 2 x Cat 6 or higher cables from Floor Consolidation Room 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 Primary or Secondary Fibre Consolidation Points. In the interest of saving space within the apartment it is necessary 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.

5.2 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 Building Consolidation Room/Floor Consolidation Room, 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. Four-core (Two for day one use and two for future) fibre cable from the Building Consolidation Room or 4 Cat 6 or higher cables from Floor Consolidation Room must be terminated in the OCP. In the interest of saving space within the apartment it is necessary 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.

5.3 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 on patch panels/IDC modules, two or four core fibre cable from Building Consolidation Room/ Floor Consolidation Room, 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. Four-core (Two for day one use and two for future) fibre cable from the Building Consolidation Room or 4 Cat 6 or higher cables from Floor Consolidation Room must be terminated in the RCP. In the interest of saving space within the apartment it is necessary 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.

6 Standards and Refrence Documents

Standards and reference documents can describe good practice in a way that makes it easy to know exactly what needs to be done to comply with it and, just as importantly, to know what to specify in procurements in order to be sure that what is supplied is fit for purpose. One of organisation that has a gone a long way in defining Smart City Standards and Reference requirements is the British Standards Institution (BSI). As defined in their document PD 8100:2015: Smart Cities Overview guide Standards are developed by experts in a particular area of interest, using a transparent consensus-building process that allows a variety of stakeholders to provide input. Figure 6-1shows the three levels of standards relating to smart cities – strategic, process and technical specifications, each of which can play an important role in ensuring that the smart city is built on firm foundations.


Figure 6-1 Standards for developing Smart City Standards

6.1 Strategic Level Smart City Standards Strategic-level smart city standards provide guidance to city leadership on the process of developing a clear and effective overall smart city strategy, identifying priorities, and developing a practical implementation roadmap and an effective approach to monitoring and evaluating progress.

6.2 Process Level Smart City Standards

Process-level standards cover good practice in procuring and managing cross-organizational and cross-sectorial smart city projects, including guidance on putting together appropriate financing packages.

6.3 Technical Specifications Technical specifications cover the practical requirements for smart city products, services and spaces to ensure that they achieve the results needed. Strategic-level standards are of most relevance to city leadership and process-level standards to people in management posts. However, even technical specifications are relevant to people in management posts as they need to know which standards they need to refer to when procuring technical products and services.

6.4 The BSI smart cities portfolio City leaders need to decide where to focus in applying new smart approaches. There are a number of routes that can be followed, and invariably the best answer may well be a mix of these. The BSI portfolio presently includes a large number of service-specific level 3 technical specifications. Many are relevant to smart cities, though few, as yet, overtly address the integrated services agenda. A number of level 1 and level 2 documents have been published or are in development, specific to the smart city agenda.


6.4.1 Level 1 leadership guides

PD8100, Smart city overview – Guide

PD 8101, Smart cities – Guide to the role of the planning and development process, which gives guidance on how the planning and implementation of development and infrastructure projects can equip cities to benefit from the potential of smart technologies and approaches.

BS ISO 20121, Event sustainability management systems – Requirements with guidance for use deals with all pillars of sustainability with a focus on community level interventions.

Ongoing developments will continue to support city leadership:

business case, business models and funding are topics presently being considered for standardization, in order to help decision-makers better understand how best to engage smart services;

a city performance assessment method is also planned.

6.4.2 Level 2 process frameworks

PAS 180, Smart cities – Vocabulary, which defines terms for smart cities, including smart cities concepts across different infrastructure and systems elements and used across all service delivery channels.

PAS 181, Smart city framework – Guide to establishing strategies for smart cities and communities, gives guidance on a good practice framework aimed at decision-makers in smart cities and communities from the public, private and voluntary sectors to help them develop, agree and deliver smart city strategies that can transform their city’s ability to meet future challenges and deliver on future aspirations.

PAS 2070, Specification for the assessment of greenhouse gas emissions of a city – Direct plus supply chain and consumption-based methodologies aims to provide a robust and transparent method of quantification, attribution and reporting of city-scale greenhouse gas emissions.

PAS 182, Smart city concept model – Guide to establishing a model for data interoperability,

provides a framework that can normalize and classify information from many sources so that

datasets can be discovered and combined to gain a better picture of the needs and behaviours

of a city’s residents and businesses.

New work on a number of priority topics for level 2 standards is being investigated,

including:

Collaborative procurement;

IoT alignment;

Building information modelling (BIM) alignment;

Open data code of practice;

Data privacy and security;

City systems resilience;

Service accessibility.

Figure 6-2 shows the portfolio of strategic and process smart city standards being

developed by BSI, mapped to the smart city process framework.


Figure 6-2 Smart City Standards mapped to the Smart City Process framework

6.5 Work of other standards bodies Guidance is also being developed on a range of other smart city issues by partner standards

bodies globally. Some of the most noted standards bodies and their work streams are listed

as follows:

ISO – specifically in the work of TC 268, the technical committee that is working on standards

related to sustainable development in communities, including indicators and management

standards for smart community infrastructures.

IEC – the International Electro technical Commission, specifically in the work of SEG1

that is looking at the electro-technical standards needed to enable the integration of

city systems.

ISO/IEC JTC1 – the joint technical committee of ISO and IEC that is responsible for

ICT standards – that is looking at the role of ICT standards in smart cities.

ITU-T – the Standards-making body of the International Telecommunications Union,

through the focus group that has been set up to look at the telecommunications

standards needed for smart and sustainable cities.

CEN/CENELEC/ETSI – the three European Standards organizations and the joint co-

ordination group they have set up to review the need and scope of European

Standards for smart and sustainable cities and communities.

ISO TMB Strategic Advisory Group for Smart Cities – set up to help facilitate better

co-ordination internationally among standards bodies. BSI provides the chair for this

group.

Figure 6-3 provides an overview of international smart city standardization activities. It can be

expected that over the next few years a great deal of useful standards and guidance

documents will be developed through these different standards bodies that will help support


the progress of UK cities in becoming smarter. BSI will act as a key information source to help

city leaders identify those standards of most relevance to the path their city is following.

Figure 6-3 International Smart City standardization activities

6.6 Standards Publications For undated references, the latest edition of the referenced document (including any

amendments) applies.

BS ISO 20121, Event sustainability management systems – Requirements with

guidance for use

BS ISO 37120, Sustainable development of communities – Indicators for city services

and quality of life

PAS 180, Smart cities – Vocabulary

PAS 181, Smart city framework – Guide to establishing strategies for smart cities and

communities

PAS 182, Smart city concept model – Guide to establishing a model for data

interoperability

PAS 2070, Specification for the assessment of greenhouse gas emissions of a city –

Direct plus supply chain and consumption-based methodologies

PD 8101, Smart cities – Guide to the role of the planning and development process

6.7 d3 Specific Reference documents. Following is the list of documents that can be referenced for more details in case required to understand the background, purpose or more details.

1 Service Catalogue 2.00 21/06/2015

2 Service Strategy 3.00 06/07/2015

3 As is assessment cum designs guidelines document

2.01 18/10/2015

4 UAE Fire and Life Safety Code of Practice

Edition 2011 06/2011

5 FIT-OUT GUIDELINES (issued by Zoning Authority – TECOM)

Rev 1 06/06/2008


6 Traffic Safety Guidelines (issued by Zoning Authority – TECOM)

Rev 0 04/03/2008

7 MEP & Sustainability Design Guidelines

A-Draft 12/08/2010

8 Power Supply guidelines for Major Projects (issued by DEWA)

Update – June 2014 06/2014

9 Distribution Substation Guidelines (issued by DEWA)

March 2007 22/03/2007

10 Regulations for Electrical Installation (issued by DEWA)

1997 Edition 1997

11 Environmental Regulations for the Reuse of Treated Wastewater fro irrigation & Thermal Treatment Sludge Agriculture Purposes (issued by Dubai Municipality)

Technical Guidelines Number 13

June 2011

12 Telecom Infrastructure standards for buildings (Issued by du)

V.5

13 Health and Safety Environment (HSE) Regulations (issued by Zoning Authority-TECOM)

Rev 1 29.10.2008

Table 6-1 d3 Specific Reference Documents


7 Appendices

7.1 General Guiding Principals

7.1.1 The Network as the Platform

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 development. In addition, it also includes functionalities like the CCC, Contact Centre to deliver the Smart Services. The city wide 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 the development. The data centre will host the servers of Smart Services. The Smart City 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. This IP network will be designed for all buildings within the development and will extend to the public spaces outside the buildings. The IP Network is a converged network that will enable all systems, sensors and devices within the development. The d3 IP network will be used to deliver all smart services. The regulated services will still be provided by the telecom operator using their own active and passive networks.

7.1.2 Convergence of the ICT Infrastructure

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

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 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 Provide owners/operators with greater operational flexibility, e.g., the

ability to operate several buildings from one control centre, improving effectiveness while reducing cost

• 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, etc) 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 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.

7.1.2.1 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 7-1 Data Virtualization

Business Directory

Discovery

Studio

Adapters

Manager

Deployment Manager

Monitor

Active Cluster

SQL(ODBC, JDBC, ADO, .NET

Web Services(HTTP, SOAP, REST, JSON, OData)

Messaging(JMS)

Hadoop(Input Format)

Front-end Applications

Data Virtualization Server

Security

Federation Engine Cost-based Optimizer Rule-based Optimizer

Views, SQL Script (Database Centric) XQuery, Java, WSDL, SCA (Services Centric)

Caching Quality Governance

Security

URI Hadoop JavaMF

AdapterApplication API’s

Messaging(JMS)

Web Services

(REST, SOAP)

SQL(ODBC, JDBC)

Data Virtualization Platform

Management Environment

Development Environment


Data Virtualization 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. 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/PM

Siemens Desigo

FM Reflections

ESRI/GIS

Empower

Figure 7-2 Virtual View Layered Architecture

These applications will be integrated within the scope of this 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.

7.1.2.2 API Management

The API Management layer may be provided by an Integration Platform 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. The integration platform shall provide the following two functions:

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

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

Figure 7-3 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.

Figure 7-4 API Management Platform

The platform promotes faster deployments:

Integration Bus API Manager

Integration Platform

SAAS Application Social Data Cloud Data Partner DataDevices

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


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 7-5 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

Figure 7-6 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 Integration Platform for process innovation with Internet of Everything (IoE) and

mobility solutions.

SAAS Application Social Data Cloud DataPartner Data Devices

Enterprise App’s Custom Apps Enterprise Services

Ecosystem Partners Customers

API API APIAPI

API

Employees Processes Devices DataInfrastructure

API

Integration Bus

Prebuilt Connectors Transport Transform Mediate Manage Data ServicesVisual Flows Process Events


Figure 7-7 Creating a Value Chain and Ecosystem

At d3, the API Management is out of scope for now, but it is necessary at a later stage to design and build this layer in order to create an automated integration platform for process innovation with Internet of Everything (IoE) and mobility solutions. 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.

7.1.3 Transformation/Service Delivery

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.

Production Consumption

API Catalogue App Market Place

APP

AppExchange

APIs API Management Platform

APPs App Store

Service

API

Platform Administration

Tenant Administration

API Owner

API Developer

User Community

APP Developer

https://en.wikipedia.org/wiki/XML

https://en.wikipedia.org/wiki/Representational_state_transfer

https://en.wikipedia.org/wiki/JSON


7.1.4 Automation of processes and systems

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 Smart City Maturity Model as shown in the Figure 7-8 identifies and describes five stages to maturity and key attributes of each phase:

Figure 7-8 Smart City Maturity Model

Automation, which consists of the digitization of the city systems and processes, is essential in moving from the adhoc 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. 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.

7.1.5 Easy Accessibility

One of the key requirements of Smart Cities is to ensure that the city infrastructure and smart services are accessible to individuals with special needs and abilities equally. The consultants and the developers have to ensure that the infrastructure and the services are built keeping in view such requirements in physical design and functionality. Such series shall impact designs in public areas and common areas of the development.


8 Glossary

ICT Information and Communications Technology CRM Customer Relationship Management KM Knowledge Management HR Human Resource PFC Primary Fiber Consolidation SFC Secondary Fiber Consolidation BCR Building Consolidation Room FCR Floor Consolidation Room FE Floor Enclosures ACP Apartment/Villa Consolidation Point OCP Office Consolidation Point RCP Retail Consolidation Point CPE Customer Premises Equipment ISP Internet Service Provider FTTN Fiber to the Node/Neighbourhood FTTC Fiber to the Cabinet or Fiber to the Curb FTTB Fiber to the Building FTTH Fiber to the Home FTTP Fiber to the Premises FTTx Fiber to any CAPEX Capital Expenditure OPEX Operational Expenditure OSP Outside Plant PoP Point of Presence QoS Quality of Service PoE Power Over Ethernet WLAN Wireless Local Area Network WAP Wireless Access Point RAP Root Access Point MAP Mesh Access Point CCC Command and Control Center PWN Potable Water Network SWN Sewage Waste Network SDN Storm Drainage Network FFN Fire Fighting Network IWN Irrigation Water Network CCTV Close Circuit TV RTA Road Transport Authority RESTful Representational State Transfer SOAP Simple Object Access Protocol API Application Programming Interface JSON JavaScript Object Notation XML Extensible Markup Language SCADA Supervisory Control and Data Acquisition EVCS Electric Vehicle Changing Station DEWA Dubai Water and Electricity Authority KPIs Key Performance Indicators IEC International Electrotechnical Commission EN European Standard IEEE Institute of Electrical and Electronics Engineers UPS Uninterrupted Power Supply


ISO International Standards Organisation GUI Graphical User Interface BMS Building Management System HVAC Heating, Ventilating and Air Conditioning DDC Direct Digital Controller ASHRAE American Society of Heating, Refrigerating, and Air-Conditioning

Engineers SCS Structured Cabling System ANSI American National Standards Institute TIA Telecommunications Industry Association UTP Unshielded Twisted Pair BAS Building Automation System NOC No Objection Certificate NOC Network Operations Center

Please refer to the CCO Internetworking Terms and Acronyms Guide at

http://docwiki.cisco.com/wiki/Category:Internetworking_Terms_and_Acronyms_(ITA) for

additional terms.

http://docwiki.cisco.com/wiki/Category:Internetworking_Terms_and_Acronyms_(ITA)


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.