2017 ORS 381.310¹
Port of Hood River bridge projects
  • definitions
  • agreements
  • evaluation of proposals

(1) As used in this section and ORS 381.312 (Tolls, administrative fees and civil penalties in connection with Port of Hood River bridges):

(a) “Bridge” means an existing bridge, or a completed bridge that results from a bridge project, and any related facilities.

(b) “Bridge project” means a project to construct, reconstruct or replace a bridge that spans the Columbia River, and any related facilities, that a private entity undertakes in accordance with:

(A) An agreement with the Port of Hood River that requires the private entity to fund, in whole or in part, the construction, reconstruction or replacement; and

(B) Rules that the port adopts in accordance with subsection (4)(b) of this section.

(c) “Bridge project activity” means an activity that a private entity undertakes in accordance with an agreement with the Port of Hood River to plan, acquire, finance, develop, design, construct, reconstruct, replace, improve, maintain, manage, repair, lease, operate or otherwise develop a bridge that spans the Columbia River to Washington State and any related facilities.

(d) “Related facilities” means real or personal property for:

(A) Operating, maintaining, renovating or facilitating the use of a bridge;

(B) Providing goods and services to people who use a bridge; or

(C) Generating revenue that can reduce tolls or that will be deposited in an account established under an agreement described in this section.

(2)(a) For the purposes set forth in paragraph (b) of this subsection and subject to the requirements of subsection (3) of this section, the Port of Hood River may enter into an agreement for a bridge project that is partially or completely within the port’s district.

(b) The purposes of entering into an agreement under paragraph (a) of this subsection are to:

(A) Develop an expedited project delivery process;

(B) Maximize innovation in project design, construction, delivery or financing; and

(C) Develop partnerships with private entities or units of government.

(3)(a) An agreement under subsection (2) of this section must, at a minimum, specify:

(A) At what point in the bridge project the public and private partners will assume responsibility for specific elements of the bridge project;

(B) How the public and private partners will share costs and risks of the bridge project;

(C) How the public and private partners will allocate financial responsibility for cost overruns;

(D) Incentives to perform and penalties for a failure to perform an element of the bridge project;

(E) Accounting and auditing standards for evaluating work on the bridge project; and

(F) Whether the bridge project is consistent with the plan that the Oregon Transportation Commission developed under ORS 184.618 and any applicable regional transportation plans or local transportation system programs and, if the bridge project is not consistent with the plans or programs, how and when the bridge project will become consistent with the plans and programs.

(b) In addition to the specifications set forth in paragraph (a) of this subsection, the agreement must:

(A) Establish an account into which proceeds from tolls, administrative fees and civil penalties from the bridge may be deposited;

(B) Provide that the public has dedicated and unrestricted use of the bridge for the duration of the bridge’s functional life unless the port, a state government or the federal government declares an emergency that forbids using the bridge; and

(C) Provide that construction of the bridge project may not proceed until the Department of Transportation has issued, in accordance with ORS 374.305 (Necessity of permission to build on rights of way), any permits that are necessary to connect the bridge project to state highways.

(c) The port may include in an agreement under subsection (2) of this section any financing mechanisms, including but not limited to imposing and collecting franchise fees, user fees or tolls, and any other revenue sources the public and private partners may use.

(4)(a) ORS 279.835 (Definitions for ORS 279.835 to 279.855) to 279.855 (Entities that may obtain goods and services through Oregon Department of Administrative Services) and ORS chapters 279A, 279B and 279C do not apply to an agreement that the port enters into under subsection (2) of this section, or to bridge project activity undertaken in accordance with the agreement, except that if the bridge project activity is a public works, as defined in ORS 279C.800 (Definitions for ORS 279C.800 to 279C.870):

(A) ORS 279C.380 (Performance bond), 279C.385 (Return or retention of bid security), 279C.390 (Exemption of contracts from bid security and bonds) and 279C.800 (Definitions for ORS 279C.800 to 279C.870) to 279C.870 (Civil action to enforce payment of prevailing rates of wage) apply to the bridge project activity; and

(B) Any agreement for constructing, reconstructing, performing a major renovation on or painting the bridge project must provide for paying workers under the agreement in accordance with ORS 279C.540 (Maximum hours of labor on public contracts) and 279C.800 (Definitions for ORS 279C.800 to 279C.870) to 279C.870 (Civil action to enforce payment of prevailing rates of wage).

(b) Before entering into an agreement under subsection (2) of this section, the port shall adopt rules that substantially conform with the rules that the Department of Transportation has adopted, as of January 1, 2018, to implement the provisions of ORS 367.800 (Findings) to 367.824 (Rules).

(5) Sensitive business, commercial or financial information that a private entity provides to the port for the purpose of evaluating a proposal from the private entity for a bridge project is exempt from disclosure under ORS 192.311 (Definitions for ORS 192.311 to 192.478) to 192.478 (Exemption for Judicial Department). The terms of a proposed or final agreement between the port and a private entity are subject to disclosure under ORS 192.311 (Definitions for ORS 192.311 to 192.478) to 192.478 (Exemption for Judicial Department).

