My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 10/09/2001
Ramsey
>
Public
>
Agendas
>
Council
>
2001
>
Agenda - Council - 10/09/2001
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/25/2025 12:28:13 PM
Creation date
9/4/2003 3:10:54 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
10/09/2001
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
252
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
-210- <br /> <br />Thomas B. Olson <br />Page 2 <br />August 10, 2001 <br /> <br />As cited in your June 28 letter, Substantially Complete is a defined contractual term in Section <br />9.81 of the Agreement where said term as "... when the Work... is sufficiently complete.., so <br />that the Owner can occupy or utilize the Work for its intended use." The Contractor asserts that <br />the substantial completion date is January 31, 2001, however, the Owner and Architect dispute <br />this date as amongst other things, the building on January 31 was not weather tight. Exterior <br />panels at the top of the building walls were not installed and outside weather was still able to <br />invade the building. On February 7, 200l the Contractor, by letter, stated that the "punch list" <br />was submitted on February 6, 2001 and requested an inspection on February 8, 2001 "... to <br />determine whether the work or portion thereof is substantially complete...". Clearly this is in~ <br />consistent with a January 31 substantial completion date asserted by the Contractor. See <br />attached Exhibit "A". Furthermore, the Contractor failed to follow the Agreement requirements, <br />Section 01770 to obtain the Substantial Completion status. This section specifically outlines the <br />procedure required for substantial completion, one of which, requirements is to "Submit specific <br />warranties." These were not delivered until at least March 8, 2001. See attached Exhibit "B". <br /> <br />In your letter of June 28, 200l, you state that various change orders permitted additional time <br />extensions. My review of the change orders indicates that while additional time was requested, <br />none was granted except for 15 additional days pursuant to four Architect's Supplemental <br />Instructions and Change Proposal ("ASI"). These are ASI Nos. 24, 31, 34 and 57. See attached <br />Exhibit "C". In the event we are able to settle this matter, I will recommend to the Owner that its <br />claim for liquidated damages be reduced fi.om 87 days to 72 days. I find no evidence that <br />additional time was ganted pursuant to verbal change orders as you claim. <br /> <br />For your information, the Owner and Architect advise me that the Contractor got behind in the <br />Project generally as a result of its failure to timely order the steel. This then precipitated the <br />completion date issues and is why we are now discussing this liquidated damages claim. <br />Additionally, see the letter dated October 22, 2000 attached as Exhibit "D" from the City's <br />Architect, Nancy Schultz, in which concerns about the Project schedule on that date were already <br />apparent. <br /> <br />In your various correspondence you threaten to "sue" the City/Owner. I would like to bring, to <br />your attention Sections 4.5 and 4.6 of the Agreement which call for disputes to be settled throu~ <br />mediation and ultimately arbitration. Please advise if you have reason to believe these <br />provisions are not applicable to the present dispute. <br /> <br />I <br />I <br />I <br />! <br />I <br />I <br />I <br />I <br />! <br />I <br />I <br />I <br />i <br />i <br />I <br />i <br />I <br />I <br />I <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.