|
COPYRIGHT 2006 Ziff Davis Media Inc.
In preparation for the kickoff of a series of monthly RFP (request for proposal) templates, eWEEK Labs recently spoke with a group of IT managers to discuss best practices for the development of RFPs.
Technology Editor Peter Coffee, Executive Editor Deb Donston and Senior Writer Anne Chen spoke with members of eWEEK's Corporate Partner Advisory Board--senior IT professionals from a variety of industries and company sizes--who agreed that the quality of an RFP correlates directly with the quality of the response.
Click here [link omitted] for the first RFP in the series, on blade servers.
Roundtable Participants:
Randy Dugger, president, Dugger & Associates
Tom Miller, director of IT, FoxHollow Technologies
Nelson Ramos: CIO and Enterprise IT Strategist, Sutter Health
Robert Rosen, CIO, National Institute of Arthritis and Musculoskeletal and Skin Diseases, National Institutes of Health
Francine Siconolfi, senior project manager, Aetna
Kevin Wilson, product line manager, desktop and mobile, Duke Energy
eWEEK: When we look at RFPs, we always wonder whether the driver tends to come from inside the tech organization to business managers or from business organizations to IT. Is there a general perception that it's starting in any one corner or another?
Dugger: It's a hard subject to tackle because RFPs are so personalized for every organization and in every instance.
Rosen: Well, it depends on the RFP. Basically, there are a couple kinds of RFPs that are done. One is a fully competitive RFP that is open to the world, and whoever wants to bid on it can bid on it. Then there are others that are more narrowly defined. Typically, there is a formalized structure used in the government.
I've done way more RFPs than I ever wish I had...
Read the full article for free courtesy of your local library.
|
Bookmark this article
Print this article
Link to this article
Email this article
Digg It!
Add to del.icio.us
RSS
