Cerberus…who writes the RFP?
Steven Schwartz
Image via Wikipedia
In the past 10 years RFP (Request for Proposal) has been growing in the mid-Enterprise space. I actually saw an RFP, written by Glasshouse under contract, for a smaller law firm in Illinois. This RFP was about 80 pages (25 of witch were detailed technical questions on SAN, NAS, and Backup/Recovery). This customer wanted the entire solution of the top three chosen vendors set-up for testing in the Vendor’s labs, for a minimum of two weeks for the customer to test performance, features, and functionality. Additionally, they wanted to fully test replication and application failover during this lab time, they required the full proposal to be built out with the proposed servers, switches, storage, etc. Now I’m all for bending over backwards for a customer, but to put together a FULL POC(proof of Concept) with NO Conditional Purchase Order in place??? I’m not unreasonable, but this seemed a bit unreasonable. The reality, budget got pulled away from this IT project for the customer, and the RFP was killed. However, in the process for responding to the RFP there were several questions that were “crafted” to a specific solution from a specific vendor.
RFP Authors
So, this leads me to who authors a customer RFP. In complete disclosure, when I was Infrastructure Architect many years ago, and I had personally chosen the solution I felt was write for our company, I wrote an RFP (which was required by our purchasing process) that leaned very heavily in features and specifications toward a single vendors product. I would assume that others have done the same, however, where I drew the line, was letting the vendor help me write the RFP.
The “consulting firm” is also contracted for RFP creation. In general, hired contractors are just that, they have a job to do, and they get paid for it. They typically have relationships with the customer and with vendors. The problem with a consulting firms, is typically they are also paid for implementation and design work as well, they have a bag of vendors that they know work, and they know enough about to meet the customers requirements. The problem with this model, it is usually a biased opinion, NOT INTENTIONALLY!!!!
Lastly, the vendor. I’ve had several vendors over the years offer to “help” with canned RFP templates,so that “I wouldn’t have to start from scratch”. Clearly, we know all of the legal, ethical and moral problems with this approach. This is disgusting behavior on the part of a vendor!
So, in order to help potential customers and vendors out there I’ve put together the following list of terms and phrases that are RED FLAGS that an RFP has been written for a specific product. This helps customers, so that they don’t use terms like this causing other vendors the in-ability to compete. This helps vendors, because it shows if an RFP has been “unintentionally” biased. This are primarily geared to storage RFPs.
- Storage Group
- Most likely PS-Series, Dell | Equallogic
- Member(s)
- Most likely PS-Series, Dell | Equallogic
- All Inclusive
- PS-Series, Dell | Equallogic
- SAN IQ, LeftHand Networks (HP in 2009)
- Frameless Architecture
- PS-Series, Dell | Equallogic
- SAN IQ, LeftHand Networks (HP in 2009)
- Campus SAN
- SAN iQ, LeftHand Networks (HP in 2009)
- Data Progression
- Compellent
- Commodity Architecture
- SAN IQ, LeftHand Networks (HP in 200)
- Compellent
- Filer (Clustered Filers)
- Aggregates
- NetApp
- FlexVol
- NetApp
- Primary Volume A-SIS
- NetApp
- High Performance RAID6 (Fast RAID6)
- NetApp
- Meta Volumes
- EMC
- Business Continuance Volumes
- EMC
- Shadowimage
- HDS
- Composite Device
- HDS
- TrueCopy
- HDS
- FlashCopy
- IBM
- Space-Efficient Disks
- IBM
- Global Mirror
- IBM
- Grid Containers
- SUN | STK
- Predictive Self-Healing
- SUN | STK
This list can go on and on, but these are some common ones that I’ve seen in some recent RFPs that have crossed my desk.
Related articles by Zemanta
Posted in Enterprise, General |
10 Comments »

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_c.png?x-id=d7716cfa-f9dc-46a5-bf62-ba9083dccfb2)