My WebLink
|
Help
|
About
|
Sign Out
Home
CC_Minutes_2011_0926
Roseville
>
City Council
>
City Council Meeting Minutes
>
201x
>
2011
>
CC_Minutes_2011_0926
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/11/2011 12:00:49 PM
Creation date
10/11/2011 12:00:40 PM
Metadata
Fields
Template:
Roseville City Council
Document Type
Council Minutes
Meeting Date
9/26/2011
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
62
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Regular City Council Meeting <br /> Monday, September 26, 2011 <br /> Page 30 <br /> Chief O'Neill advised that in the two (2)processes he'd used to-date: construction <br /> manager and architectural services, there was an evaluation guide for the team to <br /> use if they felt proposals were strong or weak, with the guide used from informa- <br /> tion provided by ASU. Chief O'Neill reviewed the preparation for the interview <br /> portion of the process upon receipt of the proposals; and redaction of information <br /> to remove any references to the firm or its principles to ensure a blind process. <br /> On a personal note, Chief O'Neill advised that during his review of the proposal, <br /> he noted his questions throughout each proposal in just about every category; and <br /> advised that the interview allowed him an opportunity to sit down with the entire <br /> architectural team to specifically discuss the Roseville project, as well as other <br /> projects they've done; and opined that this interview process was the most impor- <br /> tant part and allowed him to gain the most information on who would be best for a <br /> particular project. <br /> Councilmember Pust questioned if they should be called interviews since scoring <br /> was not based on interview skills or personalities, but the additional information <br /> made available in evaluating their proposal. <br /> Chief O'Neill opined that the interview included perceptions on whether they <br /> would be able to complete a project on time; their background with geothermal <br /> systems; and included each member of the evaluation team asking standard, as <br /> well as specific questions, based on the proposals; while being aware of various <br /> nuances they bring to the table. <br /> Further discussion ensued regarding the highest possible scores in the various cat- <br /> egories (fees, past performance, background, risk assessment) with seven evalua- <br /> tors involved in the interviews, two of whom consisted of representatives from the <br /> construction management team; series of questions based on evaluator notes from <br /> each proposal, with additional questions varying based on specific proposals. <br /> Councilmember McGehee brought to the attention of Councilmember Pust the <br /> spread from the previous proposals and the spread between the top•two firms. <br /> Councilmember Pust opined that this didn't matter to her as much as if potential <br /> points were different than other categories; and asked that Mayor Roe, from his <br /> engineering expertise, provide a mathematical analysis of the categories for com- <br /> parison; and with how close two of the firms were, if it was prudent to standardize <br /> the weighting. <br /> Councilmember Johnson opined, from a business perspective on interviews and <br /> form a managerial point of view, the interview phase should be a key aspect, since <br /> the project manager needed a relationship with City staff as well as the construe- <br />, tion management team and the full architectural team. While recognizing that <br /> cost was an issue, Councilmember Johnson opined that if there was no artistry, <br /> chemistry, or camaraderie, it would not be as effective of a relationship. Coun- <br />
The URL can be used to link to this page
Your browser does not support the video tag.