• No results found

DC110 Data Center Design and Best Practices Version 1.4 Student Guide September 2010

N/A
N/A
Protected

Academic year: 2021

Share "DC110 Data Center Design and Best Practices Version 1.4 Student Guide September 2010"

Copied!
253
0
0

Loading.... (view fulltext now)

Full text

(1)

Dat:a Cent:er

Best:

Version

(2)

DC110

Data Center

Design

Best Practices

(3)

o Copyrlghl 201 0 by BICSI

Printed in the United States of America Version 1.4, First Printing

Bicsi"

All righlS re\!'"rwd. No pan of this workbook may be used, reproduced, or uan'>mined in any form or by any means, electronic or mechanical. including photocopymg, recording. or by any information storage and retrieval system, without prior agreement and "'fltten permission from the publisher, except for the inclusion of brief quotations in a review.

Thecoments of this workbook are subject to revision without nolice due to continued progress in methodology, design, and manufacturing.

THE GUIDE IS PART OF THE BleSI DESIGN COURSE CURRICULUM AND IS PRESENTED H 1\ WITHOUT WARRANTY OF ANY KIND, RESPECTING THE CONTENTS OF THIS GUIDE INCLUDING BUT NOT UMITED TO IMPUED

WARRANTIES FOR THE GUIDE'S QUALITY, PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR ANY PARnCULAR PURPOSE. BICSI SHAll NOT BE LIABLE TO THE PURCHASER OR ANY OTHER ENTITY WITH RESPECT TO ANY LIABILITY, lOSS, OR DAMAGE CAUSED DIRECTlY OR INDIRECTLY BY THIS GUIDE.

All brand names, trademarks, and registered trademarkS are the property of their respective holders. BleSI lX'odd He.ld<juarlcr~

8610 Hidden River Parkway Tampa, Fl33637·1000 USA

800.242:.7405;+ 1813.979.1991;~x"'1813.971.4311 \Neb sill': www.blcsi.org

(4)

S1"dom Guido

o..t.t

Centw& & Tho Datolgn Pmco ..

CQU~:

DC 110 Data Center Design

&

BlI&t Practices

This Is;, c:ourse em Oat.l

Center

Design and

Best Practices, the plimery

source for

the

matenal presented

here

Is:

(5)

S..-Ouldo

Module 2: Data Centers and the Oeslgn ProC:e$$

Module Goals

2.1

lNs introductory module is meant to introduce !he basic cor'ICepr:s assoClated with data centers and data center design; after finishing this introductory module you should be able to:

• Identify and distinguish the 3 primary types of data centers • Identify !he typical structures and systems thai make up a data

center

• Identify !he 4 bilsic stages

of

data center design

...

(6)

Stud ... GukIo Data C ... & Tn. Doslgn Proe ...

Data Canhtr Ovarvlew

2.2

Data Centers contain mission critical computer systems.

In

addition to computer hardware, they typically Indude:

o Sped.,.1 environmental controls and cooling systems o Specia I electrical systems and backu p power supplies

o Redundant data communication connections

o Special high-security systems

o Build Ing automation Ii 'control systems

Data Center Types

There are three basic types of data centers:

o Enterprise Data Centers

• Internet Data Centers • Collocation Data Centers

Enterprise Data CenleB

2.3

2.4

Enterprise data centers serve a single cllent·s data proc ... ng and IT eq uiproent storage needs. Enterprise data centers typlca Ily possess:

o Placement on the same physical site as a dient's other business

operations

o less redundancy

• Cost management as a primary design driver

Internet Data Centers

An Internet Data Center (or 'managed hosting facility') manages IT systems and applications fot off-site customers. Hos~ng fadllties typically encompass:

• Higher

hardware

densities

to maximize potential revenue o Greater redLlndancy

o Availability/uptime as tile primary desJ9n driver

<4OI.aiC$/'

(7)

Slude", G .. de

Collocation Data C.."ler

1.6

A ooIlocatlon facility

provides space,

power, and cooling

for

different

customers' IT ~quillme"t. Collocation faciHties typic~lIy

posS</SS:

• Uirqer floor are". tha" Enterprise alld Intemet data centers • Lower equipm,,"t densities

• M ore centralized patch fields and distributed networks

• Seculity and spacing requirements as primary design drrvers

Data Center Deslgn-$trutlures \IS. Systems

2.7

Data Center desiqn involves not only building design and layout, but also \t1e design and Jayout of Infrastructu~ systems, such as the design power, rooling, voice. & <lata cabling, and control systems

Power VOK:~& Data C.bling Autom.~on &. Cooling Control

~

Syslenu

(8)

81udontGuldo Data Cantlrs & The DHlgn Procan

Component

Structures

2.8

The physical components of data centers Include: • The computer room

• The building support spaces

• The supportJng off-sire services and structures

~~ vll~ 'PII'

l..uk .. II'I'"'"f.iII .... \~"".,II'"' ...

0UCIfflS .Jtn!1IG s~ IlllUlIIe:

..

~,,.*

..

,

I

...

,

D

Et'u.J1K1 roo!'I()l DltAQtIll:efd~ .l1li

_tI\Tif'rC.Jl~m.

...

,

"\

/

"

0

Tw"""m~~1

I

~room,allll ~"'"

....

~'I~nll ~

...

lMtJ...,ooclcl

I

I ;

I

can,llwbl. Raon

(9)

The Compuler Room

2.11

The heart of a data center is a computer mom housing IT equipment racks, a main cabling distribution "",,,, and often a special area for gigital information storage (or Storage Area Network (SAN»

,-

- -

;i~c;.,;;,,;-~

-

- -I

I

"~-·a

-

~""r=Q'''''A. I I M - '

""'

..

...-

t--::lo" .... ~"'l{It'U """M

I

OfIIbot. c.-~ I ___ I c - t .• ~

-

--

--

.

..

...

,----

....

---,

i (AI .. , ..

I

""'"

"""-

I .1-hI<\.I~' ,

-,

~i~ : e:. .. "i! MaiI1 Oi$(ribullon

I

I n.r..:.tII~'" A, ... ~~

..

I

Tel..ooro RMm

""'"'"

/l,t.:lln elU!!l!f-Cllm-..'1,i C:jIm4If £qu~ 0I- I

I1r.ot11Ont.1ll Cro!;1li'COOI'1llU

,oa,:, e e q.rp!T'el1 ~ ~1f1.1 Hdril'QI'IUoI o.JJWn:CI~DI'l

QI~,-r.-nt'\I""..t I I

.

I

~~Ir' l~"'~R~_1

/

~laI DIroIll'ilMltivn ~ OI .... lmutioII "

,,/

.,..

...

ijMi:....,1,fI1 Ct~1WI9d HlilrIllll!Ml c~·c.:..~

."

!

""

A()

:

,...

f._"".

.,~' " ,,1 ,J

,

,':

(10)

student Guide Data Coni". & Tho

Doo;go

P"' ...

The Building

2.10

The computer room's location within a particular build ing needs to be

designed

w~

power, security, ilnd cooling recuirements foremost in . .

';1;-

;

i,,>(»">

mind "" ~ -' . t ··~ ( ' ~~'A .

-

,

f

;>' o5tlrr.1l1t M~u'~

- - - - -

-

- -

I "1.1-0", I ~l'''' EI",,~ ~~

....

'''. I t".crf~~~·

"""

IV,'".. 1'Ic:.c.o: I lon:~" olI,. NC1'.I.oro Aor",,~.

I ~ ... ;

...

-

-

- -

-

-

-",..Ccn> PLr.:lf ~

,

...

,

-

-

- -

-

- - - -

-

- I ~~~'"

I

I H"",,~vr, I !orI~' IIr.d: "~I I .. »

J Ir)~,. L -

