|
Lexington Home Page
|
Help
|
About
|
Browse
Search
2024-01-11-PBC-min
Breadcrumb Navigation:
TownOfLexington-Public
>
WEB PUBLISHED-PUBLIC DOCUMENTS
>
MINUTES-REPORTS-COMMITTEES ARCHIVE
>
Permanent Building Committee-PBC
>
Minutes
>
2024
>
2024-01-11-PBC-min
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/1/2024 10:54:43 AM
Creation date
5/1/2024 10:50:17 AM
Metadata
Fields
Template:
Archives
Year
2024
Author or Source
Mark Barrett, Project Manager
Department
Town Clerk
Keywords or Subject
Minutes
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
Jon Himmel noted that there were weekly SBC meetings. He discussed that a postcard should be received by all <br />Lexington residents a week before the community meeting so everyone was aware of it. There was a scheduling <br />working group meeting on January 18th. It was discussed that any land taken out of recreational land had to have <br />similar land added. <br /> <br />There was a meeting during the week of January 15th to discuss the integrative design process. <br /> <br />A milestone look ahead document was shared, which included the dates, meetings, and topics. The document <br />would be issued at the next SBC. A checklist was created after going through the IDP to put deliverables on a <br />spreadsheet, and it was stated that feedback on the checklist would be helpful. The checklist would be a matter of <br />record as part of the packet after the SBC meeting. It was suggested to have the documents on their own on the <br />website. It was suggested to watermark the document as tentative so that it could be posted. It was stated that a <br />meeting log was required to be kept, and an agenda column was added to show what was being discussed at each <br />meeting. The meeting log would also be publicly available. It was discussed that some critical dates were important <br />for everyone to attend, so having the meeting log in advance was helpful. It was decided that documents should be <br />simultaneously sent to the Sustainable Lexington Committee and the PBC. Mike Burton presented the integrated <br />design policy checklist and explained it. It had a policy column, a status column, any actions and comments, and <br />their corresponding dates. The second section covered attachment B and showed the same columns. It was asked <br />if there was a way to circulate the information about what was decided at meetings. Mike Burton stated that he <br />could share the information with the appropriate people. <br /> <br />It was stated that no decisions had been made on parking/EV charging yet. It was requested having some element <br />of the reports be sent to the members of the PBC. It was suggested to have a presentation go to committees prior <br />to the town meeting. David Kanter stated that the public would appreciate an explanation of the cost and what was <br />happening in the project and asked that periodic updates be made available to the Finance Committee. Jon Himmel <br />stated that there would be crude estimates, but these would be more relative costs and not absolute costs. For <br />instance, upgrade and renovation will involve more general conditions (GCs) for shiftwork, so we need to discuss <br />how to make informed comparisons. It was discussed that a schedule of when items would be available could be <br />provided. It was stated that the cost estimates would be available in April, but it was clarified that these would not be <br />the final numbers as there would be many decisions to be made, but even benchmark costs would be helpful in <br />choosing options. David Kanter stated that enough information was needed to provide before the town meeting, and <br />he stated that the report to the town meeting needed to make a compelling sense of what was being done so that <br />everyone understood it. It was suggested that potential adjustments that would be made to the costs be discussed <br />during the February meeting. <br /> <br />Mike Burton stated that once the educational program was finalized, the MSBA would measure all options based on <br />the educational program. Lorraine Finnegan noted that meetings will be held with the estimators to provide the <br />necessary information. She stated that the package of the preliminary costs would be sent at the end of March so <br />that the pre-estimate conversation would be held in March. Lorraine Finnegan stated that she could provide the <br />information from the conversation with the estimators at the March PBC meeting. <br /> <br />It was discussed that the school committee meets for five hours per month and may need some assistance. It was <br />stated that the PBC meetings may need to be shifted. It was stated that the schedule dictates what is being <br />produced, and meetings should be scheduled shortly after the material was issued. It was stated that the milestones <br />should be discussed in the scheduling work group. It was discussed to hold joint meetings with the SBC. It was <br />discussed that the intent of the discussion was for the PBC to share the knowledge in advance of meetings. Jon <br />emphasized that the PBC wants to review schedule, costs, massing and materials, in advance of presentations to <br />the SBC. Also, site logistics is a priority, the PBC should discuss and review even at the conceptual stage. It was <br />discussed that finished documentation to be presented at the PBC prior to it going to the School Building <br />Committee was not necessary. It was suggested to have members of the community look at the meeting minutes <br />and send their thoughts to Mark Barrett. Jon Himmel stated that the current draft of the 12/6/23 minutes should be <br />shared with the consulting team, and then there could be discussions on any changes to the schedule. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.