This basic foundation is often taken for granted and not sufficiently reviewed. As a result, IT may be forced to deal with excessive amounts of equipment failure, corrupted data and overall service-level issues. This topic will be covered in two articles. This first one will focus on some basic project elements that are needed; the second will cover issues for consideration.
As with any project, a basic plan is needed. This helps facilitate improved communications and better results. Within the basic project plan, the following task categories and suggestions are given for review:
Don’t forget that other groups in your organization may be very familiar with power issues and be great resources to utilize. This includes groups such as facilities maintenance, manufacturing operations, manufacturing engineering, and so on. All parties who can significantly contribute to the solution or be impacted by the result should be considered a stakeholder.
Talk With The Utility
A good starting point is to contact your local power company and have a meeting with your customer representative. Topics to discuss include past outages, typical time to repair, highest risks and what their service levels are.
Ask for a map of the power grid in your area to understand what heavy users are on your segment. Point blank, ask the representative what risks you should prepare for. What are the longest outages on average? What other issues are common in the area in terms of spikes, sags, harmonics, etc. Then, ask how the power company can help. There are things they will do for free and others for a fee.
Either through the power company, or a consultant, install a power line monitor to collect data about spikes, sags, harmonics and so on. The duration of the survey should be based on a combination of what the IT team suspects and external recommendations. If a foundry is next door and they turn the furnaces on at 6 a.m. and off at 6 p.m., then be sure to monitor the lines during those times. This is predicated on you understanding the power grid you are on and who you share the line with.
Talk to IT, manufacturing, management and other organizations in your area to understand what they have experienced and avenues they have taken to deal with risks associated with the power. Move beyond IT to better leverage the experiences of others both in terms of the state of power quality as well as potential solutions that they employed.
Analyze the Results
Take the results of the utility meeting, site survey and interviews and review them with the IT team to understand threats and see what possible compensating solutions the team can come up with. Having good representation from people who understand issues surrounding power quality can be very beneficial. Objective third-party consultants can be very helpful in terms of the unbiased recommendations that they can offer.
Develop a List of Requirements
The next step is to generate a list of requirements for power to the data center. This is shaped, in part, by service level commitments, power consumption, planned expansion, sensitivity of the electronics to power quality, etc. Armed with a list of requirements, it is time to open talks with vendors.
Part of the interview process should be a discussion of vendors that other groups have used. This should be coupled with internal experience and a review of solutions in the industry trade magazines and websites.
Aim to get at least three vendors involved and be sure to research them. The old saying of “trust but verify” must always echo in your thoughts. Require formal written proposals so the solutions can be compared, questions assembled and vendors held accountable. If a legal issue ever arises, you’ll want everything in writing to prove what was said and done.
Additional Vendor Selection Criteria
In addition to internally developed criteria, consider including the following elements as well:
For big systems, resist the temptation to do internal maintenance. These systems can be very complex and the better left to trained technicians. Similarly, if they are maintained in-house, the liability related to failure is fully absorbed by the organization.
Take the requirements list and establish a weighting for each point. Those items that are most important get a weight of five and then go down the scale to least important which get a one. Then score each vendor with a one for a low score to a five for a high score. As a result, the vendor with the highest score should be the best, the next best vendor will have the second highest score and so on. This allows for fairly objective ranking of the vendors on the basis of merit. Stakeholders should weigh in on each and an average for each score developed.
IT systems can’t run without power and their reliability and availability are directly linked with the quality of the power supplied. Power can’t be taken for granted and if it hasn’t been reviewed, now is an ideal time to start such a project. In the next part of our article, we will review topics for consideration.