WP_195 Fundamentals of Managing the DC Life Cycle for Owners-140902130318-Phpapp01

8/10/2019 WP_195 Fundamentals of Managing the DC Life Cycle for Owners-140902130318-Phpapp01

1/27

Fundamentals of Managing theData Center Life Cycle for

OwnersSchneider Electric

Data Center Science Center

Schneider Electric Data Center Science Center WP 195 Presentation February 2014

White Paper 195


2/27

Just as good genes do not guarantee health and well-being, agood design alone does not ensure a data center is well-built andwill remain efficient and available over the course of its life span.For each phase of the data centers life cycle, proper care and


action must be taken to continuously meet the business needs ofthe facility. This presentation describes the five phases of thedata center life cycle, identifies key tasks and pitfalls, and offerspractical advice to facility owners and management.


3/27

Introduction Understanding the Big

Picture

The Five Phases of theData Center Life Cycle



4/27

Plan Phase

Ideal project process

Often referred to as programming

Determines key project parameters of thephysical system to be created, i.e., systemconcept, site selection, and project process


ys em concep Players at this stage

Facilities and IT departments

Executives

CFO

Real estate group within the company

NOTE: In this paper, only system planning is covered. System planning refers to the power, cooling, racks,

and other support infrastructure systems. Planning related to the IT equipment is not discussed here.


5/27

Plan PhaseIdeal project process

Conduct project efficiently, reliably, andunderstandably

Have safeguards to eliminate missed handoffs, ambiguousresponsibility, and lost information


White Paper 140, Data Center Projects: Standardized Process, offers a detailed

definition and description of a formal, standardized, and documented process.

Detail key stakeholders, responsibilities Include strategies to manage unplanned occurrences, i.e., project

changes and defects

Be modular and configurable, adaptable to projects of different types

and sizes


6/27

Plan PhaseSystem concept

A high level description of thesystem

Includes validated user preferencesand constraints, standards, codes,


See white paper 142, Data Center Projects; System Planning, for moreinformation.

resource assignments, deadlines,and process requirements forproject

These design requirements become

input for design phase


7/27

Establish

PROJECT PARAMETERS

Develop

SYSTEM CONCEPT

1

2

Make the six foundational decisions that willcontrol the system architecture and budget

Choose a model design for the system,based on the six PROJECT PARAMETERS

Plan Phase

System Planning SequenceSystem concept


Incorporate

USER PREFERENCESAND CONSTRAINTS

Determine

IMPLEMENTATIONREQUIREMENTS

3

4

Identify, validate, and adapt user-specific details that will refine theSYSTEM CONCEPT

Collect standards, codes,deadlines, resource assignments,

and process requirements theproject must conform to

Criticality Capacity Growth plan Efficiency Density Budget

Referencedesign

Roomchoice

ConceptAdaptations

ValidatedPreferences

ValidatedConstraints

Implementationrequirements

The combined outputsare the design

requirements for inputto the DESIGN phase


8/27

Plan Phase

System concept

Ri ht information > ri ht decision

Avoid Problems inProject Process


maker > right sequence Focus on shared understanding and

consensus: criticality, capacity,growth plan, efficiency, density, and

budget Avoid detailed design work until

design requirements are validatedand agreed upon


9/27

Plan Phase

System concept Reference Designs

Validated, documented hi h-level lan for


See white paper 147, Advantages of Using a Reference Design for moreinformation.

physical infrastructure Especially important in the absence of

design engineers in early planning phase


10/27

Plan Phase

Site selection

Site must meet design requirements Site evaluation must consider availability risks

and financial benefits


See white paper 81, Site Selection for Mission Critical Facilities, for more

information.

Energy costs

Tax preferences/incentives

Labor costs


11/27

Design Phase

Involves detailed design work required totranslate Plan phase outputs into site-specific schematics and buildable

construction documents, i.e., drawings andspecifications


Approved documents used for permittingby governmental authorities-having-jurisdiction - AHJs

Construction contractors evaluated,selected

Well-managed design/build model takesabout 4-6 weeks

Well-managed design/bid/build modeltakes about 8-10 weeks


12/27

Key Tasks:Project management, meet budget, feasibility studies, preliminary

Architect & CE Firm

Owners Design Requirements from

Plan Phase (see Figure 2)

OR Design/Build Firm

Owner evaluates,hires, and entersinto contractwith

Design Phase

Typical high-level overview


, , ,contractor and/or sub-contractors for build & commissioning phases

General Contractor

Likely parties involved indetailed design:

Owner/Owners RepArchitectMEP engineers

Structural, civil engineersIT consultantsEnergy/LEED consultantsCommissioning agentFacility Operators

Schematicdesign (10%complete)

Design

development(50% complete)

Constructiondocuments(100% complete)

Detailed design outputs (approved by owner):

Electrical Contractor

Mechanical Contractor Low Voltage Contractor

Cycles of design iterationtypically take place asrequirements, preferences,and constraints change.

If construction delivery

model is design/bid/build,bidding by contractorsoftentakes place at each of thedesign documentationlevels (10%, 50%, 100%are common)

hired by architect or design/buildfirm

Networking Contractor


13/27

Design Phase

Design/bid/buildTraditional approach. Contractors bid during designdevelopment. Lowest priced responsible bidder meeting