-

- -

- - -

- - - 5.~~,.:t! JiIl.!'''''~1 wcu"'"<~~: ~~~. ~~~r~L=I.l.;lln= MQ~~.", !

I

l;<=Im

I

""',

ep,il~r ';'OE;<r

..

~ .r .... .,.,., .... ' mt~' ""~ ~ DC 11.: DMI c~ DwiIP1" "f"~ H

(11)

Student Guide

Off-sfte

Off'slte components of the d.", centerolten Include: • Power and Telecom Access Providers and Feeds • External 'Generators

• Emmal Thertnill Storoge I Water Tanks

• Offslte - Data Storagel Dis. ster RecOIIery F"dlities

I _ eu.o..n~ IIUIOI'« Wi_1OI Q -

H.I...,.

! · ... 1"")4'11 .. _

' _~«o':_

Data Center Infraslructunl

,. ~ 11ft~_

,,-

~ ... "leICl'

to

"

_ "" __ .. _

... .... _ 1 .. """. I'II,\4 ... ~

2.11

2.12

In addition to the physical components, data center design

encompasses inft-astructure systems and their inter' relations. These systems include:

• The Electncal Systems

• The Heating and Cooling Systems • The Telecommunications Systems • The Automation ContnJl Systems

...

(12)

Student ~Ide

Data CenlN Electrical Systems

Data

Centers require b~cku~ electrical systems and generators to

ensure continuous operations and must SErve increasingly high

electrica I loads to hill her density blade

se

...

[hote Centar Coonng Systems

2.13

2.14

Mnst of the electrical load delivered

to

data center IT e<julpment will be

converted

to

heat which must be removed to prevent the e<julpment

from

malfunctioning

Data Center Telecommunications &

Cabling

2.15

The IT equipment in the data center will need to be connected witn

both internal and external computer networks, creating uniquely dense

cabling req uirements

Data Center Control Systems

2.16

Data Centers are

Increasingly designed with

a

'lights

out'

philosophy, minimizing access to equipment and creating the need for unique

monitoring and control functions

Data C ....

ter

V$. Standard Facliity Design 2.17

As

a

mlsslon-crttlc.1 facility,

Data

Center design differs from standard

facility design in many ways, induding:

- 10 to 30 times as much power as a standard office space

• Equipment densities 3 to 5 times denser than standard offIce s~ace

• Operating CC'st 2

to

3 lime higher than stan~rd office space operating CQ.sls

(13)

&luaent Guidt

Integrated Design

2.18

The data ~ef1ter design process needs to refiect the different n~ture of data ce'nter requirements

• Data center design should be

integrated

rlIther than linear to

ensure effldent use of IT, power, and cooling assets

• Maximum coordination is required during

111e

earliest plMnlng

stages for efficient data center power usage. cooling. and cabling

arcn~res

Data

Cenlar De8ign

There

are 4

kev considerations in data center design: • Avail. bllity

• Scalability

• Security

• Efficiency/Cost

AvaHablllty

The primary purpose of the data center is to ensure cuslOmer and

employee access to data and computer applications whenever It Is needed

.Sample Downtime Costs Per Industry. per hour:

Stock brokerage:

Finane<!.

Credit Card: Bankins:

Media COmpa

ny

:

Cross·lndustry Individual Company average:

oDl'O'IO Bidil'

:>-10

BICSI p ... taty pr,~ ~otCo~'1

$7.000.000. $3.000.000. $3.000.000 $1.000.000 $47.000

2.19

2.20

(14)

StudonlGuldo 0 ...

c.nhM'&

& Tho Dooign PrOCH.

5<:alability

2.21

The potenti~1 for growth must also

be

consi~ere~ in ttle data center's design

• Large businesses typically experience 50% growth In data

per

year

• Power reqUirements for a data center can dou ble over the course of 2 years

• IT equipment

will

often

completely

turnover

over the course

of

3

yea...

IL

.

,f

.

,.

..

r\rk ....

~:~~,.o.'\ ~-:. ,J(tH.~~

S(....1.:... ''()

(,.tr"'h_~ · )

Security

In addition to insuring reliable "ccess,

the

~"ta center designer must also

protect

against unauthon,.,d

access

"nd

10 ••

of phy'i,.1

_ssets.

Secu

rlty question. datil

center

·

de5ign., ...

need

to

add ress:

• How is the data to be protecte~ from criminal threat?

• HOW

is the

data

to

be protected from

natural

disaster~?

Efficiency/Cosl

2.23

Data center design must consider not ",,'y initial costs, but also the total cost of a fadllty over Its IIfetlme. Considerations r<!garoing effiCiency that designers should address I nelude:

• How much redundilncy is it worth p"ying for to ensure availabil~y? • Are the power requIrements belnlJ met efflc",ntly?

• Is the IncINsed cost of newer equipment justifiable, given Its nigher power ~nd cooliny requirements?

• Is !he building

space

being utilized effidently?

Client CommunlcalJon and tbe Design Process

The data center design process Is driven mOr<! by unique client IT equipment needs rather than standard person nel spaci og and now requirements

• Because of this, the data

center

deSigner must

gather

as much inFormation from the dlent as possible about their Information teclmology needs, plans, and goals

(15)

student Guido Data Cent*" & lh& Dallgn PI'OCOIIiS

Data Centers and the Mission' Critical Design Process

There are four essential steps In deslgnlng mission critical lacilltle~

such as data centers: • Risk Ana lysis • Problem Definition • SOlutkln Development • Implementation

The Design Process, Phase

f:

Risk Analyels

2.25

2.26 Risk analysis i. the process of balancing fulllre costs <>f downtime with

til

e present costs <>1 p~ntion

• Data Center risk. analysis addresses three key design fealllres: Operational reqUirements-the opportunity

to

suspend operations lor maintenance

Availability reqUirements-the targeted uptime of the system during operations

Impact of downtime-the Impact of unplanned dis,upHons

RIsl< Analysis & the High Nines of Reliability 2.21

Wh~e customers and clients may seek "6 nines" In terms of reliability. risk analysis I~ the process of balancing that desire against the high costs assodated with Insuring limited downtime

O2IItO

.1CSi'

Reliability 99% 99.9% 99.99% 99.999% 99.9999%

Visruption TIme per Year

as hours

8.8 hoors S3 Minutes 5.3 Minutes

(16)

student Guide Data ~ & The D.,.lgn Proceso

Phase II: Problem DefInition

2.28

rusk-analysis estabflshes a target I'l!4labllity level for a facility while problem definition concerns tne task of meeting this ta'llet In terms of:

• Facility space

• rr

assets

• Project locatk>n • Proj

ect

budget

The end result of the problem definition phase of design i. the creation of the fBdflty program

Phase III: Solution Development 2.29

The third stage of Oata Center design Is the development of one (occasionally two) design solution(.) to be submitted to the dient for approval

The design solution phase usually involves: • Planning

• Space Programming

• Cost Estimation

• Const",Clion Documentation

SoluUon Development: Planning

• Planning typically Involves coordination between technologlcol consultants and architects regarding:

- Space - Power - ·Cooling - Security - Fioer leading - Grounding - Eledrical protection

"J."".

'Ql

\ .. '1.'\

- Telecommunication pathways

..

"

a!csIP~~NotcQFIY 2.30

(17)

StucMnt Guld. 0 $ C."tar& & Tho DesIgn Pro:esl

Solution Development: Spac:e Programming 2.31

Space Progrclfnming requires estimating data center requirements at rull capacity

f1Jr:

• IT hardware &. ",cks

• Electrical Equipment • HVAC equipment

• Space

for

personnel

amI

airllow

• TelecQmmunications equipment and cabling

• Furu re

growth

Solution

Development: Cost Estimation

2.32-33 Cost estimation involves COflsideration of one-time, recurrent, and Intangible

costs:

• One time costs:

- Real estate costs - Local tax Incentlve~

-

Cost to

bring utilities

to Site

- Demolition and site prepitrittion costs

-

Cost

of temporary 5e/Vlces to support

IT

migration

-

Cost

of equipment relocation

- ConSillrant costs • Recurrent 'Costs

- Utility usage costs (power, water, sewer, gas) - Telecommunication services

-

Wages

- Lease

costs

- Taxes

• Intangible Costs

- Availability of alternate or multiple telecommunications access providers

- Availability of utility se/Vices - Availability ot transportation

H.

(18)

Student <kIld. ON Centers & Thll o.sign P'tocMI

"haae IV: Implementation

2.34

Alter ~ clesi9" solution has been chosen, the final stage of data center

design takes place

which Includes;

• Construction

, Commjssioning

Conflnlction

....

.. '

c

(Ii

---"~~

'

d'

+"""

;

"

O

'

~

»

[).

'

l~J"i)

2.35

The construction

phase

of design typically lndudes the coordination of

• Structural proje<ts • Mechanical projects • Electrical prOjects • cabling projects

Commission Ing

Commissioning Includes;

• In~lI.tion of vendor equipment • Fi<!ld testirlll equipment

2.36

• Oevekll>ment and lmplementatlon of oper-..tio",,1 and maintenance procedures

(19)

Dot> C."".r& & Tho Dool911 Proan

Review Questions

1. What are the

3

types of Oata Centers?

- j ,

, '::f~~tr

r

I ,.,~ " \: I'-

~

v

"'" \

..

\Uhl(f"L~

'i

~

.

"

2. What are the 4 key design criteria or data centers]

_

{I",,\

h

!e

"

.

l ..

~

-

'7(,,\,,~ I,~

S<~rl~

-

(\\';L'C

••

;,{\

f[c'J\

J. What are the 4 st~ges of mission rrltlcal facllltv design?

- Ri4<-

f\""\~ ~

..

- ,(robi"",-

\)

i.\

'

I"

\.

'

\)1'.

_

.:,,!

"

"

~\

'tl"

\)<I..,;t\

(20)

Risk. RMllability . .. Class Ranklngl

Module 3

;

Risk, Reliability.

&

Redundancy

Module Goals

3.1

A first step in data center design is determining a target reliability

dass; ofter completing this module you should be able

to

:

• Identify tt1e components of a reliability class ranking determination

Determine a target reliability class ~iven customer reQuirements

• Use a cost

benefit

analysis to communicate the benefits of a higher

Initial investment

to

adient

'0'

(21)

Reliability & tile Risk of Downllm&

,. target reliability class results from balancing the future cost

of

downtime vs. the present cost of prevention • Reduced downtime~ increased redundancy

• Greater redu

ndancy

=

increased cost Data Centers and Target Reliability ClasBes

3.2

3.3

.,..-:

i..1J~ \?

, h

\7-J ....

\""'e~~

Data centers are typically classified according

to

iI 4-01 .... ranking

system

• OilSS F1 is the lowest In terms of reliability (avalla~lity - 99%). and Class F4 is the hl9hest (availability g 99.999%)

"'f

I-i""~·

( • As dasses correspond {in part) to fulu", availability forecasts, their

I

/"'n ;,

"'>"

classlfk:!tkm tends to

be

both

art

and science

-h-V cft... .... ,1+IY?i

~d.Jj~' E~en

SOl it i$ Oil usefuJ met1ic lor balandng the cost of downtime with the cost of prevention

Components

of

a Reliability Clan

Ranking

3A

Setting a target reliability level for the data center requires: • Determination 01 operallonal requirements

• Determination 01 availability requirements • Delermi" atlcn of Impact of downtime

"~

"

· ... 1 .

'

..

.!"":':::;.

.

~~~

,

.'

'"

--"

.

...

-.

, ,.

'

_ft4iInd~

I I _" r ' , O2IItO

aics

,

"

(22)

Student Guide R .... Rollobilly. & C ... Ranklngs

Determining Operational Raqui",menta

3.5

The operational requirements account for the time the facility's

components must be operating. plus time allowable for maintenance:

Deoc:r1.,- Ann .... 1 Allowable D_allon.1 LAlv.1

... 'nten.nce Hours

Where fUflCborlS are operational ~$

!hall 24 ,",ou'! ~ d.y, hiss tha~ 7 dt"'~" >400 Level 1

...

Wher.e fum.tions ar.e Clpercrtional up 10

24 hours. iii day, 7 days..a wiNk. up to 50

>200 ~el ~

w~k$ ~ ~r-and l1I.\11tntenOlnce time Is

av;a.ilallie durin~ wort:in~ hClUl'S WMt'C' Nnaloni "r. olM!r~~.Il4

b(lllJr,s a ~V, 7 dalf' fI \lIftk, for SO

we!!ki Of" more-and no time Gan be >0 I.1!vel 3

made available -durins wort:ing hours tOf"

mai~nance.

1NtIe1'1' JundiOtl:ii Ir!!" opt(ttloNf.4

oo,,~ l:I .cW, 1 d.iIys II we~ 52 Y/ft:Ic$ 0 Level 4

each year

(23)

Student Gu5de lIi.k. R"Uabmty, & Class Ranklngs

Detennlnlng Operational Requirements

3.6

Ca

lculaH n9 the ~me In hours that the data center systems ca n be

brought offline for ma I"tena nee allow$ one

to

detefTTline an operational level

• For ""ample, Jf a facility could allow for 120 hours of maintenance

per year that would put them In Operational Lf!'Ie/ 3

Annual Allowable

DeIIcrlpilon Maintenance Operational

HOUfS level

Where functions are opermional I ... th,,"

>400 Levell 24 hours a day. Ies.; than 7 days a week

Where . ,,~are v>"',, up_to 24

hou rs a day, 7 day. a week. up to 50

> 200 Level 2

weeks a year- and maintenance time Is

available hours

Where tunctions are operational 24 "vu,~

a day. 7 days a week, for 5<1 weeks or

Level 3

more-a nd no time ca n

be

made .vailable >0

during working hours for maintenance

Where f" are operational 24

hours

.

a day. 7 days a week, 52 weeks each 0 Level 4 year

H

(24)

Student Guide RJ~. Reliability,

a

CIUG RAnking,

Determining Avanabllfty Re'l"lrements

Availability

Is

the total

uptime

a fadllty must support. It can be

expressed as an A "ailabillty Ranking, lying at the Interse<:tlon of an intended

maximum

annual downtlme and the Ol)erational level,

AIIorwllble UBiIlfmurn Ann .... Twgotad AvaJaWRy

Dow"' ....

III'n .... )

" ' - 9 0

500 -5000 9910 99,9

50 -500

",,-9

10 99,00

5-50 99.99 10 00,_

0_5- 5.0 00,99910 00,9009

Alow.bie Mauntwn An"ual OtJlMltme ( .. in . . . . )

Opel'Btiol1ii1

__

50-SUO 5-50 0,5 - 5.0 Lo .. 1

le,..'

1 1 2

"

L~'tt!I :2 1 2 2 3 Le'fEI1 3 2 2 3 4 L.:i'fi!l14 3 3 4 4

D8lllrml

nlng

a Sampl" Availability Ranking

We saw .... rlier tltat a fadlity

that

could allow fot 120 hours of

maintenance

was in

Operational

Level 3

3.7

3.8

• If the target availability for this facility was

to have no more tha n

a

hours (480 minutes) of unscheduled

downtime a year,

then

the

target

avalhlM/lty rtlnkfng

of

the

faci

l

ity would be Level

Z

AII .... b .. Mu'mum - . . , D _ .... (lI'n_)

OperdoQeI !!OO ....,..., B - 5DD

.-50

0,5 - 5J) Lo .. , LeYoEll1 1 'II 2 3 L'I'<r 2 1 2/\ 2 3 ~ 3 4 ~14 3 3

4

(25)

stoliont Guido R1.k. RoII.blllly. & CI ... Ronking.

Determining the Impact of Downtime

3.9

Not all downtime has

the

~me Impact.

There are fou,

downtime 1m pact dasslHcations:

Description Classlflcatl""

lmp,(t of downtime Is tocalln scoper and iIIf'Yects only a sft'lgle site or

QperBticn, or results in a minor disruption or delay In 8chle\l1ng keo; La ... 1

orqanizatiooill Qbjective.s

Impact

0'

downtime i$ regional In scope, affeaing a portion of tt,le

enteo'pn •• (although not in Its entirety) or ,esvlling In a mod...,.te Regional dlsruptjon Of'" delay in achieving key crganlutfonal Objed:tve5

Iml'act of downtime is m ulti~reg lonal In scope, arfecttng a majOr pO<t:lon

or

th. ent.rpM •• (although not in its enti~ty) or .... sulting In

Multl-~Io""t

p mC!ljor dlsruptfon or delay in iKhieving key organtzatronal

objectives

Impact ¢ downtime I. global In !i<Dpe and affects the quality of

service delivery across the enttre enterprise, Qr results fn 21 Enterpri&e -siQnUlcant disruption or delay'n achieving key ~Bnizational W'ode

objectives

Pulling

It

all Toget .... ,

3.10

With the operational requirement, availability r~nklng, and downtime Impact assessment in hand, a rellabllltv class can be assigned:

I_<tof Awilltblfty A . . IIabMlly .o.voIJoblU." A,",,"""'ity

DownI_

R_1

RBnk2 Ronk3 Rank.

E<nerprio!' W"," Cl8s.s;;Fl CI ... F3 CISS5F4 elll56 1="4 t.lJ1'I~Qion.1 0...F2 a...F3 Clason CI ... F4

RogoanaI C/a5s F1

a ...

F2 ClaosF3 Clossf3

(26)

Sample Reliability Clas8 Ranking C_lcu'-IJon

3.11

We saw eartler that

a

facility

that

could schedule up to 120 hours for

maintenance a yesr while allowing for up to 8 hours of unscheduled downtime

a year

would

have

an availability rank of Z

• If

we

detennine th"t the.impact of downtime for such a facility Is

multi-regional

in scope. affecting a major portJon of business

operations, but not stopping business opera~ons entirEly. then this Ir\dicates ar\ apPr\Opr1ate target reliability c:lass ",nklng for the

fac:lllry of Class F3

Avall.bUIly ... ""'U.y ... ,""'111y ... ilabOilty

ufD_me Rank t R.nI< 2 RoM 3 RonI< 4

Enterprise Wk:le ct •• 1i F3 CI ... Ciao. F4 Ciao. F4

Multi-Rag., ...

,."

.

~. ( CIM_ F3) CI . . . F3 CIaO$ F4

~on.1 Clasa F1 Cia.;. F2 CIa . . F3 Cia. F3

1.oc.1 CI_Fl Class f1 ctU:I F2 CI_F3

Classes & Facility Profiles

3.U

Each dass is assodated with a specific mission -critical facility pnofi:\e defined by:

• Component redundancy

• System redundar\cy • Quality of components

(27)

_.ntGuldo RIok, RwlI.bIKly. & Cia . . Ranking.

The Cla88 F1 Data Center

~I<." ~

~

3.13

A

dass

F

l

data

center

Is

a

basic

data

center where

the

impact of downtime

is

deemed not to be overly critical

• Down~me Im~act

=

minimal

• Component redundancy required- none • System redundancy required; nooe • Quality control = standard

• Survlv:' billty

=

none

• Annual scheduled malnt""ilnCe hours = 200 Or more • Targeted availability; 99.0%

1m

pact of downtime - local

or

Regional

The Class F2 Data Center \ ,..:.,,,,,,,\ " • .-0"'-

\...;,...~")

3.'4

A Class F2 facility has higher ,ssoclated downtime

costs.

It

guards against failure

of

components most likely to fail (such

a.

UPS, controls, generators, etc.)

• Component redundancy;

for

critical components only • Sy.tem red u nda ney = none

• Quality control ; premium for ctitlcal components only

• Survivability ~ moderate hardening

for

sea;rity

and

strueto",' Integrity

b\. ,.

...

' \

• Ann uill scheduled maintenance hours = 50 - 200

• Targeted avail.bility =

99.9%

(28)

SIudontGuido

Class F3

~~".

f

!,>,.\..

(<.,~.,.

' )

3

.

15

Class F3 facilities must provide for reliable, continuous power when

major components are OLlt

of

service

• Component «<Iunclaney ; redundancy is provided for all components not part

of

a redundant system

- System Redundancy ~ system redundancy may be provkled

w~otll. component redundancy I

.f...:

\

,.,.,.

.. \

• Quality Control ;premium quality for all oompone<1ts

- Survivability ~ s~niflcant hardening for security and structural Integrity

(<'"'1'1,'-"')

• Annual maintenance hpur< ~ 5 - 50 • Targeted Availability; 99.99%

• Scope of Imp&et ~ local ti> Enterprise-wide

Class F4

3.16

aaS.

F4 facilities provide the highest levels of redundancy

• Component redundancy ~ redundancy Is provided fer all components

• System redund'mcv ~ redundancy is provided for all systems • Quality control - premium quality for all romponents

• Survlvablltr.y ~ aU building systems are self-supporting and , ) protected against tile highest levels of natural' forces

(~".

,'-

..

?I'''''''

• Annual planned maintenance hours ~ 0

- Targeted availability; 99,999%

• Multi-regional or Enterprise wide

(29)

_".Guldo Rllk. RlU.biltty ... CIas& Rankings

Class Summary

3.17

CI ...

Fl

Class F2 Class F3 class F4

Cgmponent None For Critical For all For all

~.dundancy 'Components ·compo·n,mts IXlmponents

not part or.a

redundant

System

System No No Where For ali

Redundancy ~on'lponent systems

red undancy Is lacking

$unrivll bilily ~.on" Moderate· Slgnlflcilnt Highestl~1

Hardeoil'l9 ·hardening of protectiOn

Quality

Stand.rd

Premium Fo

r

Premium

Prem

fu

m

Control

critical

components

Targeted ··99% 99;9'11, 99.99% 99.999%

Availabilig:

....

.

(30)

8tudAnt Gukle

Seri.1

va.

Parall8~Klnds

Of Redundancy

3.18

It Is Impo.unt to understand that target reli~bility cless typically refer.;

to systems as a whole

• The difference between individual and system reliability

can be

illustrated by considering the difference between two systems will1

equa lIy rei iable components run nlng serially VS. running in parallel

)

-

5Ysc-C-';--.1\1 R~SO%

I

Syst~m 1\2 R~SO%

I

Calculating Rella bilili"

~ystE1fl.n ~Y<"'" Bl

A~ 50'> hlO,.

Paral"'l Sys .. m

3.19 • Serial systems' reliability Is calculated in terms of the produd of the

component systems

• Parallel systems' reli"bility Is Cillculated In terms of the complement of the component systems

Serial System

Reliability Ca leu/alion.

3.20

If lIle two'serial component systems have reliabilities ~.5. then the total system reliability equals:

• R;.,. R;.,

~

.5

*

.5

- .25 ; .2S

I System Al R= 50","",,-.1

I

I Serial System

(31)

Stllllont Guide Rllk. R41loblitty. & Ci8s. Renklng"

Parallel System Reliability

3.21

If

two parallel component systems have rel;abillUes ~ .50, the~ the total sYstem reliability

-1 - [(1- .5) • (1- .5)] ~ I. - (.5'· .5) ; 1 - .25; .75 ~ .75%

Reliability of

the

Pal1ll

vs.

Reliability 01 the Whole

3.22

The foregoing calculations show that it isn't solei

V

the reliability of individual comporients that is crucial to el1Suring a reliable S'/stem

• Rather, the reliability of a system

depend.

upon how its compo!1ents

are

put together

C I a -& the W<lakeat link

3.23

People sometimes spe.1<. of the class rating of a particular sub-system

(such as a Class IV power/electrical system)

• The dass ratings of the Individual sub·systems of the data center can difflor from the class ratings of the system

as

a whole

- The

ove",11

reliability of a system as whole is determined by the

reliability of its ·wellkest link"- its least reliable component

The Lo_.tCommon

Denominator

3.24

A d"ta center may have different class ratings for different portions of tts In frastructure

• For example, a data center mav be rated Class F4 for UPS power, but C"'ss

Fi.

for the mechanical system's power train

- He", tile eJectr~ I S'/stem class rating is equal to tile lowest rating of its components, yielding a aass f2 electrical rating

l

.

n

(32)

Btua.ntGuldl

Reliability & Slngl" Pornls

of

FaUu",

BecauSE a system's reliability Is defined by its weakest link, the presence of s;IIgle poillts of failure

Is

crucia I to class ratings

3.25

Single

points

of

failure

should

be

eliminated

to

Improve reliability

• Eliminating single points of failure means In<:reasin.!! system rt!dundancy

• C,"55 F3 and Class F4 ratings require Ihe elimination of all single points of failure

Risk

and CO$tJBenafit

Analysis

3.26

The last

part

of risk "n"lySiS involv,," an appropriat" weighting of

rosts

and benefits, and communicating this ttl the dlent In terms of a target class

• The following table shows one way of demons_ing the relatWe upfront costs In terms of initial investment and e><ped;ed downtime of a Oass Fl, f2, and F3 data center

Availability Total First Expected

Costs Downtime

99% 10,000,000 B3 Hours of

Downtime

99.9% 15,000,000 BMour

(33)

5tudtnt Gukie Risk. RwlI.I>IIty. " Cia •• ~","ng.

Calcu latlng Annual CoSts of Downtime

3.27

TI>e

prior tabde illustrates the difference between 83 hou~ of expected

downtime for a

Cia,..;

Fl fadllty vs. 8 hours of clowntime for a Class F2 • One way to lIIust",te ttlis

to

a client is to simply multiply

these

hourn

by

the

$47,000

cross-industry average

mr

the cost of

down~me to compute an annual cost of downtime

~Iillbility Total First Expected Estim .. _

Costs Downtime Anl'luul Cost of Downtime aass FI

99%

10,000,000

83 Hours

of

$3.901,000

Downtime Class F2

99.9%

15000000

8 hour

$376000

Class F3

99

.

99%

20000000

1

hour

$47000

Showing Ihe Benefits

of

Highet' I"Hlallnvestmenis

3.28

The prior table demonstrates tnat a Class F2 faCility can save an average client over

l.5

mlilion

dollars

annuiJ/ly Over a Class F1 facility • These ann·ual savings can r>Ow be used to demonstl"llte·the value to

clients of a higher initial expenditure relative to long-term costs of a lower class

Reliability Total First Expected Annual cost :I

yea,

Costa

Downtime

of

dowoilime

savlnlls

over Class

F1

99%

10,000,000

83 Hours of

3,901,000

Nta Downtime 99.9%

15,000,000

8 hour

376

,

000

10, 575.000

99

.99%

20

,

000,000

1 hour

47,000

11,592,000

(34)

S~Guide Riot, RellobiU\)', &

as ••

RanlUng.

Review Questions

1. What are the 3 preliminary detenninations that must

be

made

befol'i! determining a target reliability class?

.

() P

OJ"

tv:

,

.

I

P't'''

