Commentary

Michael Singer
 

VoiceCon: Make Your RFP Future Proof

The world of VoIP, video, and instant messaging is traveling at such a speed that your request to evaluate competing products may be obsolete by the time you finish reading this sentence.

The world of VoIP, video, and instant messaging is traveling at such a speed that your request to evaluate competing products may be obsolete by the time you finish reading this sentence.So a group of like-minded industry individuals have come up with a so-called open source solution to the problem.

Spearheaded by Ed Mier and Dave Mier and sponsored by Siemens, a new wiki has been established to create a future-proof template request for proposal (RFP) for next-generation IP communications systems.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Introduced at the VoiceCon show in San Francisco, which runs through Thursday, the wiki tries to get into the details of what you'd specify if you were going out to bid with the aim of providing unified communications functionality for your users.

"What we'll be encouraging the industry to do is treat Ed and Dave's RFI/RFP as an open source project. There's no ownership involved, so you can download it and use it however you'd like. What we'd ask in return is that you join the conversation: We've set the project up as a wiki so that you can edit the document, add to it, or submit wholesale revisions if you think this one misses the mark, or submit versions tailored to specific industries or applications," said Eric Krapf, editor at Business Communications Review and VoiceCon program chair.

The template could have benefited national power tool retailer Black & Decker. Karen Dean, director of global telecommunications told the VoiceCon audience on Tuesday that her company went through a couple of RFIs before settling on Avaya's solution.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links