Deliver Us from Evals: Evaluating Storage Software

Enterprise Storage Forum content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More.

Few people enjoy the grueling evaluation period that typically accompanies the purchase of storage software and systems. By knowing the key points to consider and learning from the experiences of others, however, it may be possible to make the process less distasteful.

Here we take a look at two different approaches in the real world and the lessons learned:

Storage Sprint

When Sprint decided to upgrade its storage management capabilities, it wanted to avoid having to be inundated with dozens of products to evaluate.

“Deliver us from storage evals,” said Lynn Neal, senior systems integrator at Sprint. “You have to keep the whole Request for Proposal (RFP) process simple of you end up having to evaluate too many products.”

Lessons learned from Sprint’s recent storage purchases include:

  1. RFPs must neither be too general nor too specific. Too specific or too much of a shopping list and costs can mount. Too general and you end up with software doesn’t fit your needs or that lacks business value.
  2. Identify pain points and tie those in to your functional requirements. To be funded, software has to solve a real issue. Then communicate internally to determine which functions are given overall priority. By publishing the results, you can flush out any lingering disagreements. And don’t forget to achieve broad agreement from top management.
  3. Continually refer back to your RFP to avoid becoming sidetracked by vendor hype about the latest and greatest new features.

    “Keep your original documentation and refer to it often,” said Neal. “Otherwise you forget.”

  4. Use your RFP to cull responses down to a maximum of five vendors. Don’t pick any more than this or the selection process will become too complex. These are the products you are going to evaluate. And avoid beta versions unless you get an offer you can’t refuse or have a special vendor relationship.
  5. Match your test lab match to your operational environment. So the only way to do a valid test for YOUR enterprise is to set up a test system that runs the same apps with the same workloads etc. And don’t allow vendors to alter them or take an excessive period of time to complete their work in your lab.

    “Limit vendor tests to a specific time period — no more than one to two weeks,” said Neal. “Some vendors will try to tie up your test lab for weeks and throw your schedule well behind.”

  6. Score each product objectively with regard to predefined features. Keep criteria simple and score only those items. If you test correctly, the highest scoring product will be the most suitable.
  7. Once testing is completed, bring cost into the equation. This helps you evaluate value. If the top-of-the-line system is twice the price of number two, maybe you can do without a specific feature and save a fortune

Page 2: Storage Insurance

Continued from Page 1

Storage Insurance

Rather than devote a large number of staff to the RFP/eval process, Guardian Life Insurance decided to utilize a third party. The company brought in GlassHouse.

“We wanted a professional firm with experience that would be vendor agnostic as we had no time to manage the RFP process,” said Bob Mathers, vice president of IT operations at Guardian. “We knew we needed a third party as internal expertise was limited, resources were required elsewhere and we realized the time needed would be reduced by bringing in outside help.”

The company also felt that a third party would help to keep the focus on their own needs as opposed to being influenced by marketing hype, end of quarter deals and bidding wars before they had determined the right solution.

Here are some of the key elements implemented:

  1. Guardian created a team that included management, technical and operational staff from its Technology Operations Division to interface with GlassHouse.
  2. They laid out three distinct parts of the process — discovery, evaluation, and selection i.e. analyze the market to discover the likely candidates, evaluate those that most closely meet requirement and then select. This led to written RFP’s being sent to EMC, Hitachi, IBM, STK and Sun.
  3. Deliver regular progress reports to upper management.

Mathers recommends being honest with yourself when it comes to competently evaluating storage software. Do you actually have the time, expertise and resources to do the job internally? If not, farm it out to industry experts.

“Your message to senior management can be given more weight if it comes from a third party like GlassHouse,” he said.

Feature courtesy of Enterprise IT Planet.


See All Articles by
Drew Robb

Drew Robb
Drew Robb
Drew Robb is a contributing writer for Datamation, Enterprise Storage Forum, eSecurity Planet, Channel Insider, and eWeek. He has been reporting on all areas of IT for more than 25 years. He has a degree from the University of Strathclyde UK (USUK), and lives in the Tampa Bay area of Florida.

Get the Free Newsletter!

Subscribe to Cloud Insider for top news, trends, and analysis.

Latest Articles

15 Software Defined Storage Best Practices

Software Defined Storage (SDS) enables the use of commodity storage hardware. Learn 15 best practices for SDS implementation.

What is Fibre Channel over Ethernet (FCoE)?

Fibre Channel Over Ethernet (FCoE) is the encapsulation and transmission of Fibre Channel (FC) frames over enhanced Ethernet networks, combining the advantages of Ethernet...

9 Types of Computer Memory Defined (With Use Cases)

Computer memory is a term for all of the types of data storage technology that a computer may use. Learn more about the X types of computer memory.