N/W

·

--JS

-

Av

/..}(to.'>.(,

·

';;

Rt~""

\'<.

«G-.h

- r."'rd

c

1

<.L

:.

.v',--"

~

.\...£

2. What

are

the targeted availability ranges asso<:lated with each of

the 4 class ran kings?

S"

c:::c

_S uP,.)

>"

_

$"0<>

'S"

..

' ) 0

c

.

.,

_'5

.

0

<,"r

to

"''<.

"I

't ".

"r I" '"

"<.

'l."

"

'i.

~1"

f'

-"'i,«

'i

<"I

'( 'I

.

"l"

"i

~'-' <"("(,

"I

'i

f '/

J.

If

their comllOnents were equally "'liab .... wouk! " ... ri,,1 or parallel

sy.tem be more reliable?

(35)
(36)

SCudlnt Guide Locadon

Module

4: Location

Module Goals

4.1

This module examines factor'S relE!llant

to

choosin9 a stJ~able location for a dat.'> center; after completing the module you should be able to:

• Advise clients regarding data center site suitability

• Identify best pr~ctices reganding power and telecom

acce;;

feeds • DlstUss the recommendations regandlng app<opriate

d<lta

center

(37)

stud.nt Guido

Clreul! "

utility

F •• de

4.7011

The ta,.get reliabilitY' class will determine the type of utility feed reoommended for a data center

• 5i "!lIe FMd

from

51 ngle utility $11 .... Statlon - the least desirable method for power delivery to a site, suitable only for Class F1

'--

iL .

~

~

:;-

LI_ ...

__

--II

'"<~- LI_'_~I_~_"'---,

• Redundant

Fee""

fro ...

Dillerse Prollld .... -the preferred

method for power delivery

to

a Class F2 or F3 facility

• R .. dund.nt!Pive ... F...,ds from Diverse Utility Sclb-StatlDns - preferred method for power delivery to a Site, 5 LJita ble for Classes F3 and F4

1

_ _

I~O?i

_oo_oJ

~&'1

o

.•

~

I

.-~.:.':""- ~ '2utntlltloro·2 ~

• Redundant Faeds

from

Dillerse Providers-the preferred method for _ delivery to a Oass F4 facility

(38)

student Guide

4.9

All electrical service et1tri1nce feeds should

be

underground

wiltl •

minimum separation

of

4 ft

(l

'

.

2m) from

other utilities along the

entire

route

• If ovemead utility lines

to

the site cllnnot be avoided, provKle multiple power source paths

o Separate electrical servi<:e entrances snoJ,Jld have a minimum

separation of 55

It

(20m) from One a/'lother

(39)

_ G u i d e Loclllon

Location and Telecom

Acce&$

The primary concem regarding location and telecom access is

redundancy in terms of both access reeds and service providers

4.10

• Data centers should

be

located in an area· w~h easily sustainable

connectivity provided by two or more access provider central offices

- Diverse service feeds

Me

recommended to have

a

minimum

separation distance of

20

m

(66 ttl

along the entire route

IWfIolmurn 06 fl/20 rn)

location and Telecom Access Types

Telecom access feed recommendations are determined by target

reliability dass rankings

Class F1 acee •• recommendations:

• One service feed from one access provider cenlral office

Class F1 Access Provider Layout

4.11

Long Dj,tance

...

..

Access

Providers

A

Data Cente,

,

.

..

Central Office

..

Central Office r

...

(40)

cr_

F2

Acceu R&comrnendatlons

4.12

Oass F2-Mooerate Redundancy:

• Diverse servke reeds r,om one centra I office

• ead!

service

teed

using separate and diverse

paths

I

Long Distance

~:_=:::::~

Centlal Office

~::==:>~

Data center

Redundant Telecom Access 4.13

Red unda nt Oass F3 recommendations:

• At least one service feed from two separate and d istirICI: ao:ess

provider central offices

o Ead1 access provider central offICe conn..cted to .. me long-distance

carrier

• Each

service reed to the site using separate a nd diverse

paths

Centra! Offlc" ~ 1

long Dirtance Data Cenr~r

(41)

~d."Gc.oldo

The site should be at least 1 mile (1.6 km) away from: • Gas stations

• Auto body or paint shops

• Self-storage fa~ifities "" ...

,.;,_

:>

.,.,:

'.J~ - High voltage power d!stribatillri lines

• Public utility SoJ bstatlons

• Water storage towe",

• Commercia I nlilways

• Highways and other major traffic arteries • Coasta I or Inla

nd

waterways

The data center shouk! be at least 100 yards (91 m) away from:

• 100-year flood ha2ard areas NMghbors

You

Do Want

The data center should be within at least 5 miles (8 km) of:

... A police 5wtion

• Afire department station

The data center should be at wttl1ln at least 10 miles (16 km) of;

• A hospftal \) ...

