HomeMy WebLinkAboutIGA - TSP ODOT
- 1 -
For Recording Stamp Only
INTERGOVERNMENTAL AGREEMENT
Deschutes County Transportation System Plan Update
THIS INTERGOVERNMENTAL AGREEMENT (“Agreement”) is made and
entered into by and between the STATE OF OREGON, acting by and through its
Department of Transportation (“ODOT” or “Agency”), and Deschutes County (“County”
or “Grantee”).
RECITALS
1. The Transportation and Growth Management (“TGM”) Program is a joint
program of ODOT and the Oregon Department of Land Conservation and Development.
2. The TGM Program includes a program of grants for local governments for
planning projects. The objective of these projects is to better integrate transportation and
land use planning and develop new ways to manage growth in order to achieve compact
pedestrian, bicycle, and transit friendly urban development.
3. This TGM Grant (as defined below) is financed with federal Safe,
Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users
(“SAFETEA-LU”) funds. Local funds are used as match for SAFETEA-LU funds.
4. By authority granted in ORS 190.110 and 283.110, state agencies may enter
into agreements with units of local government or other state agencies to perform any
functions and activities that the parties to the agreement or their officers or agents have
the duty or authority to perform.
5. County has been awarded a TGM Grant which is conditional upon the
execution of this Agreement.
6. The parties desire to enter into this Agreement for their mutual benefit.
NOW, THEREFORE, for good and valuable consideration, the receipt and
sufficiency of which is hereby acknowledged, the parties agree as follows:
REVIEWED
______________
LEGAL COUNSEL
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 2 -
SECTION 1. DEFINITIONS
Unless the context requires otherwise, the following terms, when used in this
Agreement, shall have the meanings assigned to them below:
A. “County's Matching Amount” means the amount of matching funds which
County is required to expend to fund the Project.
B. “County's Project Manager” means the individual designated by County as
its project manager for the Project.
C. “Direct Project Costs” means those costs which are directly associated
with the Project. These may include the salaries and benefits of personnel assigned to
the Project and the cost of supplies, postage, travel, and printing. General administrative
costs, capital costs, and overhead are not Direct Project Costs. Any jurisdiction or
metropolitan planning organization that has federally approved indirect cost plans may
treat such indirect costs as Direct Project Costs.
D. “Federally Eligible Costs” means those costs which are Direct Project Costs
of the type listed in Exhibit D incurred by County during the term of this Agreement.
E. “Grant” or “County's Amount” means the total amount of financial
assistance disbursed under this Agreement to County.
F. “ODOT’s Contract Administrator” means the individual designated by
ODOT to be its contract administrator for this Agreement.
G. “Project” means the project described in Exhibit A.
H. “Termination Date” has the meaning set forth in Section 2.A below.
I. “Total Project Costs” means the total amount of money required to
complete the Project.
J. “Work Product” has the meaning set forth in Section 5.J below.
SECTION 2. TERMS OF AGREEMENT
A. Term. This Agreement becomes effective on the date on which all parties
have signed this Agreement and all approvals (if any) required to be obtained by ODOT
have been received. This Agreement terminates on June 30, 2009 (“Termination Date”).
B. County’s Amount. The County’s Amount shall not exceed $100,000.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 3 -
C. County's Matching Amount. The County's Matching Amount is $12,359 or
11% of the Total Project Costs.
SECTION 3. DISBURSEMENTS
A. Subject to submission by County of such documentation of costs and
progress on the Project (including deliverables) as are satisfactory to ODOT, ODOT shall
reimburse County only for Direct Project Costs that are Federally Eligible Costs that
County incurs after the execution of this Agreement up to the County's Amount .
Generally accepted accounting principles and definitions of ORS 294.311 shall be
applied to clearly document verifiable costs that are incurred.
B. County shall present reimbursement requests, cost reports, progress reports,
and deliverables to ODOT’s Contract Administrator no less than every other month.
County shall submit reimbursement requests for 100% of County’s Federally Eligible
Costs, and shall be reimbursed at 89% up to the County’s Amount.
C. ODOT shall make interim payments to County for deliverables identified as
being County’s responsibility in the approved statement of work set out in Exhibit A
within 45 days of satisfactory completion (as determined by ODOT’s Contract
Administrator) of such deliverables.
D. ODOT reserves the right to withhold payment equal to ten percent (10%) of
each disbursement until 45 days after ODOT’s Contract Administrator’s approval of the
completion report described Section 5.L(2), at which time the balance due to County
under this Agreement shall be payable.
E. Within 45 days after the latter of the Termination Date of this Agreement or
County’s compliance with Section 5.L. below, ODOT shall pay to County the balance
due under this Agreement.
F. ODOT shall limit reimbursement of travel expenses in accordance with
current State of Oregon Accounting Manual, General Travel Rules, effective on the date
the expenses are incurred.
SECTION 4. COUNTY’S REPRESENTATIONS, WARRANTIES, AND
CERTIFICATION
A. County represents and warrants to ODOT as follows:
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 4 -
1. It is a municipality duly organized and existing under the laws of the
State of Oregon.
2. It has full legal right and authority to execute and deliver this
Agreement and to observe and perform its duties, obligations, covenants and
agreements hereunder and to undertake and complete the Project.
3. All official action required to be taken to authorize this Agreement
has been taken, adopted and authorized in accordance with applicable state law
and the organizational documents of County.
4. This Agreement has been executed and delivered by an authorized
officer(s) of County and constitutes the legal, valid and binding obligation of
County enforceable against it in accordance with its terms.
5. The authorization, execution and delivery of this Agreement by
County, the observation and performance of its duties, obligations, covenants and
agreements hereunder, and the undertaking and completion of the Project do not
and will not contravene any existing law, rule or regulation or any existing order,
injunction, judgment, or decree of any court or governmental or administrative
agency, authority or person having jurisdiction over it or its property or violate or
breach any provision of any agreement, instrument or indenture by which County
or its property is bound.
6. The statement of work attached to this Agreement as Exhibit A has
been reviewed and approved by the necessary official(s) of County.
B. As federal funds are involved in this Grant, County, by execution of this
Agreement, makes the certifications set forth in Exhibits B and C.
SECTION 5. GENERAL COVENANTS OF COUNTY
A. County shall be responsible for the portion of the Total Project Costs in
excess of the County’s Amount. County shall complete the Project.
B. County shall, in a good and workmanlike manner, perform the work, and
provide the deliverables described in Exhibit A.
C. County shall perform such work described in Exhibit A as an independent
contractor and shall be exclusively responsible for all costs and expenses related to its
employment of individuals to perform such work. County shall also be responsible for
providing for employment-related benefits and deductions that are required by law,
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 5 -
including, but not limited to, federal and state income tax withholdings, unemployment
taxes, workers’ compensation coverage, and contributions to any retirement system.
D. All employers, including County, that employ subject workers as defined in
ORS 656.027, shall comply with ORS 656.017 and shall provide workers’ compensation
insurance coverage for those workers, unless they meet the requirement for an exemption
under ORS 656.126(2). County shall require and ensure that each of its subcontractors
complies with these requirements.
E. County shall be responsible, to the extent permitted by the Oregon Tort
Claims Act, ORS 30.260-30.300, only for the acts, omissions or negligence of its own
officers, employees or agents.
F. County shall not enter into any subcontracts to accomplish any of the work
described in Exhibit A, unless it first obtains written approval from ODOT.
G. County agrees to cooperate with ODOT’s Contract Administrator. At the
request of ODOT’s Contract Administrator, County agrees to:
(1) Meet with the ODOT's Contract Administrator; and
(2) Form a project steering committee (which shall include ODOT’s
Contract Administrator) to oversee the Project.
H. County shall comply with all federal, state and local laws, regulations,
executive orders and ordinances applicable to the work under this Agreement, including,
without limitation, applicable provisions of the Oregon Public Contracting Code.
Without limiting the generality of the foregoing, County expressly agrees to comply with:
(1) Title VI of Civil Rights Act of 1964; (2) Title V and Section 504 of the Rehabilitation
Act of 1973; (3) the Americans with Disabilities Act of 1990 and ORS 659A.142; (4) all
regulations and administrative rules established pursuant to the foregoing laws; and (5)
all other applicable requirements of federal and state civil rights and rehabilitation
statutes, rules and regulations.
I. County shall maintain all fiscal records relating to this Agreement in
accordance with generally accepted accounting principles. In addition, County shall
maintain any other records pertinent to this Agreement in such a manner as to clearly
document County’s performance. County acknowledges and agrees that ODOT, the
Oregon Secretary of State’s Office and the federal government and their duly authorized
representatives shall have access to such fiscal records and other books, documents,
papers, plans, and writings of County that are pertinent to this Agreement to perform
examinations and audits and make copies, excerpts and transcripts.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 6 -
County shall retain and keep accessible all such fiscal records, books, documents,
papers, plans, and writings for a minimum of six (6) years, or such longer period as may
be required by applicable law, following final payment and termination of this
Agreement, or until the conclusion of any audit, controversy or litigation arising out of or
related to this Agreement, whichever date is later.
J. (1) All of County’s work product related to the Project that results from
this Agreement (“Work Product”) is the exclusive property of ODOT. ODOT and
County intend that such Work Product be deemed “work made for hire” of which ODOT
shall be deemed the author. If, for any reason, such Work Product is not deemed “work
made for hire”, County hereby irrevocably assigns to ODOT all of its rights, title, and
interest in and to any and all of the Work Product, whether arising from copyright, patent,
trademark, trade secret, or any other state or federal intellectual property law or doctrine.
County shall execute such further documents and instruments as ODOT may reasonably
request in order to fully vest such rights in ODOT. County forever waives any and all
rights relating to the Work Product, including without limitation, any and all rights
arising under 17 USC §106A or any other rights of identification of authorship or rights
of approval, restriction or limitation on use or subsequent modifications.
(2) ODOT hereby grants to County a royalty free, non-exclusive license to
reproduce any Work Product for distribution upon request to members of the public.
(3) County shall ensure that any work products produced pursuant to this
Agreement include the following statement:
“This project is partially funded by a grant from the Transportation
and Growth Management (TGM) Program, a joint program of the Oregon
Department of Transportation and the Oregon Department of Land
Conservation and Development. This TGM grant is financed, in part, by
federal Safe, Accountable, Flexible, Efficient Transportation Equity Act: A
Legacy for Users (SAFETEA-LU), local government, and State of Oregon
funds.
The contents of this document do not necessarily reflect views or
policies of the State of Oregon.”
(4) The Oregon Department of Land Conservation and Development and
ODOT may each display appropriate products on its “home page”.
K. Unless otherwise specified in Exhibit A, County shall submit all final
products produced in accordance with this Agreement to ODOT’s Contract Administrator
in the following form:
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 7 -
(1) two hard copies; and
(2) in electronic form using generally available word processing or graphics
programs for personal computers via e-mail or on compact diskettes.
L. Within 30 days after the Termination Date, County shall
(1) pay to ODOT County’s Matching Amount less Federally Eligible
Costs previously reported as County’s Matching Amount. ODOT may use
any funds paid to it under this Section 5.L (1) to substitute for an equal
amount of federal SAFETEA-LU funds used for the Project or use such
funds as matching funds; and
(2) provide to ODOT’s Contract Administrator, in a format provided by
ODOT, a completion report. This completion report shall contain:
(a) The permanent location of Project records (which may be subject to audit);
(b) A summary of the Total Project Costs, including a breakdown of those
Project costs that are reimbursable hereunder and those costs which are
being treated by County as County’s Matching Amount;
(c) A list of final deliverables; and
(d) County’s final disbursement request.
SECTION 6. ODOT’S REPRESENTATIONS AND COVENANTS
A. ODOT certifies that, at the time this Agreement is executed, sufficient
funds are authorized and available for expenditure to finance ODOT’s portion of this
Agreement within the appropriation or limitation of its current biennial budget.
B. ODOT represents that the statement of work attached to this Agreement as
Exhibit A has been reviewed and approved by the necessary official(s) of ODOT.
C. ODOT will assign a Contract Administrator for this Agreement who will be
ODOT’s principal contact person regarding administration of this Agreement, including
the monitoring of County’s work and the review and approval of County’s work, billings
and progress reports.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 8 -
SECTION 7. TERMINATION
This Agreement may be terminated by mutual written consent of all parties.
ODOT may terminate this Agreement effective upon delivery of written notice to
County, or at such later date as may be established by ODOT under, but not limited to,
any of the following conditions:
A. County fails to complete work specified in Exhibit A within the time
specified in this Agreement, including any extensions thereof, or fails to perform
any of the provisions of this Agreement and does not correct any such failure
within 10 days of receipt of written notice or the date specified by ODOT in such
written notice.
B. If federal or state laws, regulations or guidelines are modified or
interpreted in such a way that either the work under this Agreement is prohibited
or ODOT is prohibited from paying for such work from the planned funding
source.
C. If ODOT fails to receive funding, appropriations, limitations or other
expenditure authority sufficient to allow ODOT, in the exercise of its reasonable
administrative discretion, to continue to make payments for performance of this
Agreement.
In the case of termination pursuant to A or B above, ODOT shall have any remedy at
law or in equity, including but not limited to termination of any further disbursements
hereunder. Any termination of this Agreement shall not prejudice any right or
obligations accrued to the parties prior to termination.
SECTION 8. GENERAL PROVISIONS
A. Time is of the essence of this Agreement.
B. Except as otherwise expressly provided in this Agreement, any notices to
be given hereunder shall be given in writing by personal delivery, facsimile, or mailing
the same, postage prepaid, to ODOT or County at the address or number set forth on the
signature page of this Agreement, or to such other addresses or numbers as either party
may hereafter indicate pursuant to this Section. Any communication or notice so
addressed and mailed is in effect five (5) days after the date postmarked. Any
communication or notice delivered by facsimile shall be deemed to be given when receipt
of the transmission is generated by the transmitting machine. To be effective against
ODOT, such facsimile transmission must be confirmed by telephone notice to ODOT’s
Contract Administrator. Any communication or notice by personal delivery shall be
deemed to be given when actually delivered.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 9 -
C. ODOT and County are the only parties to this Agreement and are the only
parties entitled to enforce the terms of this Agreement. Nothing in this Agreement gives, is
intended to give, or shall be construed to give or provide any benefit or right not held by or
made generally available to the public, whether directly, indirectly or otherwise, to third
persons unless such third persons are individually identified by name herein and expressly
described as intended beneficiaries of the terms of this Agreement.
D. Sections 5(I), 5(K), 5(L) and 8 of this Agreement and any other provision
which by its terms is intended to survive termination of this Agreement shall survive.
E. This Agreement shall be governed by and construed in accordance with the
laws of the State of Oregon without regard to principles of conflicts of law. Any claim,
action, suit or proceeding (collectively, “Claim”) between ODOT (and/or any other
agency or department of the State of Oregon) and County that arise from or relates to this
Agreement shall be brought and conducted solely and exclusively within the Circuit
Court of Marion County for the State of Oregon; provided, however, if a Claim must be
brought in a federal forum, then it shall be brought and conducted solely and exclusively
within the United States District Court for the District of Oregon. In no event shall this
Section be construed as a waiver by the State of Oregon of any form of defense or
immunity, whether it is sovereign immunity, governmental immunity, immunity based on
the Eleventh Amendment to the Constitution of the United States or otherwise, from any
Claim or from the jurisdiction of any court. County, BY EXECUTION OF THIS
AGREEMENT, HEREBY CONSENTS TO THE IN PERSONAM JURISDICTION OF
SAID COURTS.
F. This Agreement and attached Exhibits (which are by this reference
incorporated herein) constitute the entire agreement between the parties on the subject
matter hereof. There are no understandings, agreements, or representations, oral or
written, not specified herein regarding this Agreement. No modification or change of
terms of this Agreement shall bind either party unless in writing and signed by all parties
and all necessary approvals have been obtained. Budget modifications and adjustments
from the work described in Exhibit A must be processed as an amendment(s) to this
Agreement and the PSK. No waiver or consent shall be effective unless in writing and
signed by the party against whom such waiver or consent is asserted. Such waiver,
consent, modification or change, if made, shall be effective only in the specific instance
and for the specific purpose given. The failure of ODOT to enforce any provision of this
Agreement shall not constitute a waiver by ODOT of that or any other provision.
On June 18, 2003, the Oregon Transportation Commission (“Commission”) approved
Delegation Order No. 2, which authorizes the Director of ODOT to approve and execute
agreements for day-to-day operations when the work is related to a project included in the
Statewide Transportation Improvement Program (“STIP”) or a line item in the biennial
budget approved by the Commission
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 10 -
On September 15, 2006, the Director of the Oregon Department of Transportation approved
Subdelegation Order No. 2, Paragraph 1, in which authority is delegated to the Deputy Director,
Highways; Deputy Director, Central Services and the Chief of Staff, to approve and sign
agreements over $75,000 when the work is related to a project included in the Statewide
Transportation Improvement Program or in other system plans approved by the Oregon
Transportation Commission such as the Oregon Traffic Safety Performance Plan, or in a line
item in the biennial budget approved by the Director. The Director may also delegate to other
Administrators the authority to execute intergovernmental agreements over $75,000 for specific
programs such as transportation safety, growth management and public transit.
County
Deschutes County
DATED this _______ of __________, 2008
ATTEST:
___________________________________
Recording Secretary
BOARD OF COUNTY COMMISSIONERS
___________________________________
DENNIS R. LUKE, CHAIR
___________________________________
TAMMY (BANEY) MELTON, VICE CHAIR
_________________________________
MICHAEL M. DALY, COMMISSIONER
Contact Names:
Peter Russell
Deschutes County
1300 NW Wall St., Suite #200
Bend, OR 97701
Phone: 541-388-6570
Fax: 541-388-4752
E-Mail: peterr@co.deschutes.or.us
ODOT
STATE OF OREGON, by and through
its Department of Transportation
By:
Jerri Bohard, Division Administrator
Transportation Development Division
Date:
ATTORNEY GENERAL'S OFFICE
Approved as to legal sufficiency by the
Attorney General's office.
By: ________________________
(Official's Signature)
Date: ________________________
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 11 -
Devin Hearing, Contract Administrator
Transportation and Growth Management Program
63085 N. Hwy. 97
Bend, OR 97701-5754
Phone: 541.388.6388 Ext 360
Fax: 541-385-0476
E-Mail: Devin.HEARING@odot.state.or.us
- 12 -
EXHIBIT A
Deschutes County
Transportation System Plan Update
STATEMENT OF WORK AND DELIVERY SCHEDULE
Local Agency Project Manager:
Name: Peter Russell
Address: Deschutes County, Planning
Division 117 NW Lafayette,
Bend, Oregon 97701
Phone: (541) 383-6718
Fax: (541) 385-1764
Email: peterr@co.deschutes.or.us
Agency’s Grant Manager
Name: Devin Hearing
Address: ODOT, Program & Planning Unit,
63085 N. Hwy 97,
Bend, OR 97701
Phone: 541-388-6388
Fax: 541-388-6361
Email: Devin.Hearing@odot.state.or.us
A. DEFINITIONS AND ACRONYMS
ADT Average Daily Traffic
Agency/ODOT Oregon Department of Transportation
AWSC All-Way Stop Control
BMPO Bend Metropolitan Planning Organization
BPAC Bicycle and Pedestrian Advisory Committee
CARU Crash Analysis & Reporting Unit
County Deschutes County
DLCD Department of Land Conservation and Development
MPO Metropolitan Planning Organization
NTP Notice to Proceed
PAC Project Advisory Committee
Project Transportation System Plan update for Deschutes County
Project Manager Deschutes County Senior Transportation Planner
Project Team Agency staff, County staff, and other entities involved with the project
RMS Road Management System
RTP Regional Transportation Plan
SC Steering Committee
SOW Statement of Work
TAC Technical Advisory Committee
TAZ Transportation Analysis Zone
TGM Transportation and Growth Management
TPAU ODOT Transportation Planning and Analysis Unit
TPR Transportation Planning Rule
TSP Transportation System Plan
TWSC Two-Way Stop Control
UGB Urban Growth Boundary
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 13 -
B. WORK ORDER CONTRACT (WOC) OVERVIEW and BACKGROUND
1. Background
Since the 1998 Transportation System Plan (TSP) was completed Deschutes County (County)
has witnessed a vast array of changes. When the first TSP began in 1995, Deschutes County had
a population of 94,100 (40,850 in the County and 53,250 within Urban Growth Boundaries
(UGB’s)). In 2010 the Coordinated Population Forecast anticipates the County will have a total
population of 166,572 (59,127 in the County and 107,445 in the UGB’s). That is an increase of
77% in the County’s total population and a 45% increase in the rural population.
In 1998 County had one destination resort. In 2007 that original destination resort has expanded
twice and the County now has five destination resorts. There are three more destination resorts
just across the line in southwest Crook County and Jefferson County has mapped sites for two
potential destination resorts, again just north of the Deschutes County line. The combination of
the destination resorts in Crook County and the growth of Prineville has brought increased
traffic to the Powell Butte Highway and Alfalfa Market Road, two County facilities that never
anticipated such volumes.
The urban areas have also grown. Bend has become a Metropolitan Planning Organization
(MPO) of which County and Oregon Department of Transportation (ODOT) are partners.
Bend is also master planning for Juniper Ridge, the 1,500 acres on Bend’s northeast side that will
impact several County roads. Redmond has designated Urban Area Reserves, including future
rights of way for anticipated roads, in concert with Deschutes County and Bend is beginning the
process with County assistance. Sisters continues to grow and presses for alternate routes
around the community. The County even has Oregon’s newest city, La Pine, within its borders.
A private coach now provides transit service between Bend and La Pine. Public transportation
is becoming a recognized need within the County, particularly between Redmond and Bend and
a Mobility Consortium has formed to analyze the problem at a tri-county scale. As Bend has
begun fixed-route transit service there is now a potential hub for a system linking Sisters,
Redmond, and Prineville together with an expanded transit or paratransit system.
All of this has resulted in the need to update the Deschutes County TSP. County staff from the
Road Department and Planning have already identified several major areas for the TSP update
to address including 19th Street extending from Redmond to Bend to offer a parallel local route
to U.S. 97; access and circulation issues in Terrebonne; safety issues on Powell Butte Highway,
Alfalfa Market Road, and Huntington Road; possibility of using rural roundabouts; improved
circulation on the west side of Redmond between OR 126/Helmholz and U.S. 97/Quarry; a trail
system to provide non-highway links between Sisters-Redmond, Bend-Redmond, and Sisters-
Bend; and finally access and circulation between U.S. 20 and Cline Falls Highway in Tumalo.
Regarding Rural Communities specifically, there are operational, circulation, circulation and
bicycle/pedestrian needs that will need to be addressed in the update for Terrebonne and
Tumalo. There have not been significant changes in the Rural Communities of Alfalfa, Millican,
Brothers, or Hampton so it is expected there will be minimal updating for those locales. As
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 14 -
Sunriver and Black Butte are private roads and bike paths, they will not be addressed in the TSP
update except for where their private roads connect to the County transportation system.
Obviously, the impending TSP assessment will identify other gaps or needs, which will be
incorporated into the TSP update. Similarly, the County has a long history of proactive public
outreach. That tradition will continue with the TSP update through as series of several open
houses and workshops across the County to query local residents for their input.
2. Transportation/Highway System Benefit
The purpose of this Transportation and Growth Management (TGM) Project is to develop an
updated 20-year TSP suitable for adoption by Deschutes County that will:
• Assess the existing transportation system of state and county roads to identify any
current operational, mobility, or safety problems, and need for any revised policy
language.
• Propose modernization projects, system management strategies, or transportation
policies to improve the overall operating conditions on the highway and local arterial
and collector roads.
• Reduce reliance on the auto by assessing the existing bicycle and pedestrian network
for areas outside the Urban Growth Boundaries (UGB’s), assess possible placements
of park and ride lots, identifying gaps and prioritizing remedies of either construction
projects, system management, or policies.
• Comply with the Transportation Planning Rule (TPR), Oregon Administrative Rule
Chapter 660, Division 12.
The TSP update must involve review and analysis of existing and available information,
including work associated with the updates of the Bend, Redmond, and Sisters TSP’s, the
Bend and Redmond UGB expansions, the Bend and Redmond Urban Area Reserve
expansions, and ODOT refinement plans for U.S. 97 and U.S. 20. The review must include
population projections, existing and future traffic volume projections, and County land use
regulations. The TSP Update must include an examination of potential parallel County
arterials or collectors to provide an alternate route to the state highway system.
Project Purpose and Objectives
The purpose of this Project is to:
A. Develop an Updated TSP for Deschutes County that includes a County road component
that reaffirms the current functional classification of County arterials and collectors,
provides reason for changing functional classification of County roads (either upgrading
or downgrading), if warranted, and identifies the general alignment of future County
arterials and collectors,
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 15 -
B. Designate a network of rural bicycle routes and/or shared roadways that cross the County
and connect to the urban bicycle network of Bend, Redmond, and Sisters, establish
policies to implement and maintain the designated rural bicycle network of routes and
shared roadways,
C Prepare a project list of transportation improvements, providing the projects general
location, planning-level costs estimates, priority (high, medium, low) and when needed
(0-5 years, 6-10 years, 11-20 years).
D. Prepare a plan which complies with the TPR with particular adherence paid to the
processes described at 660-012-0015 and 0016 for coordination; 660-012-0020 for
elements; 660-012-0030 for determining needs, 660-012-0035 for evaluating and
selecting alternatives, 660-012-0040 for financing, and 660-012-045 for implementation.
This is not to imply that other sections of the TPR will be ignored.
E. Accomplish the above while following best practices for soliciting public input and
responding to suggestions by the public as well as other local governments and state
agencies.
The goals and objectives of this TGM Project are twofold as listed below. These are
described broadly while the specifics of how they will be achieved are set forth in the Tasks
section.
Goal 1: Provide the widest possible opportunities for public involvement in the
formulation, development, and adoption of the products of this project.
Objective 1 - Establish Project Advisory Committee with representatives from
Deschutes County Community Development and Deschutes
County Road Department and provide ongoing opportunity for
public involvement throughout process.
Objective 2 – Establish a Technical Advisory Committee with representatives
from Deschutes County Community Development Department,
Deschutes County Road Department, ODOT Region 4, ODOT
Transportation Planning and Analysis Unit (TPAU), Department of
Land Conservation and Development (DLCD), and Deschutes
County Bicycle and Pedestrian Advisory Committee (BPAC).
Objective 3 - Provide adequate notices and news updates to interested agencies
and citizens during life of project, utilize the Deschutes County
website for providing updates, seeking comments, posting copies
of work products, etc.
Objective 4 - Provide public workshops during the project as well as briefings to
Deschutes County Planning Commission, Board of County
Commissioners, and interested City Councils and/or City Planning
Commissions for Bend, La Pine, Redmond, and Sisters
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 16 -
Goal 2: Prepare a County transportation network that is consistent with the City of Bend
Urban Reserve Area, City of Redmond Urban Reserve Area, as well as the City of
Sisters TSP and the Bend Metropolitan Planning Organization (MPO) Regional
Transportation Plan (RTP).
Objective 1 - Assess the existing County TSP’s for portions that may require
updating, including but not limited to population forecasts,
expected traffic forecasts, project list for projects already
completed, adequacy of policy language, transportation-land use
policies, funding strategies, etc.
Objective 2 -Assess the existing TSP for consistency with the TSP’s for Bend,
Redmond, and Sisters, and RTP for the Bend Metropolitan
Planning Organization (BMPO) for roadway functional
classifications, bicycling routes and/or trails, future projects, public
transportation, park and ride lots or opportunities for such lots, etc.
Objective 3 - Meet with staff from ODOT Region 4, TPAU, DLCD, and cities of
Bend, BMPO, La Pine, Redmond, and Sisters to identify critical
issues, opportunities, and constraints.
Objective 4 - Prepare a County TSP update that addresses the gaps identified in
the assessment, staff interviews, and public process and that meets
the requirements of the TPR.
Objective 5 - Adopt the updated County TSP into the Deschutes County
Comprehensive Plan.
C. WORK METHODS AND TASKS
1. Expectations about Written and Graphic Deliverables:
All graphic deliverables must be well documented, with project name, a title that corresponds
to task deliverable, draft number, a legend, and the date of preparation. Graphic deliverables
are required in hard copy and any that are prepared electronically must be submitted in
electronic format as well. All electronic copies of illustrative drawings must at a minimum be
in .PDF, .TIF or .JPG format.
All written (text) deliverables must be prepared and submitted using an MS Office program
fully compatible with Agency (e.g. word, excel, access, PowerPoint, etc.) and must include
the project name, a title that refers to the contract deliverable, draft number, subtask number,
and date of preparation. Written deliverables need to be usable and readable in black and
white. Deliverables must also be submitted in hard copy as specified for specific tasks or
upon request
Deliverables (excluding meeting minutes) will be submitted as draft documents and will be
revised for the final Deschutes County TSP update by Local Agency Project Manager per
County and Agency review comments (if any). If no revisions are necessary, the draft will
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 17 -
then be considered final. All subsequent references to Project Manager means the Local
Agency Project Manager, who is the Deschutes County Senior Transportation Planner in the
Planning Division of the County Community Development Department. The Project
Manager will work with other staff of the department as well as County Road Department
staff to update the TSP.
Project Manager shall provide an advance copy of the newsletter to PAC meeting prior to the
public event that follows newsletter publication. The mailing date must be at least 10 days
prior to scheduled public events. County staff shall provide to the Local Agency Project
Manager written comments on the draft newsletter at least 10 working days prior to the
mailing date.
Agency will complete draft reviews within 10 working days of receipt of the drafts.
County shall send one copy of each deliverable to Agency’s Grant Manager according to the
schedule specified in the statement of work (SOW).
At end of Project, County shall submit to Agency a CD with all interim and final deliverables
produced throughout the project.
An Oregon-registered professional engineer (Civil or Traffic) must perform or oversee all
traffic analysis work.
Adoption ready: Final plans and amendments to plans shall be prepared as final policy
statements of the local government and shall not include language such as “it is
recommended…” or “County should…” New and amended code language shall be prepared
as final regulatory statements of local government. Final plan, plan amendments, code, and
code amendments must include all necessary amendments or deletions to existing local plans
or code to avoid conflicts and enable full integration of proposed plan with existing local
documents.
The following text must appear in the final version of all final deliverables:
“This project is partially funded by a grant from the Transportation and Growth
Management (TGM) Program, a joint program of the Oregon Department of
Transportation and the Oregon Department of Land Conservation and Development.
This TGM grant is financed, in part, by federal Safe, Accountable, Flexible, Efficient
Transportation Equity Act: A Legacy for Users (SAFETEA-LU), local government, and
the State of Oregon funds.
The contents of this document do not necessarily reflect views or policies of the State of
Oregon.”
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 18 -
2. Expectations about Meetings
The planning process must include an outreach program to stakeholders, other jurisdictions
and state agencies, and the general public. This outreach will be accomplished via a
combination of small group meetings (5-10 people per meeting) and larger workshops. The
small group meetings will occur with stakeholders, staff from other jurisdictions and
agencies. The larger public workshops will be held initially in Bend, La Pine, Redmond, and
Sisters. If there is insufficient interest (attendance of less than 10 people) in any of these
geographic areas, subsequent meetings may not occur in such locations. The Project
Advisory Committee (PAC) and Technical Advisory Committee (TAC) meetings (which can
be open to the public, if desired), to inform the general public/stakeholders of the planning
process and solicit input and review on transportation/mobility problems, issues and
priorities. Specific timetables are given in the Tasks section of the SOW.
The following is a general description of meeting associated activities, unless otherwise
specified in SOW tasks.
y Project Manager shall coordinate PAC and TAC review of all draft deliverables and shall
be responsible for consolidating all comments on draft deliverables for response. County
shall arrange meeting facilities for all PAC and TAC and public meetings. County shall
distribute agenda and meeting materials to PAC and TAC seven days prior to the
scheduled meetings (unless a timeframe is mutually agreed upon) to allow sufficient time
for review and comment.
y Project Manager or designee if Project Manager is unavailable, shall attend and facilitate
all PAC and TAC and public meetings. County shall prepare appropriate materials such
as agendas, displays and material needed for informed meetings. County shall also
provide summaries for all meetings within two (2) weeks of the meeting.
y Project Manager shall schedule public meetings, distribute meeting notices and materials,
security, room furnishings, refreshments, and other event logistics. Project Manager shall
record attendance at the meetings. Project Manager shall develop the event agenda,
presentation and information materials for distribution, facilitate the event and prepare a
meeting summary.
y Upon request by Agency (or as required in specific tasks), meeting agendas and minutes
shall be provided to Agency for review prior to distribution.
D. PROJECT COMMUNICATION
To the extent possible, all transmittals from County to ODOT must include the TGM File
Code, Intergovernmental Agreement number, and Project name. Formats for the document
control system shall be discussed at the initial meeting between Agency and County.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 19 -
E. TASKS
Task 1: PUBLIC INVOLVEMENT
1.1 Establish Project Committees
County shall initiate the public outreach for the project by soliciting PAC members and
distributing letters or e-mails to notify members of their appointment to PAC for the
Deschutes County TSP Update. The PAC must be no smaller than five (5) members and no
greater than eight (8). The County shall establish a Steering Committee for the Deschutes
County TSP update that must have no fewer than two (2) and no more than three (3)
members.
County shall establish a TAC for the Deschutes County TSP Update. The TAC shall meet
no fewer than six (6) nor more than eighteen (18) times. The Project Manager must lead the
TAC and membership must include, but not be limited to:
y County Project Manager
y County Road Department
y County Finance Department
y ODOT Grant Manager
y ODOT representative from TPAU
y DLCD Region 4 Field Representative
y City of Bend Planning Department
y BMPO
y City of Redmond Planning Department
y City of Sisters Planning Department
County shall establish a Steering Committee (SC) and the SC shall meet no fewer than three
(3) nor more than twelve (12) times. The SC must contain the following:
y County Planning Director
y County Road Department Director
y ODOT Region 4 Program & Planning Unit Manager
The purpose of PAC and TAC meetings (which can be open to the public, if desired), is to
inform the general public/stakeholders of the planning process and solicit input and review
on problems, issues and priorities. The purpose of the Steering Committee is to provide
direction to the TAC on broad conceptual issues and to provide guidance should the TAC be
unable to reach consensus on an issue, problem, or priority. County shall prepare for and
attend all PAC, TAC and public events, which are planned to occur on the same trip.
Meetings are deliverables in the tasks in which they occur.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 20 -
1.2 Project Notice
County shall prepare Project Notice to initiate the public outreach. Project Notice must
include the background description of Project, Project objectives, expected milestones,
committee membership roster and stand-alone Preliminary Project Schedule. Preliminary
Project Schedule shall be recommended by County and approved by Project Manager prior
to finalizing Project Notice. The meeting date, time and location for the first committee
meeting(s) must be stated in the Project Notice for future reference. Subsequent meeting
dates and times will be confirmed by the committees in advance of each meeting.
County shall distribute Project Notice to PAC’s, TAC, and SC.
1.3 Public Notice and Subsequent Mailing List
County shall prepare public notices and press releases for any public meeting and then
develop a mailing list from any attendees or those who contact the County requesting
information on the Deschutes County TSP Update. Mailing List will be used to contact
interested parties about subsequent public workshops, public meetings, or public hearings.
1.4 Public Workshops
County shall hold at kickoff workshops in Bend, La Pine, Redmond, and Sisters, midterm
workshops to show how input, suggestions, and issues raised in kickoff workshop were
incorporated into the TSP update, then a series of workshops on the draft TSP update. The
location of the midterm and draft TSP update workshops will be determined based on
attendance and interest from previous workshops. The total number of workshops will be no
less than three (3) and no more than twelve (12). (While described generally here, the timing
and deliverables of the midterm and final workshops are specified in the appropriate tasks
when they would occur in the TSP Update Process.)
County Task 1 Deliverables:
1.1 Public Notice and Press Release
1.2 Distribute Public Notices and Press Releases
1.3 Compile and Update Mailing List
1.4 Schedule and manage public workshops
1.5 Prepare rosters for PAC, TAC ,and SC
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 21 -
Task 2: REVIEW EXISTING TSP
Objective: Identify, review and summarize existing TSP including but not limited to
population, projects previously completed, changes in policies or standards, functional
classifications, major land use changes, UGBs or urban reserve area boundaries, etc.
Characterize existing conditions in the Deschutes County TSP relying primarily on readily
available information sources and studies, personal interviews, and summarize changes
between the 1998 TSP and current conditions.
2.1 Review and Assess Current TSP
County shall review, assess and determine requirements, elements and components of
existing plan, policies and standards, including the TPR - OAR 660 Division 12, as they
relate to the areas which warrant updating. Actions taken to complete this assessment must
include:
1. Reading current TSP to compare and contrast that with:
y Requirements outlined in ODOT’s 2001 TSP Guidelines.
y Changes in the January 2006 edition of the 1999 “Oregon Highway Plan” for
performance standards for existing and future conditions, access management
standards, functional classifications and/or management goals for state
facilities.
y Changes in the 2003 Highway Design Manual for performance standards for
TSP alternatives and resulting projects for state facilities.
y Changes in the “Oregon Bicycle and Pedestrian Plan” as the 1992 plan is
essentially the bike/ped portion of the current TSP
y Changes in the “Deschutes County Comprehensive Plan” that relate to
transportation and land use.
y Changes, if any, in public or private airports, bike/ped facilities, railroads, or
pipelines in terms of number, location, or operation.
y Completion of road projects listed in the 1998 TSP
y Completion of sidewalks system shown in the 2005 Tumalo Non-Motorized
Transportation Plan
y Completion of sidewalks system shown in the 2005 Terrebonne Non-
Motorized Transportation Plan
2. Interviewing the following:
y County Planning Director and staff and County Road Department Director
and staff for any changes in standards, policies, or facility management goals
for County streets or financing strategies for transportation improvements to
County facilities
y Members of Deschutes County BPAC for assessment of how current plan
addresses bicycle and pedestrian issues and needs.
y Staff from Planning and Public Works Departments for cities of Bend, La
Pine, Redmond, and Sisters as well as BMPO and Bend Metro Park and
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 22 -
Recreation District to identify if current plan addresses transportation issues in
the rural/urban interface.
y ODOT Region 4 Program & Planning Unit staff and DLCD regional field
representative for their assessment of the current plan.
y Commute Options Director for issues pertaining to policies to affect single-
occupant vehicle intercity commuting patterns between cities as well as
between Deschutes, Jefferson and Crook counties.
y ODOT Rail Unit personnel for issues pertaining to railroad crossings in the
County and/or potential reroutes of existing railroad lines
2.2 Prepare Draft Technical Memorandum #1: TSP Assessment
Project Manager after completing tasks identified in 2.1 shall prepare Draft Technical
Memorandum #1, an analysis of existing policies, standards, project lists, etc., and a gap
analysis of which areas need to be updated or revised. While mainly focused on the
County’s road network of arterials and collectors, the gap analysis must include
bicycle/pedestrian, air, rail, and pipelines as applicable. Draft Technical Memorandum #1
must be distributed to the TAC and SC and allow three weeks for review and comment.
2.3 Prepare Final Version of Technical Memorandum #1: TSP Assessment
Project Manager shall revise Technical Memo #1 based upon comments from TAC and SC.
Once the deadline for comments on the draft Technical Memo #1 is reached, the final version
must be done in two weeks.
County Task 2 Deliverables
2.1 Draft Technical Memorandum #1, “TSP Assessment” (Task 2.2)
2.2 Final version of Technical Memorandum #1, “TSP Assessment” (Task 2.3)
TASK 3: REVIEW OF EXISTING TRAFFIC CONDITIONS
Objective: Determine the current traffic volumes on the County transportation system of
collectors, arterials as well as State highways within the County. Determine which
intersections and links are meeting performance standards for the County and ODOT.
Gather data from a variety of sources in sufficient amount and detail to provide an accurate
baseline of current traffic volumes which can then be used to predict future traffic volumes
on County collectors and arterials and State highways within Deschutes County.
3.1 Collect roadway inventory data, traffic volume data from selected rural
intersections, and data for other modes including air and rail.
y Traffic counts will be collected by the County and ODOT as per Task 3.4.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 23 -
y Traffic counts will also be obtained from previous and current projects (US 97
North Corridor, Wickiup Jct, Terrebonne, Lava Butte), ODOT’s Data section
databases, and the County counting database to complete the entire volume data set.
y Obtain 3-5 year segment crash data from ODOT’s Crash Analysis & Reporting Unit
(CARU) for state highways and County arterials and major collectors. Because of
the size of this request, at least two months must be allotted for the production of
this data before it is needed in Task 3.3.
y ODOT TPAU will provide a list (or map) of segments and intersections that the
County needs to provide inventory data for.
y County shall provide either from existing data or from field collection, the
following items for County collectors and arterials. ODOT TPAU will provide the
following items for roads under ODOT jurisdiction using a combination of existing
databases, maps, aerial photos, and video logs.
o Functional classification
o Number of lanes on segments
o Posted speeds
o Bridge conditions
o Intersection control types (stop-control, signal, roundabout, etc)
o Intersection turn prohibitions
o Lane configurations at intersection approaches – number and location of
left, through and right turn lanes, but not including storage bay lengths.
o Lane widths - Will be assumed to be 11 feet on County facilities, but County
shall review databases and report out any wider or narrower widths.
o Shoulder width - Will be assumed to be 2 feet on County facilities.
o Median type/width – County will provide data only on Skyline Ranch Road
as this is the only median location on County facilities.
o Pavement type and condition – County shall provide from its Pavement
Management database.
o Terrain type – County shall provide information based on the classification
scheme of level, rolling (3-4% grades and posted curve speeds of 30-45
mph), and mountainous (6+% grades and posted curve speeds of 25 mph or
less).
o Access points per mile – ODOT TPAU to obtain from County web-based
road mileage Road Management System (RMS) table for County facilities.
o Percent No-Passing Zones – County to provide only for the county arterials:
Cline Falls Hwy, Old Bend-Redmond Hwy, Powell Butte Hwy, Neff-Alfalfa
Market Road, Baker Road, China Hat Road, USFS Road 40/45 (from
construction plans) and Burgess Road.
o Location of Two-Way Stop Control (TWSC) and All-Way Stop Control
(AWSC) intersections and locations of stop signs - County will provide
from sign database to check location of signs to check whether sign
locations are on the arterial/collector road or on the minor cross-road.
y County shall review latest version of County Average Daily Traffic (ADT) volume
table to see if any local roads have more ADT than collector or arterial roadways.
County shall provide, at a minimum, an Excel version of the latest version of the
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 24 -
County ADT volume table. County shall investigate creating a GIS shape file of the
table.
y County shall contact Oregon Department of Aviation to provide, if available,
inventory data on public and private airports in the County in terms of
classification, usage, and planned runway expansions of existing airports.
y County shall contact the Road Department to assess the shoulders on designated
bikeways in terms of width and pavement condition.
y ODOT Rail Unit will provide, if available, inventory data on the railroads regarding
frequency and length of trains operating in the County, classification of railroads,
operating speed, and projected future frequency of trains or double-tracking of
lines.
3.2 Provide information of land use applications that are significant generators of
traffic
y Project Manager shall coordinate with County current planning staff and County
GIS staff to identify any land uses which will generate more than 1,000 average
daily trips. Examples of such land uses would include but not be limited to
destination resorts, Measure 37 and Measure 49 claims, and Sunriver Town Center
redevelopment. Relevant portions of traffic studies related to background traffic,
project traffic, and future traffic with and without proposed project will be
forwarded on to TPAU.
y County GIS staff shall provide map and land use information of Measure 37 claims
in the County.
3.3 Prepare Draft Technical Memorandum #2: Existing Conditions
ODOT TPAU will prepare Technical Memorandum #2: Existing Conditions following
the completion of Tasks 3.1-3.2. The Technical Memorandum #2 must provide 30th
highest hour and average daily traffic volumes, assess whether County arterials and
collectors and State highways within the County are meeting the performance standards
of their respective classifications, and identify locations that have crash rates higher
than similar facilities. Project Manager will receive the Draft Technical Memorandum
#2: Existing Conditions from TPAU and Project Manager will then distribute TM #2 to
the TAC and SC for a review period of four weeks.
y All existing 30th highest hour volumes and average daily traffic volumes and the
analysis of them must be consistent with ODOT’s Analysis Procedure Manual
available at: http://www.oregon.gov/ODOT/TD/TP/TAPM.shtml.
y All analysis must be Highway Capacity Manual 2000-compliant.
y Review the CARU crash data collected in Task 3.1 to identify locations that have a
higher crash rate or severity than similar facilities. Segment crash rates must be
compared to published state crash rates for similar facilities.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 25 -
3.4 Prepare Final Version of Technical Memorandum #2: Existing Conditions
ODOT TPAU will revise Technical Memo #2 after receiving comments from the TAC and
SC. The revision will be done in four weeks after receipt of all comments or the deadline set
in 3.3 for TAC and SC comments has passed, whichever comes first.
County Task 3 Deliverables
3.1. 16-hour manual, turn movement, full federal classification counts at the following
intersections (Task 3.1):
y South Century Drive/Spring River Road
y South Century Drive/Vandevert Road
3-hour manual intersection movement counts from 3-6 p.m. at 15-minute intervals at the
following intersections (Task 3.1):
y Buckhorn Road/Lower Bridge Way
y Lower Bridge Way/43rd
y Northwest Way/Coyner Ave
y SW Helmholtz/Maple Ave
y SW Helmholtz/Coyote Ave
y Edison –Ice Cave Road/Upper Deschutes Road
y Tumalo Road/Hunnel Road
y Smith Rock Way/1st St
y Alfalfa Road/Powell Butte Hwy
y Powell Butte Hwy/Butler Market Road
y Alfalfa-Neff/Hamby Road
y Butler Market Road/Hamby Road
y Rickard Road/Arnold Market Road
y Johnson Road/Tumalo Reservoir Road
48-hour classification road-tube counts at 15-minute intervals at the following intersections
(Task 3.1):
y Camp Polk Road , 0.1 mile south of Sundown Road
y 31st Road, 0.1 mile south of Lower Bridge Way
y Johnson Road, 0.1 mile south of Buck Drive
y Cottonwood Road, 1 mile west of Cottonwood Road interchange
y Lava Lake Road, 0.1 mile north of Three Trappers Road
y Lava Lake Road, 0.1 mile north of Brown Mountain Road
y Cascade Lakes Highway, 0.1 mile of Moore Creek Road
y Cascade Lakes Highway, 0.1 mile south of Wickiup Road
y Burgess Road, 0.1 mile east of South Century Drive
y South Century Drive, 0.1 mile northeast of Burgess Road
y Keefer Road, 0.1 mile north of Upper Deschutes Market Road
3.2 List of any current land use applications that would generate significant amounts of
traffic (Task 3.2)
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 26 -
3.3 Provide GIS maps of Measure 37 and Measure 49 claims (Task 3.2)
3.4 List of shoulders on County bikeways for widths and pavement condition (Task 3.1)
3.5 Prepare public notice and press release for midterm public workshops
3.6 Distribute public notices and press releases for midterm public workshops
3.7 Compile and update mailing list from midterm public workshops
3.8 Schedule and manage midterm public workshop
ODOT Task 3 Deliverables
3.9. 16-hour manual, turn movement, full federal classification counts at the following
intersections (Task 3.1):
y Santiam Highway No. 16/Camp Sherman Road
y Santiam Highway No. 16/Indian Ford Road
y McKenzie Highway No. 15/Camp Polk Road
y McKenzie Highway No. 15/Cloverdale Market Road
y McKenzie Highway No. 15/Cline Falls Highway
y McKenzie Highway No. 15/SW Helmholtz Way
y The Dalles-California Highway No. 4/Odem Avenue
y The Dalles-California Highway No. 4/O’Neil Highway No. 370-Pershall Road
y The Dalles-California Highway No. 4/Cottonwood Road interchange northbound
on/off ramp terminal
y The Dalles-California Highway No. 4/Vandevert Road
y The Dalles-California Highway No. 4/State Park Road
y The Dalles-California Highway No. 4/Paulina Lake Road
y McKenzie-Bend Highway No. 17/Cloverdale Market Road
y McKenzie-Bend Highway No. 17/Cook Avenue-O.B. Riley Road
y Central Oregon Highway No. 7/Powell Butte Hwy
y Central Oregon Highway No. 7/Arnold Market Road-Byram Road
y Central Oregon Highway No. 7/St. Clair Road
y Willamette Highway No. 18/West Odell Road
3-hour manual intersection movement counts from 3-6 p.m. at 15-minute intervals at the
following intersections (Task 3.1):
y McKenzie Highway No. 15/Fryrear Road-Holmes Road
y McKenzie Highway No. 15/Buckhorn Road
y O’Neil Highway No. 370/17th
y McKenzie-Bend Highway No. 17/Fryrear Road
y McKenzie-Bend Highway No. 17/Innes Road
y McKenzie-Bend Highway No. 17/Couch Market Road
y McKenzie-Bend Highway No. 17/Bailey Road
y McKenzie-Bend-Highway No. 17/5th St
y Central Oregon Highway No. 7/Hamby
y Central Oregon Highway No. 7/Dodds Road
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 27 -
48-hour classification road-tube counts at 15-minute intervals at the following intersections
(Task 3.1):
y McKenzie Highway No. 15, 1 mile west of eastern City Limits for City of Sisters
y The Dalles-California Highway No. 4/Cottonwood interchange southbound off ramp
y The Dalles-California Highway No. 4/Cottonwood interchange southbound on ramp
y Century Drive Highway No. 372, 0.1 mile west of Edison-Ice Cave (USFS Road #45)
Road
3.10. Draft Technical Memo #2: Existing Conditions (Task 3.3)
3.11. Final Technical Memo #2: Existing Conditions (Task 3.4)
TASK 4: FUTURE TRAFFIC VOLUME CONDITIONS
Objective: Prepare a traffic forecast for 2030 for County arterial and collectors and State
highways within Deschutes County. Identify links and nodes that will not meet County and
ODOT performance standards in the forecast year.
Objective: TPAU will be the lead on model development work with the Deschutes County and
Region 4 acting in a supporting role in providing and coordinating model data inputs for the
variety of local jurisdictions included in this model expanded version. The general structure of
the model will follow a five-step process consisting of pre-generation, trip generation, trip
distribution, mode choice, and traffic assignment. The structure must adapt the current BMPO
Area model to the rest of the urban areas within the County and the County itself. The model
must be implemented entirely through a series of script files written in the R statistical
programming language, with the exception of traffic assignment, which is carried out in
EMME/2.
Objective: Compile land use information from Deschutes County GIS database, BMPO travel
demand model, and Redmond travel demand model, create a travel demand model for the
County to assess regional impacts of transportation. Participants in these tasks will include
TPAU, Deschutes County, and ODOT’s Region 4 Staff. The outcome of the project will be
travel demand forecasting model for the County that can be used to support the TSP update,
ODOT project analysis, and sets of external tabulations replacing and greatly enhancing those
currently used in both the BMPO and the Redmond models.
4.1 Construct New Transportation Analysis Zones (TAZ)
The purpose of this task is to construct a new TAZ structure for the model area. The structure
must encapsulate the following jurisdictions:
1. BMPO Area
2. City of Redmond
3. City of Sisters
4. City of La Pine
5. Deschutes County
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 28 -
TAZ’s are used as the basic unit of geography upon which all of the travel models are applied.
TAZ’s are imaginary spatial polygons the model area is divided into. Construction of these
polygons adhere to specific constrains, and many model related inputs are collected to this level
of geography. The process to be followed in construction of the area TAZ’s must conform to
guidelines outlined in “Oregon Modeling Improvement Program, Model documentation
Guidelines”.
The BMPO and the City of Redmond currently have developed models. The TAZ structure for
both areas must be retained in the County model. New zones must be constructed for the rest of
the County. Review of these new zones structure is required from County staff.
TPAU will prepare a draft TAZ construction for review by County. County shall provide a set of
non-conflicting comments within two weeks of receipt. TPAU will incorporate County
comments and prepare final TAZ construction.
TPAU Task 4 Deliverables: An ArcGIS / ArcView electronic TAZ map with zone numbers
reflecting Countywide coverage.
The TAZ map on completion will be forwarded to the County/Region 4 for review and/or
discussion with other jurisdictions. Upon completion of the review, a copy of the results will be
returned to TPAU for assessment and implementation if changes are deemed justified by the
modeling team.
County: Provide set of non-conflicting comments to TPAU within three weeks of receipt of
TAZ map (Task 4.1)
4.2 Construct the New Highway Network
TPAU will construct link / node network for the roadways to be modeled in the region. All
roads with a functional classification of minor collector or higher must be included in the coded
highway network, as well as local roads that connect higher level facilities or subareas or that
connect TAZs to the remainder of the network. The model network must cover the following
jurisdiction:
1. BMPO Area
2. City of Redmond
3. City of Sisters
4. City of La Pine
5. Deschutes County
ODOT functional class digital maps must form the basis for this step. New aerial photos (2005
or newer) provided by ODOT must be used to ensure the properness of the data reflected in
ODOT digital maps. Construction of the area’s link/node system and link attribute designation
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 29 -
(speed, capacity, lanes, ..Etcetc.) must conform to the guidelines outlined in “Oregon Modeling
Improvement Program, Model documentation Guidelines”.
The BMPO and the City of Redmond currently have developed models. The link/node structure
for both areas must be retained in the County model. New links/nodes must be constructed for
the rest of the County. Review of this new link structure is required from County staff.
TPAU shall provide the draft basic network to County.
In turn, County shall provide the following data for County arterials and collectors either from
existing files or by field collection. TPAU will provide the following data for roads under ODOT
jurisdiction.
Link attributes
1. Posted speed
2. Number of lanes
3. Directionality (one-way versus two-ways); not needed as County does not have any one-
way links.
4. Vehicle restriction: (modes on links: walk, bike, truck, etc.)
5. Functional class (needs to be consistent with Bend and Redmond)
6. Volumes by direction from County count volume deliverables under Subtasks 3.1 and
3.4.
7. Turn prohibitions where applied
8. Identification of location of control devices by type (signal, stop signs, etc.)
Deliverables
TPAU: An ArcGIS / ArcView electronic link/node map with unique link designation, covering
the full County. The link/node map on completion will forwarded to Deschutes County for
review and/or discussion with other jurisdictions. Upon completion of the review, a copy of the
results will be returned to TPAU for assessment and implementation if changes are deemed
justified by the modeling team.
County: Provide set of non-conflicting comments to TPAU within three weeks of receipt of
link/node map (Task 4.2)
4.3 Construct the Centroids/Centroid-Connections Network
TPAU to construct centroids / centroid-connectors network for the zonal structure described
above in 4.1 The centroids system is where zonal related data is stored, while the centroid-
connectors system represent local roadway, (usually not represented directly in model), where
zonal activities (trips) use to connect to the model link system to interact with other zones.
Review of the centroid connectors per TAZ must be required by Deschutes County and
subsequently by the involved jurisdictions. This is an important task, because local knowledge
of traffic circulation is an important input into what TPAU provides. Improvement of
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 30 -
assignment results can be greatly enhanced with proper assessment of this system. The TAZ
map with TAZ’s related centroids / centroid-connectors when review is completed by County the
map must be returned to TPAU for assessment and implementation if changes are deemed
justified by the modeling team.
ODOT functional class digital maps and the new aerial photos (2005 or newer) provided by
ODOT must be used for this task. Construction of the area’s centroids / centroid-connectors
system must conform to the guidelines outlined in “Oregon Modeling Improvement Program,
Model documentation Guidelines”.
The BMPO and the City of Redmond currently have developed models. The centroids /
centroid-connectors structure for both areas must be retained in the County model. New
centroids / centroid-connectors structure will be constructed for the rest of the County. County
shall review the new centroids / centroid-connectors network within 3 weeks of receipt of
link/node map.
Deliverables
TPAU: An ArcGIS / ArcView electronic TAZ map with TAZ’s related centroids / centroid-
connectors.
County: Provide set of non-conflicting comments to TPAU (Task 4.3)
4.4 Construct the Transit Network
TPAU will construct a digital transit network mirroring existing/planned area wide system (if
applicable). This network must consist of a series of transit lines that overlay the highway
network, plus whatever transit only links.
The transit network coding must be implemented in Emme/2. The transit network must reflect
all of the transit services in use in the BMPO area in 2003. Transit sub-modes must be coded
separately, including walk access and egress, park-n-ride (if they exist) and kiss-n-ride access
and any local service to rail transfer. A walk network must be coded to enable bus transfer in the
downtown area between one-way streets. TPAU will use current BMPO model structure to
provide all the data that describe the transit system and its usage. County shall provide any
information relating to public transit outside of the BMPO area, in particular, routes between
cities and Park and Ride locations. Transit system coding must conform to the guidelines
outlined in “Oregon Modeling Improvement Program, Model documentation Guidelines
TPAU will do all the network coding and utilize the BMPO model to provide the necessary
information.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 31 -
Deliverables
TPAU: Based on the information available from the current BMPO model, TPAU will
incorporate this data into the County model.
County: Provide information on public transit uses outside of the BMPO area.
4.5 – Compile Land Use and Socioeconomic Data
TPAU and County shall jointly compile land use and demographic data at the TAZ level for the
Deschutes County Model. This data is the primary source of input to the travel demand model.
This is, as mentioned, contains TAZ level data on persons, households, and employment in the
region. TPAU will prepare draft 2003 housing and employment data allocated as described
above
The finalized TAZ will be basis for this data collection effort. As to Household totals, TPAU
will use Census 2000 Block geography data to allocate regional households to the TAZ structure.
TPAU will use GIS and aerial photos to access the reasonability of the allocation process.
State of Oregon Employment Department ES202, 2003 numbers for Deschutes County must
form the basis for the base year allocation to TAZ process. This employment data must be
collapsed to the following SIC classes required for model input:
1. Agriculture, forestry (SIC 01 – 09)
2. Mining (SIC 10 – 14)
3. Construction (SIC 15 – 17)
4. Manufacturing (SIC 20 – 39)
5. Transportation, Communication, Public Utilities (SIC 40 – 49)
6. Wholesale Trade (SIC 50 – 51)
7. Retail Trade (SIC 52 – 59)
8. Financial, Insurance, Real Estate (SIC 60 – 67)
9. Service (70-89)
10. Government
TPAU will then geocode the above list to a combination of street and a tax lot layers. Data must
be aggregated by the above category and tagged to the proper area TAZ.
County shall review, edit and correct the 2003 housing and employment data (except for BMPO
and Redmond Model area which will be done by TPAU). Result will then be forwarded to
TPAU.
County shall also provide at the TAZ level the following data:
A- School data:
y School type (Elementary, Middle, and High School) by TAZ
y School enrollment by school type
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 32 -
y School by school-district
B- Number of acres by land use including:
y Residential by TAZ
y Industrial by TAZ
y Park by TAZ
y Total
C- Percent single-family dwelling units by TAZ
To be derived from 2000 Census Summary File 3 (SF3). Other local sources also can be used if
available
County shall identify locations and names of special trip generators, such as shopping centers,
universities/colleges, hospitals, major distribution centers, and major retail outlets, which will
receive special treatment in the generation and distribution model. Due to the unique trip
generation characteristics of these locations, the following data are required for each site:
y Shopping center square footage by TAZ
y College students enrollment and staff totals by TAZ
y Hospital employment, beds, square footage by TAZ
y Distribution centers employment and square footage by TAZ
County shall provide housing and employment estimates for each TAZ for the forecasting year
(2030) and other supporting data as outlined above.
Deliverables
County: Base year (2003) and future year (2030) housing and employment data per TAZ.
Special generators location and all required related information. (Task 4.5)
4.6 – Access Measurement and Other Data
Accessibility is defined as a measure of which activities may be reached from a given location
using a particular transport model. Accessibility is generally a positive concept; that is, the
higher the value attained the better. The purpose of this task is to compile at the TAZ level a set
of local indicators to be utilized in the new model structure.
County shall collect and assemble the data needed for this task. This task will rely on some data
collected in the previous task for completion. (except for BMPO and Redmond Model area)
County shall provide the following base accessibility variables including:
GIS Accessibility Measures @ TAZ Centroid
y 2003 Retail Employment ½ mi
y 2003 Total Employment ½ mi
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 33 -
y 2003 Retail Business Establishments ½ mi
y 2003 Local Street Intersections ½ mi of TAZ centroid
y 2003 Number of employees within 25 minutes of transit travel time (including
walk+wait) (only where applicable)
GIS Accessibility Measures @ Parcel
y Percent of TAZ households (HH) within ¼ mile of a bus stop or ½ mile of a transit
station. (only where applicable)
y Percent of TAZ employment within ¼ mile of a bus stop or ½ mile of a transit station.
(only where applicable)
TAZ and Zone-to-Zone Cost Data
y Parking Cost ($1995), Long Term and Short Term/Avg Length of Stay (only where
applicable)
y Transit Fares (only where applicable)
y Park & Ride Capacities (only where applicable)
County shall provide the following future 2030 accessibility variables including:
GIS Accessibility Measures @ TAZ Centroid
y 2030 Retail Employment ½ mi
y 2030 Total Employment ½ mi
y 2030 Retail Business Establishments ½ mi
y 2030 Local Street Intersections ½ mi of TAZ centroid
y 2030 Number of employees within 25 minutes of transit travel time (including
walk+wait) (only where applicable)
GIS Accessibility Measures @ Parcel
y Percent of TAZ HH within ¼ mile of a bus stop or ½ mile of a transit station. (only
where applicable)
y Percent of TAZ employment within ¼ mile of a bus stop or ½ mile of a transit station.
(only where applicable)
TAZ and Zone-to-Zone Cost Data
y Parking Cost ($1995), Long Term and Short Term/Avg Length of Stay (only where
applicable)
y Transit Fares (only where applicable)
y Park & Ride Capacities (only where applicable)
Deliverables
TPAU: Base year (2003) and future year (2030) tabulations of all the accessibility measures
outlined in the previous step. (Task 4.6)
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 34 -
Task 4.7 – Traffic Counts and Other Validation Data
To produce a comprehensive data set of 2003 daily / hourly counts, to be used in model
development. Traffic volume data will be needed at several phases of the model development
process. Some will be needed for output verification (assignment) and others will be for other
component development (external models). Count data, which yields independent estimates of
travel patterns and growth, will be used to evaluate the ability of the entire traffic forecasting
process to simulate actual travel. The specific locations are provided in Task 3 and its subsets.
TPAU will research ODOT Data Section databanks for recent (2000 – 2006) relevant counts
covering the study area. Collected data will then be adjusted to model base year (2003) and,
also, will be factored to other variations (season, traffic mix… etc.). This effort should try not to
duplicate counts obtained under Task 3.1 unless count duration/format is incompatible.
County shall collect and assemble from own and other local jurisdictions a similar data set.
Collected data must be adjusted, as described above. County shall send TPAU final count data
set for checking, and appending to TPAU’s own.
TPAU will assemble from ODOT traffic databanks all counts (2000 – 2007) relevant to the
model area. Counts will be adjusted as needed. Results will reside in ArcGis for storage.
County shall assemble from all jurisdictions available traffic counts (2000 – 2006) and
coordinate with TPAU on carrying the adjustment process to the collected data, to ensure overall
compatibility. County shall code the collected data to a GIS coverage layer provided by TPAU.
County shall forward final data set to TPAU to be merged with own GIS network layer.
(Region 4/ Deschutes County) Will be responsible for providing 24 hours intersection hose
counts for locations where existing databases do not cover. The 14 external station locations
identified are 14 hours manual classification count and will have a higher priority completion
need, as they are needed for completion of the external model.
If TPAU, Region 4 and County agree further traffic counts are needed, the County shall be
responsible for intersections under County jurisdiction and ODOT will be responsible for
intersections under state jurisdiction unless all parties agree to a different division of labor.
Task 4.8 – Summarize findings in Draft Technical Memo #3: Future Traffic Volume
Conditions
ODOT TPAU will prepare Technical Memorandum #3: Future Traffic Volume Conditions
following the completion of Tasks 4.1-4.7. The Technical Memorandum #3 must provide a
narrative to document the development of the model, future traffic volumes, assess whether
County arterials and collectors and State highways within the County will meet their
performance standards of their respective classifications at the end of the planning horizon
(year 2030), and locations that will require mitigation. The Draft Technical Memorandum
#3: Future Traffic Volume Conditions will be distributed by the Project Manager to the
TAC and SC for a review period of four weeks.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 35 -
y All future volume development and analysis must be consistent with ODOT’s
Analysis Procedure Manual available at:
http://www.oregon.gov/ODOT/TD/TP/TAPM.shtml.
y All analysis must be Highway Capacity Manual 2000-compliant.
Task 4.9 - Prepare Final Version of Technical Memorandum #3: Future Traffic Volume
Conditions
ODOT TPAU will revise Technical Memo #3 after receiving comments from the TAC and SC.
TPAU will revise Technical Memorandum #3 within four weeks of receipt of all comments or
the deadline for TAC and SC comments has passed, whichever comes first.
Task 4.10 – Identification of areas or segments requiring transportation improvements
County and Region 4 staff will review the results from Tasks 1-4.9 and identify locations or
segments that will require improvements due to mobility, operational, safety, or geometric
reasons. The determination will include identification of transportation projects or
document why certain improvements were dismissed. As part of this task County and
Region 4 staff will determine if any additional traffic analysis is required.
Task 4.11- ODOT TPAU will prepare Technical Memorandum #4: Mitigation Alternative
Analysis following the completion of Task 4.10. Technical Memorandum #4 must provide a
narrative to discuss the range of potential alternatives for each identified location or segment of
the document and provide recommendations for each identified location or segment. The
evaluation and selection of TSP alternatives must be consistent with the TPR at 660-012-0035.
The alternatives selection process will also be consistent with the goal of the OHP Major
Improvements Policy 1G of improving or adding to the local road system before widening
existing state facilities or constructing new state facilities. The intent is to identify
improvements to parallel or alternate County roads that could then offload traffic from the state
system, particularly U.S. 97. Draft Technical Memorandum #4: Mitigation Alternative Analysis
must be distributed to the TAC and SC for a review period of four weeks. All analysis will be
consistent with ODOT’s Analysis Procedure Manual available at:
http://www.oregon.gov/ODOT/TD/TP/TAPM.shtml.
Task 4.12. – Prepare Final Version of Technical Memorandum #4: Mitigation Alternative
Analysis
ODOT TPAU will revise Technical Memo #4 after receiving comments from the TAC and SC.
The revision will be done in four weeks after receipt of all comments or the deadline for TAC
and SC comments has passed, whichever comes first. The TAC will then review the identified
locations and/or segments, discuss the recommendations from the Final Technical Memorandum
#4, and document the reason for selecting the specific improvements and why others were
considered but dismissed. County shall present the TAC recommendations to the SC.
Task 4.13 – Identification of funding scenarios
County and Region 4 staff shall prepare an analysis of future County and State funding for the
short-term (2013), medium (2020), and long-term (2030) planning horizons consistent with TPR
at 660-012-0040. Funding strategies to be considered must include a local gas tax, a regional gas
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 36 -
tax, County System Development Charges, increased fees related to transportation services, or
bonding. Analysis must build upon the assumptions described below and future dollars must be
converted to base year (2008) dollars. The analysis must be based upon existing funding and use
an average of the non-restricted funds to develop state funding levels consistent with the 2006
Oregon Transportation Plan investment scenarios.
Level 1. Assumes no additional funding leading to a 40 percent loss in purchasing
power by 2030 stemming from a 3.1% annual inflation rate.
Level 2. Assumes a 3.1% annual inflation rate and new revenues that keep up with
inflation.
Level 3. Assumes a 3.1% annual inflation rate and new revenues that substantially
increase funding, leading to a 40 percent increase in available revenues
over the planning period.
Deliverables
County Task 4 Deliverables
4.1 Prepare list of future transportation projects (Task 4.10)
4.2 Prepare narrative of funding scenarios for future transportation projects (Task 4.13)
ODOT Task 4 Deliverables
4.3 Draft Technical Memo #3: Future Traffic Volume Conditions (Task 4.8)
4.4 Final Technical Memo #3: Future Traffic Volume Conditions (Task 4.9)
4.5 Draft Technical Memo #4: Mitigation Alternative Analysis (Task 4.11)
4.6 Final Technical Memo #4: Mitigation Alternative Analysis (Task 4.12)
TASK 5 TSP UPDATE
County Project Manager, using the data and public input from Tasks 1-4 shall review the current
TSP and update as needed. This includes review of factual data such as lane miles of County
and State facilities, population data, Capital Improvement Project and TSP projects that are
already constructed and need to be removed from the list and replaced with new projects,
revision of “Oregon Highway Plan” references to be current with updated OHP, functional
classification of County and State facilities, and review of County ordinances and policies and
revise as needed.
The draft TSP Update will be submitted to ODOT TPAU and Region 4, DLCD Salem and
Central Oregon staff as well as staff at cities of Bend, La Pine, Redmond, and Sisters for review
and comment for a period of not less than four weeks and no more than six weeks.
Task 5.1 - Prepare Draft TSP Update
County shall utilize Technical Memos #1-#4 as well as other information gleaned from Tasks 1-4
to prepare a draft update of the TSP. County shall hold a public workshop on the draft TSP
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 37 -
Update to solicit public input. County shall distribute draft TSP Update to SC and TAC for
review and comment for a period of not less than four weeks and no more than six weeks.
Elements of the draft TSP Update must include, but not be limited to:
Identify a system of designated current and future arterials and collectors
Identify a system of designated rural bikeways and/or routes
Identify specific, prioritized improvements with planning level cost estimates to the
designated rural bikeways and/or routes to ensure the bike system adequately
accommodates cyclists
Identify a pedestrian network for rural unincorporated communities
Identify specific, prioritized improvements with planning level costs estimates to the
designated pedestrian network for rural unincorporated communities
Identify intersections or roadway segments that will not meet ODOT or County performance
standards
Provide a prioritized list of transportation improvements with planning level cost estimates
that will ensure intersections or roadway segments will meet ODOT or County
performance standards
Detail a financing program to fund the identified transportation improvements
Task 5.2 – Finalize TSP Update
Incorporate comments from SC and TAC and revise the TSP update accordingly.
County shall produce a draft of updated Deschutes County TSP (Task 5.1). County shall
incorporate comments and prepare final draft of updated Deschutes County TSP. (Task 5.2)
ODOT will provide a set of non-conflicting comments to Deschutes County no later than six
weeks after receipt of draft TSP Update.
County Task 5 Deliverables
5.1 Draft copy of Deschutes County TSP Update (Task 5.1)
5.2 Prepare public notice and press release for final public workshop
5.3 Compile and update mailing list from final public workshop
5.4 Schedule and manage final public workshop
5.5 Final copy of Deschutes County TSP Update (Task 5.2)
TASK 6 ADOPTION OF THE TSP UPDATE
County Project Manager shall take the TSP through the comprehensive plan amendment process
as set forth by the Deschutes County code. Including appearances before both the Deschutes
Planning Commission for a recommendation adoption and the Deschutes Board of County
Commissioners for final decision on adoption of the updated TSP.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 38 -
Task 6.1 – Present TSP Update to Deschutes County Planning Commission
Project Manager shall prepare and distribute public notices, staff reports, findings, and
ordinances to present to the Deschutes County Planning Commission first as a workshop and
then in a public hearing. Project Manager shall consult with Agency to decide if staff from either
TPAU or Region 4 need to appear before Planning Commission.
Task 6.2 – Present TSP Update to Deschutes County Board of County Commissioners
County Project Manager to prepare and distribute public notices, staff reports, findings, and
ordinances to present to the Deschutes County Planning Commission first as a workshop and
then in a public hearing. Project Manager shall consult with Agency to decide if staff from either
TPAU or Region 4 need to appear before Deschutes County Board of County Commissioners.
County Deliverables
6.1 Public notices, staff reports, findings, ordinances for work session and subequentsubsequent
public hearing before Deschutes County Planning Commission (Task 6.1)
6.2 Public notices, staff reports, findings, and ordinances for work session followed by public
hearing before Deschutes County Board of County Commissioners. (Task 6.2)
ODOT Deliverables
6.3 Potentially, either Region 4 or TPAU representative be available to answer questions about
development and implementation of Deschutes County land use and transportation model at
Deschutes County Planning Commission workshop and subsequent public hearing .
(County and ODOT to decide at least two weeks before workshops and/or public hearings if
Region 4 or TPAU representative will need to attend.) (Task 6)
6.4 Potentially, either Region 4 or TPAU representative be available to answer questions about
development and implementation of Deschutes County land use and transportation model at
Deschutes County Board of County Commissioners work session and subsequent public
hearing. (County and ODOT to decide at least two weeks prior to work sessions and/or
public hearings if Region 4 or TPAU representative will need to attend.) (Task 6)
- 39 -
F. SCHEDULE
TABLE 1:
DELIVERABLE SUMMARY AND SCHEDULE
Task
Number Task Deliverable Timeline
1 Public Involvement
1.1 Establish Project Committees y Establish PAC
y Establish TAC
y Establish SC
Month 1
1.2 Prepare Project Notice to
committees y Project Notice Month 1
1.3 Prepare Public Notice; Begin
Mailing List
y Public Notice
y Press Release
y Mailing List
Month 2
(ongoing for
mailing list)
1.4 Public Workshops
y Schedule Public
Workshops
y Hold Public
Workshops
Months 3, 9,
and 15
2 Review Existing TSP
2.1 Review & Assess Current TSP
y Interviews with staff
from identified
County, City, and
other agencies or
organizations
Months 1-3
2.2 Summarize findings y Draft TM #1: TSP
Assessment Month 4
2.3 Send TM #1 for comments &
revise accordingly
y Final TM #1: TSP
Assessment Month 5
3 Review of Existing Traffic Conditions
3.1 Traffic counts y Traffic count sheets
& reports Months 3-6
3.2 Review land use applications y GIS map Months 3-6
3.3 Summarize findings y Draft TM #2:
Existing Conditions Month 6
3.4 Send TM #2 for comments &
revise accordingly
y Final TM #2:
Existing Conditions Month 7
4 Future Traffic Volume Conditions
4.1 Construct TAZ’s
y GIS map with
TAZ’s
y Comments memo
Months 5-8
4.2 Add road network to TAZ’s
y GIS map with road
network
y Comments memo
Months 8-9
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 40 -
Task
Number Task Deliverable Timeline
4.3 Add centroids-connectors to
TAZ’s
y GIS map with
centroids &
connectors
y Comments memo
Months 8-9
4.4 Add transit network to TAZ’s y GIS map with transit
links Months 8-9
4.5 Compile land use & demographic
data
y Housing &
employment data for
2003 & 2030
y List any special
generators
Months 8-10
4.6 Measure accessibility
y Table of
accessibility
measures for 2003 &
2030
Month 10
4.7 Traffic count & validation data
y ODOT traffic counts
2000-2006
y Deschutes County
traffic counts 2000-
2006
y Hose counts as
needed for external
stations
Months 7-10
4.8 Summarize findings
y Draft TM #3:
Future Traffic
Volumes
Months 10-13
4.9 Send TM #3 for comments and
revise accordingly
y Final TM #3: Future
Traffic Volumes Months 13-14
4.10
Identify areas or segments
needing transportation
improvements
y Narrative in portions
of TM #3 Months 13-14
4.11 Determine improvements to
specific areas or segments
y Draft TM #4:
Mitigation
Alternative Analysis
Months 13-14
4.12 Send TM #4 for comments and
revise accordingly
y Final TM #4:
Mitigation
Alternatives
Analysis
Months 13-14
4.13 Funding scenarios y Narrative in portions
of TM #3 Months 13-14
5 Write TSP Update
5.1 Revise and update TSP y Draft TSP Update Months 12-15
5.2 Send Draft TSP for comments y Final TSP Update Months 15-16
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 41 -
Task
Number Task Deliverable Timeline
and revise accordingly
6 Deschutes County Adoption of TSP Update
6.1 Present to Des Co Planning
Commission
y Public notices
y Staff report
y Prepare ordinances
Months 15-17
6.2 Present to Des Co Board of
County Commissioners
y Public Notices
y Staff Report
y Prepare Ordinances
Months 17-18
Task Match Budgeted
Reimbursement
Amount
1 – Public Involvement $ 1,525 $ 11,550
2 – Review Existing TSP $ 1,525 $ 8,400
3 – Review of Existing Traffic Conditions $ 350 $ 4,250
4 – Future Traffic Volume Conditions $ 2,850 $ 31,300
5 – TSP Update $ 2,759 $ 25,300
6 – Adoption of the TSP Update $ 3,350 $ 19,200
Subtotal $ 12,359 $100,000
Project Total
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
Rev. 5/10/2000 AGR.FEDCERT
- 42 -
EXHIBIT B (Local Agency or State Agency)
CONTRACTOR CERTIFICATION
Contractor certifies by signing this contract that Contractor has not:
(a) Employed or retained for a commission, percentage, brokerage, contingency fee or other consideration, any firm
or person (other than a bona fide employee working solely for me or the above consultant) to solicit or secure this
contract,
(b) agreed, as an express or implied condition for obtaining this contract, to employ or retain the services of any firm
or person in connection with carrying out the contract, or
(c) paid or agreed to pay, to any firm, organization or person (other than a bona fide employee working solely for me
or the above consultant), any fee, contribution, donation or consideration of any kind for or in connection with,
procuring or carrying out the contract, except as here expressly stated (if any):
Contractor further acknowledges that this certificate is to be furnished to the Federal Highway Administration, and is subject
to applicable State and Federal laws, both criminal and civil.
AGENCY OFFICIAL CERTIFICATION (ODOT)
Department official likewise certifies by signing this contract that Contractor or his/her representative has not been required
directly or indirectly as an expression of implied condition in connection with obtaining or carrying out this contract to:
(a) Employ, retain or agree to employ or retain, any firm or person or
(b) pay or agree to pay, to any firm, person or organization, any fee, contribution, donation or consideration of any
kind except as here expressly stated (if any):
Department official further acknowledges this certificate is to be furnished to the Federal Highway Administration, and is
subject to applicable State and Federal laws, both criminal and civil.
EXHIBIT C
Federal Provisions
Oregon Department of Transportation
I. CERTIFICATION OF NONINVOLVEMENT IN ANY DEBARMENT AND SUSPENSION
Contractor certifies by signing this contract that to the best of its knowledge and belief, it and its principals:
1. Are not presently debarred, suspended, proposed for
debarment, declared ineligible or voluntarily
excluded from covered transactions by any Federal
department or agency;
2. Have not within a three-year period preceding this
proposal been convicted of or had a civil judgment
rendered against them for commission of fraud or a
criminal offense in connection with obtaining,
attempting to obtain or performing a public (federal,
state or local) transaction or contract under a public
transaction; violation of federal or state antitrust
statutes or commission of embezzlement, theft,
forgery, bribery falsification or destruction of
records, making false statements or receiving stolen
property;
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
Rev. 5/10/2000 AGR.FEDCERT
- 43 -
3. Are not presently indicted for or otherwise criminally
or civilly charged by a governmental entity
(federal, state or local) with commission of any of
the offenses enumerated in paragraph (1)(b) of this
certification; and
4. Have not within a three-year period preceding this
application/proposal had one or more public
transactions (federal, state or local) terminated for
cause or default.
Where the Contractor is unable to certify to any of the
statements in this certification, such prospective participant
shall attach an explanation to this proposal.
List exceptions. For each exception noted, indicate to whom
the exception applies, initiating agency, and dates of action.
If additional space is required, attach another page with the
following heading: Certification Exceptions continued,
Contract Insert.
EXCEPTIONS:
Exceptions will not necessarily result in denial of award, but
will be considered in determining Contractor responsibility.
Providing false information may result in criminal
prosecution or administrative sanctions.
The Contractor is advised that by signing this contract, the
Contractor is deemed to have signed this certification.
II. INSTRUCTIONS FOR CERTIFICATION REGARDING
DEBARMENT, SUSPENSION, AND OTHER
RESPONSIBILITY MATTERS–PRIMARY COVERED
TRANSACTIONS
1. By signing this contract, the Contractor is providing
the certification set out below.
2. The inability to provide the certification required
below will not necessarily result in denial of
participation in this covered transaction. The
Contractor shall explain why he or she cannot
provide the certification set out below. This
explanation will be considered in connection with
the Oregon Department of Transportation
determination to enter into this transaction. Failure
to furnish an explanation shall disqualify such
person from participation in this transaction.
3. The certification in this clause is a material
representation of fact upon which reliance was
placed when the Department determined to enter
into this transaction. If it is later determined that
the Contractor knowingly rendered an erroneous
certification, in addition to other remedies available
to the Federal Government or the Department may
terminate this transaction for cause of default.
4. The Contractor shall provide immediate written
notice to the Department to whom this proposal is
submitted if at any time the Contractor learns that
its certification was erroneous when submitted or
has become erroneous by reason of changed
circumstances.
5. The terms "covered transaction", "debarred",
"suspended", "ineligible", "lower tier covered
transaction", "participant", "person", "primary
covered transaction", "principal", and "voluntarily
excluded", as used in this clause, have the meanings
set out in the Definitions and Coverage sections of
the rules implementing Executive Order 12549.
You may contact the Department's Program Section
(Tel. (503) 986-3400) to which this proposal is
being submitted for assistance in obtaining a copy
of those regulations.
6. The Contractor agrees by submitting this proposal
that, should the proposed covered transaction be
entered into, it shall not knowingly enter into any
lower tier covered transactions with a person who is
debarred, suspended, declared ineligible or
voluntarily excluded from participation in this
covered transaction, unless authorized by the
Department or agency entering into this transaction.
7. The Contractor further agrees by submitting this
proposal that it will include the Addendum to Form
FHWA-1273 titled, "Appendix B--Certification
Regarding Debarment, Suspension, Ineligibility and
Voluntary Exclusion--Lower Tier Covered
Transactions", provided by the Department entering
into this covered transaction without modification,
in all lower tier covered transactions and in all
solicitations for lower tier covered transactions.
8. A participant in a covered transaction may rely
upon a certification of a prospective participant in a
lower tier covered transaction that it is not
debarred, suspended, ineligible or voluntarily
excluded from the covered transaction, unless it
knows that the certification is erroneous. A
participant may decide the method and frequency
by which it determines the eligibility of its
principals. Each participant may, but is not
required to, check the Nonprocurement List
published by the U. S. General Services
Administration.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
Rev. 5/10/2000 AGR.FEDCERT
- 44 -
9. Nothing contained in the foregoing shall be
construed to require establishment of a system of
records to render in good faith the certification
required by this clause. The knowledge and
information of a participant is not required to
exceed that which is normally possessed by a
prudent person in the ordinary course of business
dealings.
10. Except for transactions authorized under paragraph
6 of these instructions, if a participant in a covered
transaction knowingly enters into a lower tier
covered transaction with a person who is
suspended, debarred, ineligible or voluntarily
excluded from participation in this transaction, in
addition to other remedies available to the Federal
Government or the Department, the Department
may terminate this transaction for cause or default.
III. ADDENDUM TO FORM FHWA-1273, REQUIRED
CONTRACT PROVISIONS
This certification applies to subcontractors, material
suppliers, vendors, and other lower tier participants.
• Appendix B of 49 CFR Part 29 -
Appendix B--Certification Regarding Debarment,
Suspension, Ineligibility, and Voluntary
Exclusion--Lower Tier Covered Transactions
Instructions for Certification
1. By signing and submitting this contract, the
prospective lower tier participant is providing the
certification set out below.
2. The certification in this clause is a material
representation of fact upon which reliance was
placed when this transaction was entered into. If it
is later determined that the prospective lower tier
participant knowingly rendered an erroneous
certification, in addition to other remedies available
to the Federal Government, the department or
agency with which this transaction originated may
pursue available remedies, including suspension
and/or debarment.
3. The prospective lower tier participant shall provide
immediate written notice to the person to
whichwhom this contract is submitted if at any time
the prospective lower tier participant learns that its
certification was erroneous when submitted or has
become erroneous by reason of changed
circumstances.
4. The terms "covered transaction", "debarred",
"suspended", "ineligible", "lower tier covered
transaction", "participant", "person", "primary
covered transaction", "principal", "proposal", and
"voluntarily excluded", as used in this clause, have
the meanings set out in the Definitions and
Coverage sections of rules implementing Executive
Order 12549. You may contact the person to which
this proposal is submitted for assistance in
obtaining a copy of those regulations.
5. The prospective lower tier participant agrees by
submitting this contract that, should the proposed
covered transaction be entered into, it shall not
knowingly enter into any lower tier covered
transaction with a person who is debarred,
suspended, declared ineligible or voluntarily
excluded from participation in this covered
transaction, unless authorized by the department or
agency with which this transaction originated.
6. The prospective lower tier participant further agrees
by submitting this contract that it will include this
clause titled, "Certification Regarding Debarment,
Suspension, Ineligibility and Voluntary
Exclusion--Lower Tier Covered Transaction",
without modification, in all lower tier covered
transactions and in all solicitations for lower tier
covered transactions.
7. A participant in a covered transaction may rely
upon a certification of a prospective participant in a
lower tier covered transaction that it is not
debarred, suspended, ineligible or voluntarily
excluded from the covered transaction, unless it
knows that the certification is erroneous. A
participant may decide the method and frequency
by which it determines the eligibility of its
principals. Each participant may, but is not
required to, check the nonprocurement list.
8. Nothing contained in the foregoing shall be
construed to require establishment of a system of
records to render in good faith the certification
required by this clause. The knowledge and
information of a participant is not required to
exceed that which is normally possessed by a
prudent person in the ordinary course of business
dealings.
9. Except for transactions authorized under paragraph
5 of these instructions, if a participant in a covered
transaction knowingly enters into a lower tier
covered transaction with a person who is
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
Rev. 5/10/2000 AGR.FEDCERT
- 45 -
suspended, debarred, ineligible or voluntarily
excluded from participation in this transaction, in
addition to other remedies available to the Federal
Government, the department or agency with which
this transaction originated may pursue available
remedies, including suspension and/or debarment.
Certification Regarding Debarment, Suspension,
Ineligibility, and Voluntary Exclusion--Lower Tier
Covered Transactions
a. The prospective lower tier participant certifies,
by submission of this proposal, that neither it
nor its principals is presently debarred,
suspended, proposed for debarment, declared
ineligible or voluntarily excluded from
participation in this transaction by any Federal
department or agency.
b. Where the prospective lower tier participant is
unable to certify to any of the statements in this
certification, such prospective participant shall
attach an explanation to this proposal.
IV. EMPLOYMENT
1. Contractor warrants that he has not employed or
retained any company or person, other than a bona
fide employee working solely for Contractor, to
solicit or secure this contract and that he has not
paid or agreed to pay any company or person, other
than a bona fide employee working solely for
Contractors, any fee, commission, percentage,
brokerage fee, gifts or any other consideration
contingent upon or resulting from the award or
making of this contract. For breach or violation of
this warranting, Department shall have the right to
annul this contract without liability or in its
discretion to deduct from the contract price or
consideration or otherwise recover, the full amount
of such fee, commission, percentage, brokerage fee,
gift or contingent fee.
2. Contractor shall not engage, on a full or part-time
basis or other basis, during the period of the
contract, any professional or technical personnel
who are or have been at any time during the period
of this contract, in the employ of Department,
except regularly retired employees, without written
consent of the public employer of such person.
3. Contractor agrees to perform consulting services
with that standard of care, skill and diligence
normally provided by a professional in the
performance of such consulting services on work
similar to that hereunder. Department shall be
entitled to rely on the accuracy, competence, and
completeness of Contractor's services.
V. NONDISCRIMINATION
During the performance of this contract, Contractor, for
himself, his assignees and successors in interest,
hereinafter referred to as Contractor, agrees as follows:
1. Compliance with Regulations. Contractor agrees to
comply with Title VI of the Civil Rights Act of
1964, and Section 162(a) of the Federal-Aid
Highway Act of 1973 and the Civil Rights
Restoration Act of 1987. Contractor shall comply
with the regulations of the Department of
Transportation relative to nondiscrimination in
Federally assisted programs of the Department of
Transportation, Title 49, Code of Federal
Regulations, Part 21, as they may be amended from
time to time (hereinafter referred to as the
Regulations), which are incorporated by reference
and made a part of this contract. Contractor, with
regard to the work performed after award and prior
to completion of the contract work, shall not
discriminate on grounds of race, creed, color, sex or
national origin in the selection and retention of
subcontractors, including procurement of materials
and leases of equipment. Contractor shall not
participate either directly or indirectly in the
discrimination prohibited by Section 21.5 of the
Regulations, including employment practices, when
the contract covers a program set forth in
Appendix B of the Regulations.
2. Solicitation for Subcontractors, including
Procurement of Materials and Equipment. In all
solicitations, either by competitive bidding or
negotiations made by Contractor for work to be
performed under a subcontract, including
procurement of materials and equipment, each
potential subcontractor or supplier shall be notified
by Contractor of Contractor's obligations under this
contract and regulations relative to
nondiscrimination on the grounds of race, creed,
color, sex or national origin.
3. Nondiscrimination in Employment (Title VII of the
1964 Civil Rights Act). During the performance of
this contract, Contractor agrees as follows:
a. Contractor will not discriminate against any
employee or applicant for employment because
of race, creed, color, sex or national origin.
Contractor will take affirmative action to
ensure that applicants are employed, and that
employees are treated during employment,
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
Rev. 5/10/2000 AGR.FEDCERT
- 46 -
without regard to their race, creed, color, sex or
national origin. Such action shall include, but
not be limited to the following: employment,
upgrading, demotion or transfer; recruitment or
recruitment advertising; layoff or termination;
rates of pay or other forms of compensation;
and selection for training, including
apprenticeship. Contractor agrees to post in
conspicuous places, available to employees and
applicants for employment, notice setting forth
the provisions of this nondiscrimination clause.
b. Contractor will, in all solicitations or
advertisements for employees placed by or on
behalf of Contractor, state that all qualified
applicants will receive consideration for
employment without regard to race, creed,
color, sex or national origin.
4. Information and Reports. Contractor will provide
all information and reports required by the
Regulations or orders and instructions issued
pursuant thereto, and will permit access to his
books, records, accounts, other sources of
information, and his facilities as may be determined
by Department or FHWA as appropriate, and shall
set forth what efforts he has made to obtain the
information.
5. Sanctions for Noncompliance. In the event of
Contractor's noncompliance with the
nondiscrimination provisions of the contract,
Department shall impose such agreement sanctions
as it or the FHWA may determine to be
appropriate, including, but not limited to:
a. Withholding of payments to Contractor under
the agreement until Contractor complies; and/or
b. Cancellation, termination or suspension of the
agreement in whole or in part.
6. Incorporation of Provisions. Contractor will
include the provisions of paragraphs 1 through 6 of
this section in every subcontract, including
procurement of materials and leases of equipment,
unless exempt from Regulations, orders or
instructions issued pursuant thereto. Contractor
shall take such action with respect to any
subcontractor or procurement as Department or
FHWA may direct as a means of enforcing such
provisions, including sanctions for noncompliance;
provided, however, that in the event Contractor
becomes involved in or is threatened with litigation
with a subcontractor or supplier as a result of such
direction, Department may, at its option, enter into such
litigation to protect the interests of Department, and, in
addition, Contractor may request Department to enter
into such litigation to protect the interests of the State of
Oregon.
VI. DISADVANTAGED BUSINESS
ENTERPRISE (DBE) POLICY
In accordance with Title 49, Code of Federal
Regulations, Part 26, Contractor shall agree to abide by
and take all necessary and reasonable steps to comply
with the following statement:
DBE POLICY STATEMENT
DBE Policy. It is the policy of the United States
Department of Transportation (USDOT) to practice
nondiscrimination on the basis of race, color, sex
and/or national origin in the award and administration
of USDOT assist contracts. Consequently, the DBE
requirements of 49 CFR 26 apply to this contract.
Required Statement For USDOT Financial
Assistance Agreement. If as a condition of assistance
the Agency has submitted and the US Department of
Transportation has approved a Disadvantaged Business
Enterprise Affirmative Action Program which the
Agency agrees to carry out, this affirmative action
program is incorporated into the financial assistance
agreement by reference.
DBE Obligations. The Oregon Department of
Transportation (ODOT) and its contractor agree to
ensure that Disadvantaged Business Enterprises as
defined in 49 CFR 26 have the opportunity to
participate in the performance of contracts and
subcontracts financed in whole or in part with Federal
funds. In this regard, Contractor shall take all
necessary and reasonable steps in accordance with
49 CFR 26 to ensure that Disadvantaged Business
Enterprises have the opportunity to compete for and
perform contracts. Neither ODOT nor its contractors
shall discriminate on the basis of race, color, national
origin or sex in the award and performance of
federally-assisted contracts. The contractor shall carry
out applicable requirements of 49 CFR Part 26 in the
award and administration of such contracts. Failure by
the contractor to carry out these requirements is a
material breach of this contract, which may result in
the termination of this contract or such other remedy as
ODOT deems appropriate.
The DBE Policy Statement and Obligations shall be
included in all subcontracts entered into under this
contract.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
Rev. 5/10/2000 AGR.FEDCERT
- 47 -
Records and Reports. Contractor shall provide
monthly documentation to Department that it is
subcontracting with or purchasing materials from the
DBEs identified to meet contract goals. Contractor
shall notify Department and obtain its written approval
before replacing a DBE or making any change in the
DBE participation listed. If a DBE is unable to fulfill
the original obligation to the contract, Contractor must
demonstrate to Department the Affirmative Action
steps taken to replace the DBE with another DBE.
Failure to do so will result in withholding payment on
those items. The monthly documentation will not be
required after the DBE goal commitment is satisfactory
to Department.
Any DBE participation attained after the DBE goal has
been satisfied should be reported to the Departments.
DBE Definition. Only firms DBE certified
by the State of Oregon, Department of Consumer &
Business Services, Office of Minority, Women &
Emerging Small Business, may be utilized to satisfy
this obligation.
CONTRACTOR'S DBE CONTRACT GOAL
DBE GOAL 0 %
By signing this contract, Contractor assures that good
faith efforts have been made to meet the goal for the
DBE participation specified in the Request for
Proposal/Qualification for this project as required by
ORS 200.045, and 49 CFR 26.53 and 49 CFR, Part 26,
Appendix A.
VII. LOBBYING
The Contractor certifies, by signing this agreement to
the best of his or her knowledge and belief, that:
1. No Federal appropriated funds have been paid or
will be paid, by or on behalf of the undersigned, to
any person for influencing or attempting to
influence an officer or employee of any Federal
agency, a Member of Congress, an officer or
employee of Congress or an employee of a Member
of Congress in connection with the awarding of any
Federal contract, the making of any Federal grant,
the making of any Federal loan, the entering into of
any cooperative agreement, and the extension,
continuation, renewal, amendment or modification
of any Federal contract, grant, loan or cooperative
agreement.
2. If any funds other than Federal appropriated funds
have been paid or will be paid to any person for
influencing or attempting to influence an officer or
employee of any Federal agency, a Member of
Congress, an officer or employee of Congress or an
employee of a Member of Congress in connection
with this agreement, the undersigned shall complete
and submit Standard Form-LLL, "Disclosure Form
to Report Lobbying", in accordance with its
instructions.
This certification is a material representation of fact
upon which reliance was placed when this transaction
was made or entered into. Submission of this
certification is a prerequisite for making or entering
into this transaction imposed by Section 1352, Title 31,
U. S. Code. Any person who fails to file the required
certification shall be subject to a civil penalty of not
less than $10,000 and not more than $100,000 for each
such failure.
The Contractor also agrees by signing this agreement
that he or she shall require that the language of this
certification be included in all lower tier
subagreements, which exceed $100,000 and that all
such subrecipients shall certify and disclose
accordingly.
FOR INQUIRY CONCERNING ODOT’S
DBE PROGRAM REQUIREMENT
CONTACT OFFICE OF CIVIL RIGHTS
AT (503)986-4354.
TGM Grant Agreement No. 24807
TGM File Code 4B-07
EA # TGM8LA67
- 48 -