|
Lexington Home Page
|
Help
|
About
|
Browse
Search
2010-03-11-CPC-min
Breadcrumb Navigation:
TownOfLexington-Public
>
WEB PUBLISHED-PUBLIC DOCUMENTS
>
MINUTES-REPORTS-COMMITTEES ARCHIVE
>
Community Preservation Committee-CPC
>
Minutes
>
2010-2019
>
2010
>
2010-03-11-CPC-min
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/10/2019 11:18:18 AM
Creation date
11/5/2010 12:08:41 PM
Metadata
Fields
Template:
Archives
Keywords or Subject
Minutes - CPC - Community Preservation Committee
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
4
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
<br /> <br />3. Executive Session – (for the purposes of discussing land acquisition) – <br /> Mr. <br />Cohen moved to enter into Executive Session for the purposes of discussing <br />matters relative to land acquisition. Members were polled and unanimously voted <br />to enter Executive Session at 2:30 pm. They returned to open session after a <br />unanimous vote to end Executive Session at 3:02 pm. The CPC then returned to <br />its regular meeting. <br /> <br /> <br /> <br />4.Town Offices Building Renovation – <br /> The following proponents were in <br />attendance to present new information on the Town Offices Building Project: Mr. <br />Mark Barrett, Project Manger, Mr. Pat Goddard, Director of Facilities, Mr. Carl <br />Valente, Town Manager, and Ms. Linda Vine, Assistant Town Manager. Mr. <br />Barrett distributed a 7-page document outlining the costs of the project. Mr. <br />Valente commenced the discussion, noting that there had been a small change in <br />the cost of the project since the CPC had received the previous breakdown on <br />March 9, 2010. He said the cost estimate was now $1,823,881, (up from <br />$1,821,509). The cost estimate represented a 75% design figure, with 65% of the <br />work representing code and ADA upgrades and 35% representing office <br />th <br />reorganization – a breakdown which the CPC had requested at their February 4 <br />meeting. Mr. Valente then spoke to the issue of the project’s development, stating <br />that a process had been followed similar to the process followed for capital <br />projects. <br /> <br />There were a number of questions regarding the 65%/35% split, with members <br />questioning how the project would change if the 35% were not funded. Mr. <br />Barrett responded to these questions, explaining that the two aspects of the project <br />were inseparable, and that the cost division did not represent two separate scopes <br />of work. There was a discussion of the fire suppression system, which Mr. Barrett <br />said was non-existent in the 1971 portion of the building. Ms. Fenollosa asked if <br />employees were at risk in that section of the building, to which Mr. Barrett <br />responded that they were not. <br /> <br />Mr. Barrett then explained the code and ADA upgrades, and how they are <br />specifically triggered by the overall cost of the project. The project cost, he said, <br />exceeds one third of the value of the building, and therefore triggers the legal <br />requirement for code and ADA upgrades. All the code and ADA work in the <br />project description, he noted, was legally required. Ms. Weiss tried to separate <br />certain project costs, and asked Mr. Barrett about the cost of one bathroom and <br />one counter, to which he responded that these costs would be difficult to <br />extrapolate. In response to a question from Mr. Kanter, Mr. Barrett explained that <br />the present estimate is not quite at 75% design state. Mr. Kanter asked if there <br />would be a need for an additional appropriation in order to get the project to bid, <br />to which Mr. Barrett replied that there would not. <br /> <br />2 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.