My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
01-28-1999
MoundsView
>
Commissions
>
Economic Development Commission
>
Agenda Packets
>
1990-1999
>
1999
>
01-28-1999
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/20/2018 5:29:12 AM
Creation date
8/20/2018 5:29:07 AM
Metadata
Fields
Template:
MV EDC
EDC Document Type
Council Packets
Date
1/28/1999
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
45
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).
Show annotations
View images
View plain text
To: Economic Development Commission Members <br /> From: Kevin Carroll, Economic Development Coordinator MEMORANDUM <br /> R <br /> IOtlf'IMDUM <br /> • <br /> Subject: Discussion of the Mermaid Hotel/Banquet Center <br /> [Development Agreement] <br /> Date: January 25, 1999 <br /> As you will recall, the entire EDC meeting on December 10th was devoted to a discussion of <br /> various aspects of the Mermaid proposal. At that time, staff members were in the process of <br /> reviewing some revisions(suggested by the Developers)to the initial draft of the <br /> Development-Agreement. The comments and suggestions that were made by the EDC <br /> members during the 12-10-98 meeting were incorporated into a revised draft of the <br /> Development Agreement,which was then forwarded to the Developers and their attorney <br /> for review and comment. I subsequently met with John Seibert, Dan Hall and his attorney <br /> (Mr. Chris Berndt)on January 7, 1998 to discuss the revised Development Agreement. A �.. <br /> copy of that Agreement has been enclosed for your review. The provisions that are <br /> underlined represent, for the most part, changes that were suggested by the EDC and/or city <br /> staff members. <br /> During that meeting, it became apparent that the Developer had no objection to most of the <br /> new provisions that had been suggested by the EDC and city staff. However, the Developer <br /> have some concerns about the language requiring an unspecified cash equity "injection" <br /> by the Developer, and personal guarantees on the part of the Developer's principals, as <br /> prerequisites to the use of TIF(tax increment financing) proceeds for the reimbursement of <br /> [some of]the Developer's project costs. At my request, the Developer's attorney <br /> summarized his client's position on this matter in a letter dated January 22, 1999, a copy of <br /> which has been attached for your review. As you will note,the letter also addresses certain <br /> other aspects of the proposed project, induding the identity of the "Developer,"the revised <br /> project costs, and potential "spinoff" benefits. <br /> An important issue for the EDC (and, ultimately, for the City Council)to address relates to <br /> the propriety, nature and amount of financial assistance from the City. Much of the discussion <br /> to date has focused on the Developer's request that the City contribute up to $550,000 <br /> toward the cost of acquiring the Rent All site. The proposed source of the funds in question <br /> would be the City's "pooled TIF account," which consists of tax increments received by the <br /> City in excess of the amounts needed by the City to make bond payments and other fixed <br /> obligations related to the existing TIF districts. Some concerns have been expressed <br /> regarding the impact(on existing and planned programs)of a "one-time" $550,000 deduction <br /> from the pooled TIF account. In the interest of exploring other options and reexamining <br /> some of our original financial assumptions, I recently contacted Public Financial Management <br /> •' (PFM), one of the City's financial consultants. PFM was asked to generate financial information <br /> regarding these two new "scenarios": <br /> ■ <br />
The URL can be used to link to this page
Your browser does not support the video tag.