<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>

<channel>
	<title>Telecom Auditing Guide &#124; Telecom Expense Management Blog&#187; RFP</title>
	<atom:link href="http://www.telecomauditguide.com/category/rfp/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.telecomauditguide.com</link>
	<description>"Telecom Tips and Strategies" by TelCon Associates, Inc.</description>
	<pubDate>Thu, 26 Jan 2012 17:31:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How to Construct an Effective RFP</title>
		<link>http://www.telecomauditguide.com/rfp/how-to-construct-an-effective-rfp/</link>
		<comments>http://www.telecomauditguide.com/rfp/how-to-construct-an-effective-rfp/#comments</comments>
		<pubDate>Thu, 07 Feb 2008 14:46:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[RFP]]></category>

		<category><![CDATA[telecom request for proposal]]></category>

		<category><![CDATA[telecom rfp]]></category>

		<guid isPermaLink="false">http://www.telecomauditguide.com/rfp/how-to-construct-an-effective-rfp/</guid>
		<description><![CDATA[                           Every day across the business world, potential customers                     [...]]]></description>
			<content:encoded><![CDATA[<p><font face="Verdana, Arial, Helvetica, sans-serif" size="2">                           Every day across the business world, potential customers                            interact with  vendors and providers of goods and services through                            signed agreements, often referred to as the &#8220;RFP&#8221;                            or &#8220;Request for Proposal&#8221;.<br />
</font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">In                            the telecom industry, the RFP can serve as the means                            for purchasing equipment as well as the preferred path                            by companies and government agencies to obtain telecom                            services and maintenance agreements from telecom carriers                            themselves.</font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">Although                            the circumstances and desired results will have a big                            impact as to the length, specificity, and detail of                            an RFP, there are certain points that you must consider                            when attempting to construct one that is effective.</font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">To                            maximize the result and time spent on the RFP itself,                            be sure your RFP contains the following:</font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">1)                            <strong>A Table of Contents</strong><br />
The organization of material contained within the RFP                            is best outlined in the beginning:the table of contents.                            Outline each area of the RFP in neat detail so that                            readers will be able to quickly scan content and understand                            exactly how the RFP has been organized.</font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">2)<strong>                            A Situation Summary</strong><br />
This area provides the reader background information                            about your company or organization - the nature of the                            enterprise, size and scope, a brief history, ownership                            information, etc. as well as an overview of the current                            telecom systems and the reasons and concerns for making                            changes. </font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">3)                            <strong>Required Rules of Response</strong><br />
An effective RFP will provide bidders with specific                            and concise terms under which they must respond. You                            will save alot of time and confusion by making this                            section of the RFP specific and detailed. In it, consider                            answering questions such as:</font></p>
<p align="left">
<ul>
<li> <font face="Verdana, Arial, Helvetica, sans-serif" size="2">When                              is the due date for proposals?</font></li>
<li> <font face="Verdana, Arial, Helvetica, sans-serif" size="2">To                              whom is the response to be delivered and how many                              copies are needed?</font></li>
<li><font face="Verdana, Arial, Helvetica, sans-serif" size="2">What                              format should the response be in? What kind of supporting                              material will be needed?</font></li>
<li><font face="Verdana, Arial, Helvetica, sans-serif" size="2">Who                              is the contact person for additional information or                              premises inspections if available?</font></li>
<li><font face="Verdana, Arial, Helvetica, sans-serif" size="2">Are                              there any exceptions in the proposal and if so, to                              what degree will you accept?</font></li>
</ul>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">4)<strong>                            Functional Objectives </strong><br />
An effective RFP should explain exactly what you wish                            to accomplish with the new system or service that is                            to be implemented AND what you expect it to do for you.                            It is in this &#8220;functional objectives&#8221; area                            that you will outline the needs analysis, operational                            considerations, traffic details, etc. </font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">5)                          <strong>Specifications</strong><br />
Once you have outlined the functional objectives, you                          will need to state the specifics for which that objective                          can be achieved. This section can be generic in nature                          or very specific. When in doubt, try to be as specific                          as to the number, size, color, type, etc. to eliminate                          confusion.</font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">6)                          <strong>Delivery and Installation</strong><br />
Here you will outline the location of the products and/or                          services to be delivered, connected and exactly when they                          must be operational. Technical installation requirements                          and any unusual scheduling considerations should also                          be included.</font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">7)                          <strong>Documentation and Training</strong><br />
This section specifies the required physical labeling                          of components, circuits, terminations, etc. You may wish                          to consider requiring diagram layouts that identify the                          location of fixed equipment and/or all cable runs needed.                          Provision of installation and technical manuals, user                          instructions, and personnel training should also be included.</font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">8)                          <strong>Warranties, technical service and maintenance</strong><br />
This section addresses the availability, terms, guaranteed                          response time, costs, etc. during the life of the contract.                          Specify bases for pricing (i.e. a purchase, 3 year lease,                          monthly lease, etc.) and any allowances (trade-ins, prompt                          payment, etc.) and rate guarantees. Strive to allow vendors                          to include complete information in this section so that                          the evaluation process is made that much easier.</font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">9)                          <strong>Vendor information</strong><br />
Lastly, it is a good idea to create an opportunity (questionnaire)                          for vendors to provide information about themselves. Most                          will do so regardless, but may not address your questions                          thoroughly. A short questionnaire of information you require                          can be helpful when sifting through bidders.</font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">After                          completing your RFP, put yourself in the vendors&#8217; position.                          Is it clear and concise? Can you perhaps be more specific                          in any areas to avoid confusion? Less specific? </font></p>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">10)                          <strong>Contract Review</strong><br />
Overall, make your RFP easy for the vendor to understand                          and respond. Once you&#8217;ve made your decision, you&#8217;ll need                          to review the contract and check for the following items                          and make provisions for them if needed:</font></p>
<ul>
<li><font face="Verdana, Arial, Helvetica, sans-serif" size="2">                            A termination clause outlining penalties </font></li>
<li><font face="Verdana, Arial, Helvetica, sans-serif" size="2">                            Network performance clauses</font></li>
<li><font face="Verdana, Arial, Helvetica, sans-serif" size="2">Renewal                            clause that works for both parties</font></li>
<li><font face="Verdana, Arial, Helvetica, sans-serif" size="2">An                            escalation clause in case things do not go as planned</font></li>
<li><font face="Verdana, Arial, Helvetica, sans-serif" size="2">Business                            downturn or growth clause</font></li>
</ul>
<p align="left"><font face="Verdana, Arial, Helvetica, sans-serif" size="2">Once                          you have finalized everything and signed the contract,                          you should be well on your way to a positive and lasting                          relationship with the chosen vendor or service provider.</font></p>
<p align="left">Contributed by: <a href="http://www.telconassociates.com">TelCon Associates</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.telecomauditguide.com/rfp/how-to-construct-an-effective-rfp/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>

