My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Special Project Oversight Committee (SPOC) Report #1
>
CS_Courthouse Square
>
Special Project Oversight Committee (SPOC) Report #1
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/20/2012 7:44:14 AM
Creation date
9/6/2011 12:12:53 PM
Metadata
Fields
Template:
Building
RecordID
10317
Title
Special Project Oversight Committee (SPOC) Report #1
Company
Marion County
BLDG Date
11/14/1997
Building
Courthouse Square
BLDG Document Type
Committee
Project ID
CS9601 Courthouse Square Research
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
188
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
~ Berrey was requested to modify his originai proposal by a special review committee <br />when it was determined ta~c exempt financing could be used. By August of 1996, a <br />preliminary financial analysis indicated the county would need to finance $14 million in <br />order to acquire ownership of 72,000 sf of office space. The rental rate, paid by county <br />departments, to cover operations & ma.intenance (O&M) and debt service, ranged <br />between $1.20 and $1.40/sf. <br />In December of 1996, Mr. Berrey produced the first financial analysis (proforma) based <br />on a conceptual design and cost estimates from the contractor. The total project cost was <br />estimated at $30 million. The county would own 72,000 sf at an estimated cost of $12.8 <br />million. The proforma estimated a rental rate of $1.17/sf. However, Mr. Bertey <br />cautioned the county to maintain a budget estimate based on $1.30-1.35/sf. A$3.6 <br />million underground parking structure was included in the cost estimate containing 335 <br />stalls. <br />The ne~rt significant change in the project scope occurred in February of 1997. Mr. <br />Berrey was developing 60,000 sf of office space which the county would lease or <br />purchase for future e~cpansion. Our financial advisors suggested that the county build the <br />expansion space and lease it to the private market. Mr. Berrey's proforma estimated the <br />cost of this additional office space at $5.3 million. However, later cost estimates <br />increased the cost of the expansion space to $13 million. As construction costs were <br />refined the total cost of the projected had escalated to $37 million. The county's share of <br />the project was now estimated at $25 million. <br />During the months of May and June, the county asked our independent financial advisors <br />to prepare new proformas. These analysis' gave us the first indication that the origiuaal <br />budget goals were unrealistic. The analysis also indicated that the parking structure was <br />oversized and was an economic drai.n on the project. The parking issue was d,ifficult to <br />address because private business concerns and the city parking boazd encouraged us to <br />build as much parking as possible. Revenues necessary to support the project were over- <br />inflated and the overall unit cost of the building was still too high. In addition, <br />independent reports from the Salem business community raised concerns that the county <br />could not, and should not, support the risk associated with overbuilding and leasing <br />excessive expansion space. <br />On July 31 1997, with the concurrence of our new developers (Melvin Mark Co.) the <br />county stopped the design process and directed the development team to study new <br />down-sized options for our consideration. The architects were asked to consider a <br />smaller (one-level) parking structure, reduce the size of the office building from 180,000 <br />gsf to 150,000 gsf and separate the public and private portions of the development for <br />easier and more fle~cible financing options. <br />
The URL can be used to link to this page
Your browser does not support the video tag.