'Do It Yourself' RFP Problems

By Ben Wood, Published Jul 25, 2013, 12:00am EDT (Info+)

What's worse than having a crappy consultant prepare your RFP? Perhaps doing it yourself, as this case shows.

Everyone thinks end users should be more educated and more proactive about spec-ing equipment for surveillance projects. "They should do their research," people say. A small community in Arizona took this to heart designed their own surveillance project through Internet research, advice from integrators and online templates. But just days after the 48-page invitation for bids was drafted and published it was rescinded, and the project was cancelled. In this note, we talked to the director of the project and review this invitation for bids and explain how the IT department got put in charge. 

**********

******* **** ******, *** **** ***** Indian ********* ********** ** ********* ******* released ************ *** ****** ********* *** * ************ ****** ** monitor ******* ** **** ** ****** housing *** *** *******. ** ****** cameras ********* **** ***** ***** *** main *******, *** *****, *** ***** entry *** **** **** ** ***** different *****. *** ***** ****** *** pre-proposal ******* *** ********** ******** ********* the *******. 

A *** ** ****** *** ** *******

**** ***** ********* *** ** ****** and ** ******* *** *** *******. The ******* **** ******** ** ** Bosch ** ******** *** *** ******* calls *** *** ***** *********** [**** ** ****** available] fixed ****** **** *** ************. 

*** ** *** *******, *** ****** as * ****** ****** **** *-**** lenses, 600 ***** ** ********** *** ** ** range ** *** ****. ** ********** ** camera **** *** '***' *** **** is *********** ********** ***** *** *********** on *** ****** *** ******** ** LEDs integrated. ******, *** ***** ****'* ** * generic ****** ********** ** ****** **** Supercircuits [**** ** ****** *********]. ** is ************ ****'* ** *** ****, probably ******* ** *** **** *** focal ****** (****). *******, *** ** light ******* ** ********* *** ****** enough ** ********** ** **** ******** in *** ****. 

********

*** ******** **** *** ** *** cameras **** **** ****** ********* ******** and ***** *****, *** ****** ** provide ** ** ****** **** ***** quantify ******** ** ****** **********.

*** ***** ***** *** **********

"******* ***** ** *** ** ****** and **** ****** ** **** **********," ******* *** system ***** ******* ** * *** normally *** ** *** ** ******. This ** ***** *** *********** *** ******* ***** **** ** *-** fps

************, *** ******* ****** **** ** would **** ** ***** **** ** the ******* *** ****** *********** (***** based, *** *********). *******, ****** *******, even ** *** ********* **********, *** only ******* ***** ** ~**' **** max ***.

********* / *******

***** ********* *** ***** **** *** IT ********** *** ****** **********, ** was ****** **** *** ****** ** surveillance ********* *** **** **** **** the ******* ********** ******. *** *******, senior ********** ********** *** ****** ******* spec *** ***** **** ***** ** likely ** *******. **** ****** *******, would **** ****** ****** ** *** budget ** *** ******* ** ***** is ~$** ********** ** *** **. 2TB ***** ** ***** ************* ****** recording ******** ** *******. 

***

*** *** ********* *** *****’********** ****** ****** ******* ******** ********. ** *** ** support ****** ******** ** *** *** and ** ** * ********** ** channels ** ** *** **** *** provide **** ** ** *******. *** housing **********’* ******* ** ***** ******** ******** **** **** ***** ******* ** using Vicon for ** ******** ****** ********* ** the *********, *** **** **** *** ****** ******* of *** *******’* **** ******** ******. *** ********* *** ** ******** surveillance ******, *** *** ******* *** the ******* **** ** *** *** know *** ******* ** *** ******. 

************, *** **** **** * ******* ** "five ** ****** ************* **** ** supported **** ******* ********* **** ** Bosch, ****, ******* ******, **********, *********, Sony *** *****" ***** **** ***** have **** ********* **** ** ** ONVIF *********. 

***********

*** ******* ********** ****** * *** year ******** **** ******* *** ** ongoing ******* *********. ** **** ** that ****, *** ********* ***** ** responsible *** *********** *** ******* ****** the ******** ****** *** ***** ** expected ** *** *** ******** ****** six *****. ** *** ********** ******* that * **** **** **** ***** be *** ********* ** **** *** ******* department **** *** * ************ ******, the ** ********** **** ** ** charge ** ***********. 

Project *********

*** ******* *** ********* *** **** design *** ********* *******, ********* ** the ******* *******. ***** *********** **** of *** ********* ******* *** ***** of *** *******, *** ******* ***** that * ******** ****** *** ***** to **** **** **** ** ********** for **** *** **** **** ******** needed ***** *** ** *** ******* ** ** ********** ***** **** * chance ** ****** * ****** **** would **** *** ***** ***** ****** than ******* *** ****** ****** ** a **** ** ********* **** *****'* that ******** ****.

******* ** *** ******* **********, *** IT ********** **** ** ******** *** final ***.

**** ** *** *****, ********* *** "300 ** ** ******" **** ****** from ******** ********, ****** **** *********** and ***** ************ ****** ********* ******, according ** *** ******* *******. ** ***** that *** ***** ****** **** **** of * **** ** ******* ************ ** fit ***** *****, *** ************* **** is ** ******* ** *** **** are ***** ********** ** **** **** decisions, **** **** **** *** *********. 

 

 

 

Comments (3)

There's an old axiom for end user companies: Don't let the vendor define your needs. Do your homework, define your expectations, and let the providers define a solution that WILL WORK. Its more often the case a company will cruise publications and Web pages, pluck disconnected brands, platforms & performance spec (marketing hype?) to build a system specification for publication which integrators just look at and moan.

I love working with clients who know what they want to do or want to see and ask us to propose a solution. They're not all that rare. We have to speak directly to the issues when we interact with the potential client. A reputation for excellence and willingness to walk away from an impossible RFP will serve far longer than taking a project doomed to fail in the end! Sometimes you just have to ask "What were you smoking when you wrote this?"!

If hope my IT brothers and sisters do actually do their research, AND consult with a professional who is actually experianced in surveillance, or alas, it will be another Cisco Surveillance system installed.

Jack Sink: There's an old axiom for end user companies: Don't let the vendor define your needs. Do your homework, define your expectations, and let the providers define a solution that WILL WORK.

I agree.

Then, ask the providers why they choose that brand, technology, devices distribution, etc. And totally valid to ask "why if we change this"...

I think customers should explain what they need and providers how they will try to give a solution in order to obtain the better system possible for each case in a given time.

Login to read this IPVM report.
Why do I need to log in?
IPVM conducts reporting, tutorials and software funded by subscriber's payments enabling us to offer the most independent, accurate and in-depth information.
Loading Related Reports