Poorly Written College Town Camera RFP Examined

Avatar
Brian Karas
•Published May 25, 2016 16:06 PM

State College, PA issued an RFP for a neighborhood surveillance system that leaves out many key details required to invite qualified bids.

We review this RFP, and the problems that can arise when too many components are left to the bidder to specify.

RFP ********

************ ************ ************ ****** ****** *** ** ******* *** ******* ** ** installed ** ******* ****** ***** ****** 7 ********** *************.

*** *** **** ******** "*********** ** scale", ******** **** ****** ******* *** be ***** ** *** ******, ****** the ****** ** *********** *********** ** not *********.

Product ************** *** *****

***** **** ****** **** ********** **** be ***** ** ********* **** ******* Genetec, ** ******** ******* ************ *** listed ** *** ***.

*** ********** *** ******* ** **** likely *** ** *** ******** *** of *******'* ****** ****** ********** **********.  ******* *** **** **** ******** ** ********* surveillance ******* *** *** ******* ** bring ******** ******* ******** *****************.

*** ************** *** *** ****** *** summarized **:

****** *** ****** ****** ***** **** the ************ ** **** *** ** outlined, ***** **** ****** ****** ** a **** ******* ** ******* ***** proposed, ******* * ****** ** *** buyers ** *** *** ******** ******** competing ************ **********. 

Important ******* *******

*** *** ******** ** ******* ** the ****** ******* ** *** ******. It *** ** ******** *** ****** is ** ** **** ** ******** persons ** *** **** ** *****, but *** ***** ****** ******* ****** examples ** *** **** ****** ** use *** ******.

******** ***********, **** ** ******* ***** ****** lighting (*** **/*** *********), *****-**-*** ****** to ******** ******* *****, ***** ************ and ********** ******* ************** *** *******.

Burden *** *******, **** *** ******

******* *** ********* *******, **** ** network **************, ****** *** ****** ** bidders ** ****** ****** **** *********** out *************, ** *** *** * costly "***** ****" ******** **** ******* key ************** ***** **** **** ** be ******** ***** **** *** *******.

** *** ****** *** *** ***** of ***** ********* ******, **** *** be ******** ** ****** * *****-**** bid ***** ******* ***** **************.  ** this **** *** ****** **** ****** need ** ****** ***** ***** ***** the ****, ** ***** ** ****** to **** *** ******-**** **********, *********** resulting ** ** ******** ******* ******.

Buyers **** ** ** ********

****** ********* ***'* ****** ** ******** about ******** ****** ** ** ********, if *** ** **** ****** ** least ** *** ****** **** *** differentiate ********* ********* **** *********** *********.

**** ***** ************* **** ***** ***** people ** *** ***** **** ***** welcome ** *********** ** *********** ***** ******* and ********* ** *** ****** ********* their ***** ********** ********.

 

 

 

Comments (2)
Avatar
John Bredehoft
•May 31, 2016
Bredemarket / Incode Technologies

I realize that this would be a huge expense for a small municipality, but perhaps the local government should have done one or both of the following before issuing the RFP:

1. Issued an RFI that included the question "What information do you need to configure a system for this neighborhood?"

2. Issued a draft RFP and invited comment.

Perhaps one of the readers who participated in this bid would like to (anonymously) comment. I'd be interesting in knowing how many questions the city received on March 21, and if the city stuck to its April 4 proposal due date.

Avatar
John Bredehoft
•May 31, 2016
Bredemarket / Incode Technologies
In reply to John Bredehoft

I went to the borough website. Vendor questions and answers to questions were never posted, no addendum to the RFP is listed, and as of now there is no list of bids received, or tabulation of the bid responses.

http://www.statecollegepa.us/2484/RFPIT092--Highlands-Neighborhood