(6)(a) In evaluating proposals for a bridge project, in addition to considering a proposer’s estimate of the cost for the bridge project, the port shall consider all of these elements:

(A) The qualities of the design that the proposer submits, if appropriate, including:

(i) The structural integrity of the design and how the design will likely affect future costs of maintaining the bridge;

(ii) The aesthetic qualities of the design and other aspects of the design such as the width of lane separators, landscaping and sound walls;

(iii) The traffic capacity of the design;

(iv) Aspects of the design that affect safety, such as lane width, the quality of lane markers and separators, the shape and positioning of ramps and curves and changes in elevation; and

(v) The ease with which traffic will pass through any toll collection facilities.

(B) The extent to which the bridge project will involve small businesses. The port shall encourage small businesses to participate in the bridge project to the maximum extent that the port determines is practicable. As used in this subparagraph:

(i) “Small business” means an independent business with fewer than 20 employees and with average annual gross receipts during the last three years of not more than $1 million for construction firms and not more than $300,000 for businesses that are not construction firms.

(ii) “Small business” does not include a subsidiary or parent company that belongs to a group of firms that the same individuals own or control and that have average aggregate annual gross receipts during the last three years in excess of $1 million for construction firms or $300,000 for firms that are not construction firms.

(C) The proposer’s financial stability and ability to provide funding for the bridge project and obtain, or act as, a surety for the proposer’s performance and financial obligations with respect to the bridge project.

(D) The experience of the proposer and the proposer’s subcontractors in engaging in bridge project activities of a size and scope similar to the bridge project activity that the port proposes.

(E) The terms of the financial arrangement that the proposer accepts or proposes with respect to franchise fees, license fees, lease payments or operating expenses and the proposer’s required rate of return from engaging in the bridge project activity.

(F) The terms that the proposer offers for engaging in the bridge project activity, including:

(i) The amount of proposed tolls and administrative fees;

(ii) Schedules for altering tolls and administrative fees; and

(iii) Any restrictions or conditions on future increases in tolls or administrative fees.

(b) After considering the elements described in paragraph (a) of this subsection in a public hearing, the port shall select a proposal that provides the best overall public value. In determining the best overall public value, the port must find that the selected proposal, compared to other proposals, is likely to:

(A) Reduce the cost of constructing the bridge project;

(B) Accelerate the schedule for completing the bridge project; and

(C) Reduce the financial risk to the port and the public.

(7) Notwithstanding any other provision of this section, the port may use any method to award a contract, agreement, franchise or license that is necessary to comply with the requirements of a grant or other funding source.

(8) Before entering into an agreement under subsection (2) of this section, the port shall engage legal counsel for the purpose of:

(a) Advising the port concerning the legality of specific proposed partnerships;

(b) Advising the port concerning legal procedures and practices that are related to implementing a bridge project in a public-private partnership;

(c) Assisting the port in negotiating agreements and preparing documents related to a public-private partnership;

(d) Advising the port concerning accounting, investment and tax requirements that apply to a bridge project the port undertakes in a public-private partnership; and

(e) Advising the port concerning any relevant federal securities or other laws and related disclosure requirements.

(9) For purposes of complying with applicable state and local land use laws, including statewide planning goals, comprehensive plans, land use regulations, ORS chapters 195, 196, 197, 198, 199, 215, 221, 222 and 227 and any requirement that the Land Conservation and Development Commission imposes, a bridge project is a project of the port and is not a project of any other person or entity.

(10) A bridge project undertaken under ORS 381.205 (Construction, acquisition, maintenance and connection of interstate bridges by counties, cities, towns and ports) to 381.314 (Sale or transfer of Port of Hood River bridge or bridge project) is:

(a) Exempt from ad valorem property taxation; and

(b) A state highway for the purposes of law enforcement and the application of the Oregon Vehicle Code.

(11) ORS 381.270 (Bids for bridge construction), 381.275 (Contracts made in name of authority authorizing work) and 381.280 (Bond required with certain contracts) do not apply to a bridge project that a private entity undertakes.

(12) ORS 381.270 (Bids for bridge construction) does not apply to a bridge that the Port of Hood River constructs, reconstructs or replaces. [2017 c.710 §2]

Note: 184.618 was repealed by section 140, chapter 750, Oregon Laws 2017. The text of 381.310 (Port of Hood River bridge projects) was not amended by enactment of the Legislative Assembly to reflect the repeal. Editorial adjustment of 381.310 (Port of Hood River bridge projects) for the repeal of 184.618 has not been made.

1 Legislative Counsel Committee, CHAPTER 381—Interstate Bridges, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors381.­html (2017) (last ac­cessed Mar. 30, 2018).
 
2 OregonLaws.org contains the con­tents of Volume 21 of the ORS, inserted along­side the per­tin­ent statutes. See the preface to the ORS An­no­ta­tions for more information.
 
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.