,,'£

~ tt~\·,

h-\..

;

:'"

\

L

IN'~

• A major metropolitan area

<'"

,1"'Lt..<- u\. .. /.,....,..,

"

Q

~ .

C0l1111 aal'

(42)

_ .. Ould. LoeoIIon

Wind

4,26

An area wiltl less than 2% annual probability of Wind over 80 mph Is preferred

• If

the site

Is

in

an area

with 8 higher probability than

this,

specific detail in

the

"hardening" of

ltIe

building must be incorporated Into

the design

-_

...

...

M.p tiho'J¥t". fo,n.do RI.k Ar._ In TM C'ontl!rminoue Unni!'d.Statea

,..., Showlna HIII"I1eaI'l~.ktlyit~

In Tile. ~irlD1D u ... ~ S1MH

-

.

,

.

,

'

(43)

Sludont Guido Lotallon

Air QualHv 4.27

In arws

witll

exisMg air quality problems, regulations re!1ardi09

nit,ogen dioxide

(NO,)

emissions (produced

by

backup and eme'!}ency generators) need to

be

consulted

• Er.osure that generator nun-time permit requests are issued in a

!Imely manner to federal and state environmental authorities

• In most

cases,

annual operation hours will be

restricted and

compli~nce must be vertfied

(44)

Stu.,.,.

Guido L.o<:alion

Review Questions

1. What type of power utllity feed Js preferred for a Class' F4 data eenter7

R~'<~.f

Ft.

.)

