FACILITIES DCIM
#dcsarticle
http://dcseurope.info/n/dycb
Avoiding common pitfalls when evaluating and implementing DCIM While many who invest in Data Center Infrastructure Management (DCIM) software
benefit greatly, some do not. Patrick Donovan, Senior Research Analyst with Schneider Electric’s Data Center Science Center, has identified some common pitfalls that should be avoided when evaluating and implementing DCIM solutions.
T
he problem, of course, is that not all solutions are effective (or appropriate) and they can be poorly implemented and maintained. Although they may understand the necessity and value of DCIM, some customers fail to obtain much value or benefit. Research has determined there are three common pitfalls that users can fall into when evaluating and implementing DCIM tools. These traps interfere with or limit the effective functioning of DCIM tools. Choosing an inappropriate solution; relying on inadequate or mismatched processes: and a lack of commitment, ownership or knowledge can each undermine the ability of a chosen DCIM toolset to deliver the value and benefits for it was designed.
Pitfall 1: Choosing an inappropriate DCIM solution At the time of this writing, there is a large and growing number of DCIM vendors and solutions. Some of the available tools are focused on specific measurement functions, or are slanted towards managing specific power or cooling devices, while others may provide a broader capability, such as workflow management or energy management, over the whole data centre. Some may allow remote control, while other tools only collect and report data. Functions are provided at
34
www.dcseurope.info I June 2012
different levels of depth across different products, and there is often overlap or gaps when assembling disparate DCIM tools into a suite.
As data centres become increasingly standardized and modular, the need to assemble a DCIM solution suite will be reduced. Some functions will become implemented as firmware within data centre modules, and other DCIM functions, e.g., analytics, may become available via cloud services. It is important to recognise this trend now and ensure that the kinds of solutions implemented today will seamlessly carry over into next-generation data centres, without dramatically changing operating practices and processes.
Although the exact methods and standards used in future data centres are not yet determined, it is possible to identify a number of key characteristics that tools selected today must have, in order to be prepared for the future and be effective today: £ Scalable, modular, flexible system £ Open communication architecture £ Standardized, pre-engineered design £ Active vendor support structure
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56