requirements is selected Construction begins.

Construction delivery models


PROs:

Possibly lower cost if design changeorders are well-controlled

Typically presented with more choicesfrom more vendors for a given design

CONs:

Bid process can add monthsto project schedule


14/27

Design Phase

Design/buildOwner or architect hires team responsible for both designand construction. Selection based on merits and price.

Price is guaranteed. Change orders typically not allowed by

Construction delivery models


.

PROs:

Shortens schedule by months.Eliminates time needed for biddingprocess. Construction starts in parallel

with design documentation development

Owner more likely to get exactly what is specified

Enables early contractor involvement in design, possibly reducing risk andnumber of design iterations

Fosters close cooperation between designers and contractors

CONs:

Likely not the lowest cost


15/27

Design Phase

Important tool for ensuringright people > right time > right focus

Defines key stakeholders roles, responsibilities byphase

Owners contract


Defines compensation and insurance requirements Describes

Cost of work

Change resolution methods

Change order process, limitations Termination grounds and processes


16/27

Build Phase

Information gathered and approved duringPlan and Design phases is used as a basisfor Build phase.


To bid for contractors

To secure building permits

As basis for what is actually built at the chosensite

Construction begins according to project plan Perform regular audits, quality assurance

Weekly progress meetings

Opportunity to train owner and facility

operations team


17/27

Build Phase

Complete when

Quality assurance confirmswork is complete to projectrequirements

Final certification of


completion is issued to ownerby construction team lead

Passing score oncommissioning test, if part ofproject

Owner issues letter of formalacceptance of project


18/27

Build Phase

Commissioning

Defined as a reliability science thatdocuments and validates the result of a datacenters design and build processes

Addresses Data Center complexity by testing and documenting overall


systems response to real world inputs and changes Ensures design and implementation in construction phase are sound

Commissioning agents developcommissioning plan and schedule

Work with design andconstruction teams


19/27

Build Phase

Commissioning

As built script report

Output Documents


Provides line-by-line report on whatpassed/failed

Component error log report

Describes what failed and what wasimpacted

Trending report

Executive summary of performance

trends


20/27

Operate Phase

A properly designed,

Time during which physical infrastructuredoes what it was intended to do: house,power, cool, and secure IT servers, storage,and networking gear.


mp emen e , an suppor e

O&M program will

minimize risk

reduce costs

provide competitive

advantage for the overallbusiness the data centerserves


21/27

Operate Phase

Focuses on risk mitigation

Grasps interconnectedness of facilityand IT systems

Mission Critical Mindset


, -

risk avoidance and problem solving

Commitment to continuous learning andprocess improvement

Owners & management mustimbue the Ops team with this

philosophy and mindset


22/27

Operate Phase

Environmental health and safety

Personnel management

Emergency preparedness and response

12 Essential Elements ofData Center O&M Program


Change management Documentation management

See white paper 196, Essential Elements of Data Center Facility Operations, formore information.

ranng

Infrastructure management

Quality management

Energy management

Financial management

Performance monitoring and review


23/27

Operate Phase

Facilities-IT cooperation

Cooperation will


Make capacity planning more accurateand day-to-day operations more

efficient

Minimize impact to SLAs and thebusiness when problems occur

Reduce disruption caused by facility orIT equipment moves, adds, changes

It is the responsibility of owners and management tofoster this cooperation!


24/27

Assess Phase

Yields useful, actionable information including

Concurrent with Operate phase, givesvisibility to how operators and physicalinfrastructure systems are performing onan on-going basis.


egree to w c t e es gn ntent an ac ty o ect ves are e ng

met by current infrastructure in operation

Energy efficiency of physical infrastructure in supporting IT

General health and current risk profile of physical infrastructure

Current power, cooling, and space capacities and use trends

Effectiveness and experience levels of personnel Facility operations & maintenance program maturity and

effectiveness


25/27

Outsourcing Services

Benefit from experience andexpertise of others

Advantages


on other key tasks andresponsibilities

Avoids learning curve and mistakesresulting from first time tasks

Provides alternative to internalresources that lackbandwidth/resources required tolearn new skills or perform certainfunctions


26/27

Conclusion

Provided owners, managementteams with basic understanding

of mission critical facility projectsand operations in the context of aData Center Life Cycle

Described phases, their


n erconnec on, pr nc pa

players, key areas of focus


27/27

Resources

Data Center Projects: Standardized ProcessWhite Paper 140

Data Center Projects: System PlanningWhite Paper 142

Data Center Projects: Advantages of Using a Data Center Reference Design

White Paper 147

The Top 9 Mistakes in Data Center PlanningWhite Paper 145

Site Selection For Mission Critical Facilities


Browse all APC white paperswhitepapers.apc.com

Browse all APC TradeOff Toolstools.apc.com

Data Center Projects: CommissioningWhite Paper 148

Ten Errors to Avoid When Commissioning a Data CenterWhite Paper 149

Essential Elements of Data Center Facility Operations

White Paper 196Avoiding Common Pitfalls of Evaluating and Implementing DCIM SolutionsWhite Paper 170

WP_195 Fundamentals of Managing the DC Life Cycle for Owners-140902130318-Phpapp01

Documents

Transcript of WP_195 Fundamentals of Managing the DC Life Cycle for Owners-140902130318-Phpapp01