",

+',<

.

~

D;.

·

t/"s,

Pre,

.

,'.!

t··

'>

2. What type of telecom "ccess

feed

is preferred for a Class F2 facility?

p

oJ..'~'''''

(

P.:..t:(<j

{no",,"

I'I'v".--$,-

fro, .

.tv;.

3. How f~r away should a data center

be

from the nearest Jake~

<]

,

....

.:( (

'7

021)11) BleSi"

•. t6

(45)
(46)

Buildings

Module 5: Building Considerations

Module Goal.

5.1

In tl1ls module we wllJ look at what makes a building a good candidate

for housing a data center; after comjJ!eting this module, you should be able to:

• Identify the tvpical support spaces of a da\ .. center • Ie/entity the "",h;tectural parameters for a data center

• Give recommendations regarding a bUilding's suitability for a data

(47)

Bulldlngo

Structural In9reGlenl& of Data Cent ...

5.2

A data center

Is

typically composed of iI computer room for housing mission cr1tleal data storage and application hardware, as well as a

collection of specific support spaces that typically include,

Telecom/Entrance Room

• Electrical Room

Storage/Receiving Room

• Control Room

SUlff Su pport Space

• Entry POint/lobby

• Battery Reom

Print

Room

• Mechanical/Chiller Room

Building SIIeII Considerations

5.3

Data Centers should

be

installed in a steel Or concret~ framed building • Building e~!eriors should

be

made of noo·flammable durable

material

• Building sections shall allow for a minimum r.ais~ floor

to

ceiling

height of 10

It

(3.1 m)

• The slab to structure above should

be

a minimum of 14.5 It (4.5 m)

19 ft

(3.. t "I)

!Hod

Ibor

Ie

CI!iriG

:1

I

...

145 ~(4.Sm)

slab

\0

floor

above

(48)

student Quk:le llulldlnll"

Data Centet Floor Lev ....

The ground noor is

often

t

he

most advant.l9eou~ for data center

placement due

to

equipment access and Hoot loading considerations

• Frequent changes In

IT

and Oata Center equipment are common

• The average IT sel'ller has a life span of approximately 3 years

• The average data (:(!nter will eIlange out its entire equipment

inventory over the cou~ of

3·5

years

Data Canters·

Equipment

Aceen

5.5

The data center should be d",lgned

to

ensure ease of eq uipment

delivery and removal

• The delivery paltlway shall allow for equipment 35 la .... e as 10

It

(3

m) long, 39 in (t m) deep, 6.75 It (2.1 m) wide, and weighing as

much as 7500 pounds (3400

kg)

Upper Floor Data Cen ...

5.6

Although less convenient for equipment acress, upper floor data center

placement can provide added security against unauthorized Intrusion

and wMer damage

, In areas subject to major lateral force issues (.uell .. s hurricane,

Wind, earthquakes, etc.) M upper floor will contribute

to

structural

illliecw:itv • , . I j

1 ... ) \lliJ

;'

'';

6

'

Dete Canter Neighbors

5

.

7

If a data center is in .. multi-tenant bUilding, ,"""ices

to

the data

center should be separate f,om ollle, tenants

• All wate, lines, sprinkler lines, duc\Werle, gas lines,

etc

.

serving

areas outside of the data C<!nter .hall nO! pass ltlough the data

Genter area

• ~o haUlrdQu$ systems shall be located in or a,ound the data

(49)

Walls

Bulldln9>

5.8

The data center'S perimeter walls s~all be full height (slab to deck

above), l·~our rated construction, fire sealed, and sealed

ro

prevent

chemical fire suppnesslon leaks

• Interior walls sholl be constructed of a minimum 22 gauge (0.65 mm) metal studs lor walls up

ro

11 feet (3.5 meters), 8 gauge (1 mm) lor walls exceeding 11 feet (3.5 meters)

• Studs 5h,,11 be " minimum 01 5.5 In (140 mm) depth to

oo:ommodate boxes and piping requited to be Installed In the wall • Walls shall be sheathed 10 ftre rated wall board such as .6 in<h (16

mm) type ")to 9)IPSum board

• Non·,ated walls should be braced no more than every ten feet (3 meters)

• Gypsum boa rd for non-rated wall Is to be .6 inch (16 mm) type "X"

Fire Rating

of Data

c.n .... ' Spaces

5.9

• Perimete" • Computer Room: • Control

Room,

Printer Room:

Media Stora~e: • Electrica I Room:

Enlrilnce Room: • Battery Room:

Receiving Room:

I-hour rating, full rn.;ght, slab to slab

No rctting4 (1001"" to c.elling I between

equip"",nt I-hour to non-computer mom spaces

No ",tlng between

computer room;

1-hou, rating to non-computer room spaces No rating between computet and control rooms; l·hour rating to other support spaces

2-hour, lull

height

1-hour,

full

"ei9ht

No ratlng between computer room;

I

-

hour

to

other

support spaces

I-hour,

lull height

No rating hetwe.en ~ompute, and control room; t-hour between other support spaces

(50)

lluldlngs

Wan

finishing

computer room

and

related walls should be finished with a non-p"rticulating smooth water-based epoxy paint

• Prior to painting, gypsum board is to be sealed with primer

$,10

• All penetrations In the perimeter wa lis a re to be completely sealed

The data center should be motsture/v" POT sealed around the perimeter, floors, and ceiling.

5.11

• If

data center

Is a

'ground

up' building,

slab

and all below grade components should be continuously sealed with

a

rubberi.ed mojsture barrier

Floora

-

All

exterior opening/penetrations are to be sealed prior to wori< on intenor walls In the data center

5.12 A

data cent..,-

Hoor shall be a minimum slab of 5,5 inches (14

em)

thick

• The Hoor slab shall be designed for" minimum of 150 Ibs/It' (7.2 kPA)

- for data centers with hiqh-denslty racks, floor slab is to be a minimum of 8 inches (20 em)

- Centers with high-density racks shall have" slab designed for

2.50 IbS/ft' (12 kPA)

...

(51)

Studlnt Guldo Bulldln!!"

Access

FIooI"8

5.13·14

A raised access floor system should

be

considered for all electro~lc

processing eq uipmen! ~re.s, telecom areas, control rooms, and other spaces that requ i re precise temperature and humlditv control

• Raised floors require higher initial investment,;, but often alloW tor more

economical long tenm cooling

solutions

• The access floor shall be a minimum of 18 in (.46 m) above.s1ab • For da ta centers with high density racks, the acce-ss

noor

shall be

24 in (.6 m) above the slab

Access

Floo",

5.15

The raised floor system shall be a eontinuous bolte~ smnger system to tra nsfer latera I load

• Raised floor system shall allow for static transfer to the grounding system

atl10SICSi"

54

(52)

Bulldl"ll'

Ceiling_

5.16

Doors

Ceilings shall be composed of a 2

It

(600 mm) x 4 II: (1.2 m) lay-in grid with a clean room vinyl faced gypsum lay-in tile Il:l prevent

contamination

t-~,~

...

1"01(,.' ....

t.t '-.

• The lay-in tiles shall be smoolh, non-particulating, faced tHe, with sufficient weig ht to prevent the IIrt-under pressure of a gas fire suppresSion agent

• The T-bar shall have neoprene seal

• All penetrations In the ceiling shall

be

sealed

• Ceiling systems shall be suspended

with

an independent 4-wav win n9 system

5.17

The primary entrance door to the data center shall minimally be it P<lir of

3

ft

(0

.

9

m) wide by

7 It

(2.1 m) high doors

• The primary entrance doors sh""ld have no center post a nd no doorsills

• Data ~nter doors shall be solid core, minimum 1

3/4

in (4.5 em) thick, either wood or steel, mounted in steel frames

• The rest of the data center doors should be a minimum of 3.67 It

(1.1 m) wide by 7

it

(2.1 m) high for it single door, or 6

It

(1.8 m) wide by 7 ft.(2.1 m) high for it pair

Data Cenier Floor Planning

S.18

The in itia I layout of a data center site, the computer room

+

support places, should ideally allow for future computer room expan;lon. Avoid placing the computer room next to:

• Outside wa lis • Elevator shal\s

(53)

8Ndent Guide elllidings

The Computer Room

va.

Support Spaces

5

.

19

Data centers should

be

designed with a "li9hts out" approach that

attempts

to minimize

needed access to the

computer

room

• ll1~ design and layout of personnel and support. sp~ce sIlould be such that minimal acress to the computer is needed .

,

\~",,<

<1111\

.

rPTI"~1bo1"'l

!

-

- -

- -

-

-

-

I r .. ~"""

fbtlfOry E~'rll,,1 UI'trJl~

i

I

I I .1I00'''l''I'',

""""'

RoI~n R""m

I

~lnrN~1" AI~ .. l\rIeIWrJIh " " , _' I - -

-

- -

-

-

-

I

...

~,

rt:.i'{~I~;u1"·IC.'O"1

(~'r1lm1

,-

- - - -

-

-

-

.

-

-

-

1\>,,"

I

I HI'ltllllH!..rt~ • ~o(>t u(!r 1iI~'" H:)vo'1

I

T.d,,1"

I - - - -

-

-

- -

-

-

J M<dI, Stor.lgt

ft¥<~rvi"') J !oI!(Vn! ~on!~r

Stt.lta91

'5oi*-l, Uri-! thl.dIAg ~d ... ltlt. 1

I

'elecorn

I

If ~:IOfIonel Sp.ll~

W"'"

(54)

Student O4.Ikte Bolldl"1I"

M~in Entry Point

5.20

The entry to the da~ center should be pOsitioned awe

y

from the entry point of lt1e building

• Entry

to

the da~ center from non-data center spaces should lead

into

a

controlled space, prior to providing access til the equipment

areaS

• Entry tor equipment should be controlled by the data cent@r

p~nelonly

• Equipment entry sIlould be located

near a

staging/storage

area for

preparation of equipment prior to entry Into comput@r

room

d.>J. "' "'"

r""-i<:,.

i

~

,( '"

L, ('.,

f

C/

Control

Room

5.21

A control

room

monllOrs the functioning

of

the computer

room

electronically

as

well

as

typically being troe center of building

monitoring and automaMn systems

• It should be near the main entrance

• A console

is

rernmnlen<ted

to

house

all mon

itors

• It should provide direct access to the computer room

Telecom Entrance Room 5.22-23

A data center should pos5eSS

a

telecom entra nee room - either

adjacent to or within" secu red section of the compute r room -

to

house access provider demCtrcatignl tennina~on, ~nd provisioning equipment

• The design should accommodate

a

minimum of

two

cabinets for each canier

• A

minimum of OIl<' owner-supplied patching rack should be supplied

for every

10

carrier

racks

The ent",nce room shoukl be positioned with orcuit distance limitations In mind and should be

ild

j

acert

to the computer room

• The entrance room should allow for sepa ration between customer

-owned

and

access-<WIned provider equipment

• Customer-owned equipment should be secured against

access-prcvider technici.

n

s

(55)

S1udonl Ouill.

Electrielll Room 5.24

A data center should have

a

dedicated electrical equipment

room

for

housing switchgear, the uninterruptlbUl power systems, distributiofl panels, and sometimes generators and power distribution units

• Two

eKits

are required

for

the electlical room

• If there are two electrical service entronces

I

pathways into tile data

center,

then

there should be two dedicated eleetrical rooms/spaces

Generators

&

Fuel

Storage

5.25

Indoor

backup generarors

are' recommended

" Indoor generators provide ease

of

access and a re more secure

• Indoor generators

"Iso

require

spedal

ventilation

- Regardless

of

whetlJer indoor

or

outdoor, ol'\S~e

generater

fuel storage space must be planned

- Ttoe amOll nt of space set aside for fuel storage should be erlough

for

between 2 and 7 days worth of fuel

Battery Room 5.28

A battery room should be adjacent to the electrical room. The size

will

depend on the type and number of batteries required

• The batte ry reom may also need to Include the Installation of disconnect switches

• The battery room

will

require two exits

• Battery rooms shall include halardous containment, either a contain ment system or hazardous mats

Check with AHJ regartling local cocle and dedicated exh8ust systems

....

(56)

Student Gulet. Bulldl",,"

MechanicaliChiller Rootn

5.27

Space needs to be provided outside of the computer mom for cooling system equipment such

as pumps,

fuel tanks, chiller

tanks,

and associated controls

• Tl1e data center deSigner ~s to coordinate with the mechanical systems .deslgner to determine the equipment spadng needs

Media Storage Room

5.28

Data centers that produce In·house storage media (such as backup storage tapes) shall provide

a

separ1!Jte room for media storage prior to its transfer to

a

permanent stol'llge facility

• The media storage room should have a 2-hour fire rollting

Print Room 5.29

Printers should be located In

a

dedicated print

room

separate from the

computer room

• The print mom should have its own dedicated air handling sy<tem • A separate puper storage area near the print mom should be

provided

]4.'''f

Fr .

....

t-.

-,

-\;-

,.1i" ....

/

.•

r.,.

''"''

/<>

.

..

,~;

M

,

-~-{

Fire Control Room

(,

·

~

~~,...

..

,..,-

h""

.

~4

LIZ

.

5.30

For the highest tier data centers, a separate room should be provided for the pre-action control valve system

• Space should be providecl for the placement of chemical lire su ppression tanks

• Tanks need to be Iocsted to assist easy serviceability

• Tanks should not be lo~ated In the ceiling area above equipment • Tl1e preaetlon sprinkler system is similar to the wet sprinkler

system eXCEpt the piping In mliral areas does not contain water untH there is a fire

• Tl1erefore, this system provlcles protection against waler damage to the data processing equipment due to an accidental di.chatge

"11

(57)

lkudontGulclo Buildings

Receilling

and

SIont\l8

Room

5.31

Aniving equipment should be stored, uncrated and prepared In a I"Oom away

from

the

computer room,

with

filtnnion

on the ne!IJm air le3vlng the room

• The storage room should be adjacent to the equipme<>t entrance of

the dIlta ce<lter

• The storage room can he a component of the s~lng room, or a separate reom near ltIe staging area

o The staging area should be monitored by CCTV

• A sep<lrate

secured

storage room shOUld be considered for high -value equipment and for vendors' equipment

Sacum loading Dock

5.32

A secure loading dock should be provided for the delivery of high value equipment

• Tne secure loading dod< should protect equipment from .evere

weather

• The secure loading dock should be

mon

i

tored

by CCTV

"11

(58)

Review Questions

1. Why is

the

ground

n()()r considered

advantageous for a data center?

k

~c...;

;I'"'t~{

A<.

(.,;'j.»

-€-r-

(w'

(c

,-

,A

k.- ,

. .... / f '

./

2. What 3 things shOllld one avoid placing the computer room ne~t to?

V

'"

~<,

i

.f

(

"'-~

(r.,

f

1,.,,,1<,

s"~f{?

u

.

J ....

J

(;I',J

1:;4,;ld·'~1

fA.

'1/

I ')

L' fl'-t-r

I,...r ....

~- J

3. What minimum number of days worth of generator fuel should be on

(59)
(60)

Studonl Guido Tho Comp,*' Room

Module 6: The

Computer Room

Module Goal,

6.1

In this module we will examine the crucial elements of ~ data center computer room; afte!" completing this module you should be able to:

• Identlfv the components of st~ndanl computer room cabling topologies

• Explain the hot/cold aisle oonrept of computer room eQuipment layout

• Describe the basic .paCing recommendations regarding standanl computer room layout

References

Related documents

• A non-parametric statistical hypothesis test used when comparing two related samples (paired). • The test is named for Frank Wilcoxon (1892–1965) who, in a single paper,

Lab experiments and field monitoring were designed to test the effects of inflow NOx concentration, pH, residence time, and reactor media on reduction of NOx

Each data center should maintain a UPS to protect against power outages in short durations, provide clean consistent power to the data center infrastructure, and provide enough

An up-flow CRAC unit delivering cold air to the room such that it is mixing with the heat being generated by the load is a typical data center example.. Row cooling is the

Design, provision, maintain and provide technical support for customer Data Center Planning and Operations services, including, but not limited to data center services, data

• What tests are required and recommended for channels and links per the ANSI/BICSI 002-2011 and other standards; End Face Inspection, Optical Loss Testing, Polarity

This analysis is based on four main categories of information collected at individual firm level: investment in intangibles and innovation activities; introduction of

171 tons (N+1) cooling data center 675kW (IT loads) data center 9 tons (N) cooling electrical room 11 tons (N+1) cooling cross-connect room 40kW (IT Loads) cross-connect room