Att. A.1 RFP# 73000-00008899 35790 Sample WOC .docm

DOCM document 169 KB Posted

Attached to
Tillamook County TSP - Planning
Solicitation number
S-73000-00008899
Issued by
Tillamook County, Oregon

About this file

This document is an Attachment A.1 - Sample Statement of Work related to a Request for Proposals for the Tillamook County Transportation System Plan (TTSP) project. The Oregon Department of Transportation (ODOT) is contracting with a consultant to develop a transportation system plan for the unincorporated communities of Tillamook County, including all trails, bike paths, and roads within the participating communities, and interconnectivity with incorporated cities. The project will document transportation needs, policies, and goals for each of these communities, with the desired outcome of the plan serving as the transportation element of the County's comprehensive plan. The document outlines the tasks, deliverables, and schedule for the project, which include project management, public involvement, background review, evaluation of existing and forecasted system conditions, development and evaluation of solutions, drafting the TTSP, and the adoption process.

The document specifies the compensation method as either Cost-Plus-Fixed-Fee (CPFF), Fixed Price, Time and Materials with Not-To-Exceed (T&M), or Price Per Unit. It also includes provisions for contingency tasks that ODOT may authorize the consultant to perform, as well as requirements for subcontractors, key personnel, and other contractual terms. Funding for the project will come from a combination of state and federal sources, and the TTSP must comply with relevant transportation planning regulations and guidelines.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Form C004-B122723

Attachment A.1 Sample Statement of Work SOLICITATION NOTE: This Attachment contains a Sample Statement of Work. Consultant shall use the Statement of Work (“SOW”) as a baseline document to develop a proposed Statement of Work which shall identify all Work and Services described in the Mini-RFP and shall address all design considerations and requirements described for the Project. Consultant shall add sufficient detail to Tasks and Deliverables that are included in the Services and omit any not needed for the Project. Certain items may be marked “to be determined” (“TBD”) and will be part of the negotiation process with the Consultant.

Once finalized and approved by ODOT, that document will become the Statement of Work for the WOC for the Project.

STATEMENT of WORK and DELIVERY SCHEDULE for WOC # TBD under PA # TBD Project Name Tillamook County TSP

Name:

Address:

Phone:

Fax:

Email:

Agency’s Project Manager (“APM”) for the WOC [Enter name of APM for the WOC. The APM is responsible for the day-to-day oversight and review of Consultant Services/Deliverables. The APM may or may not also be named as the WOC Administrator.]

______@odot.oregon.gov

Address:

Fax:

Email:

Consultant’s Project Manager (“PM”) for the WOC

______@_____.com

Email:

Agency’s Contract Administrator for the WOC [The ODOT individual responsible for administration of the WOC must be identified.]

Email:

Alternate Contact for Consultant [this information is optional]

Agency may change the APM designation, Agency’s address for invoicing (Section H.5 of this SOW), or both by promptly sending written notice (email notice acceptable) to Consultant, with a copy to ODOT Procurement Office. Changes to Agency's Contract Administrator for this WOC must be done by amendment. Any changes to Consultant’s PM must be approved in writing (email acceptable) by Agency. Consultant shall provide written notice (email acceptable) to Agency of any changes to Consultant’s other contacts for this WOC.

A. PROJECT DESCRIPTION and OVERVIEW of SERVICES Agency is contracting with Consultant for Services in connection with the following public improvement project (the “Project”):

Agency is contracting with Consultant for Services in connection with the following public improvement Tillamook County Transportation System Plan (“TTSP”) (the “Project”):

The Project will develop a transportation system plan outside of the urban growth boundary, including the unincorporated communities of Falcon Cove, Neah Kah Nie, Watseco, Cape Meares, Oceanside, Netarts, Tierra Del Mar, Pacific City, Woods, Neskowin, Blaine, Beaver, Cloverdale and Hebo (“Participating Communities”), to include all trails, bike paths and roads located within the Participating Communities of Tillamook County including interconnectivity with incorporated cities (the “Project Area”). The Project must document transportation needs, policies, and goals for each of these communities. The desired Project outcome is for this planning document to serve as the transportation element of County’s comprehensive plan per OAR 660-012-0000.

Phases of Services Reserved

Agency Responsibilities Agency commits to:

· Develop and execute an Intergovernmental Agreement with County

· Develop, launch, and maintain a public website for the TTSP Project

· Provide a link between the TTSP public website and ODOT, County and Participating Communities’ websites

· Provide ODOT Region 2 Guidelines for Addressing Title VI/Environmental Justice in Transportation Planning to Consultant and County

· Provide Agency’s traffic team contact information for reviews (see Task 3)

· Provide comments on Draft Technical Memos within two weeks of submittal of draft

· Facilitate the request of Geographic Information Systems (“GIS”) data from Tillamook County as needed (see Task 4.1)

· Provide access to Regional Integrated Transportation Information System (“RITIS”) (see Task 4.1)

· Develop and host an online open house to be posted on the Project Website, which will include an interactive tool, create a survey to solicit input on goals, objectives, and issues, concerns, and preferences for each of the Participating Communities (see Task 4.5). Note: Development and hosting of Project Website is to be TBD.

· Provide funding forecasts for ODOT funding sources

· Review the funding evaluation presented in Technical Memo (“TM”) #9

· Review the draft TTSP in coordination with County and provide one combined set of comments to Consultant (see Task 6.4)

County Requirements County commits to:

· Develop and execute an Intergovernmental Agreement with Agency

· Provide comments on Draft Technical Memos within two weeks of submittal of draft

· Coordinate with each unincorporated community within the Participating Communities to provide the following information (if available) in GIS format within one (1) month of NTP (see Task 4.1):

· Tax lot parcels with County assessor’s data

· Locations of schools, parks, libraries, and other key public areas

· Locations of key shopping areas and other key locations as identified by Participating Communities’ staff

· Aerial Photography

· Parcel zoning

· Comprehensive Plan designations

· Street-view files for all County roadways

· Street centerlines

· Existing off-street trails

· Pavement Conditions

· Street, shoulder, and right-of-way widths (as available)

· Jurisdiction of roadways within the Project Area

· Roadway traffic volume and speed data

· Location of transit stops and routes

· Bridges (including conditions and restrictions)

· Rail lines, crossing locations, and crossing controls

· Air facilities

· Water facilities

· Goal 5 resources and setbacks

· Topography

· Lifeline routes

· Tourist Routes and Congestion Points

· Tsunami evacuation routes and congregation areas

· Pipeline facilities

· Known configuration or maneuvering problems (Participating Communities to provide, qualitative)

· Sidewalk presence and condition and also buffer presence and type

· Coordinate with Agency to assist Consultant to identify expected land development within the Urban Growth Boundary (“UGB”) and planned UGB expansion areas

· Review the draft TTSP in coordination with Agency and provide one combined set of comments to Consultant (see Task 6.4)

· Schedule a Community Event, provide notification to the media, provide an ADA accessible meeting room (or coordinate an online platform for the event), and distribute public information on its website and through a press release (see Task 6.10)

· To schedule, notify and conduct the Planning Commission public hearing.

· Provide notice to Department of Land Conservation and Development ("DLCD") at a minimum of 35 days prior to the first scheduled hearing

· Provide updates to DLCD and Agency on any significant revisions to the TTSP

· Review and adopt the final implementing ordinances concurrently with the TTSP

ACRONYMS & DEFINITIONS

ADA- American Disability Act
OTC- Oregon Transportation Commission
Agency – Oregon Dept. of Transportation
PA – Price Agreement
APM – Agency’s Project Manager for WOC
PAC-Planning Advisory Committee
BLTS- Bicycle Level of Traffic Stress
PIC- Principal In Charge
BOC – Breakdown of Costs
PIP- Public Involvement Project

CE- Community Event

CIP- Capital Improvement Plan
PL- Pedestrian Level
CPFF – Cost Plus Fixed Fee
PLTS- Pedestrian Level of Traffic Stress

PM – Consultant’s Project Manager for WOC

DBE – Disadvantaged Business Enterprise
PMT- Project Management Team
DLCD- Department of Land Conservation and Development
PSIS- Public Involvement Strategy
EJ- Environmental Justice
SOW – Statement of Work
EJEO- Environmental Justice Executive Order
STTP- Statewide Transportation Improvement Project
FP – Fixed Price
T&M – Time and Materials
HCM- Highway Capacity Manual
TAC- Technical Advisory Committee
HDM - Highway Design Manual
TM- Technical Memo
LOS- Level of Service
TPAU- Transportation Planning Analysis Unit
NTE – Not to Exceed
TSP- Transportation System Plan
NTP – Notice to Proceed
TTSP- Tillamook Transportation System Plan
OH- Online Open House
UGB- Urban Growth Boundary
ODOT – Oregon Department of Transportation
WOC – Work Order Contract

ORS – Oregon Revised Statute

B. STANDARDS and GENERAL REQUIREMENTS

1. Standards The standards, manuals, directives and other guidance applicable to Professional Services and Related Services are referenced below or available on Agency’s webpages linked below and are incorporated by this reference with the same force and effect as though fully set forth herein.

The standards, manuals, directives and other guidance listed below or available on Agency’s webpages are not exhaustive and may not include all applicable standards for a given Project. Consultant shall be responsible for determining all applicable practices and standards to be used in performing Professional Services and Related Services. Consultant shall inform and demonstrate to Agency if standards, directives or practices required by Agency in performance of the Services are insufficient, in conflict with applicable standards, or otherwise create a problem for the design. Should the requirements of any reference, standard, manual or policy referenced in the PA or WOC conflict with another, Consultant shall, in writing, request Agency to resolve the conflict.

Unless otherwise specified in a given task, the most current version of applicable standards, manuals, directives and other procedural guidance shall apply. Unless otherwise specified, the system of measurement and language used in all deliverables must be English.

a. Planning, Survey, Preliminary Engineering and Design Manuals, Standards and Guidance:

· Technical Manuals - alphabetical list (https://www.oregon.gov/ODOT/Engineering/Pages/Manuals.aspx)

· Planning Guidance and Resources (https://www.oregon.gov/ODOT/Planning/Pages/Guidance.aspx)

· Planning Analysis (https://www.oregon.gov/ODOT/Planning/Pages/Technical-Tools.aspx)

· ODOT Forms Library (https://www.oregon.gov/ODOT/Forms/Pages/default.aspx)

· ODOT’s Analysis Procedures Manual Version 2

· ADA Compliance – Assessment, Design, Inspection. When the Services under this WOC include assessment or design (or both) for curb ramps, sidewalks or pedestrian-activated signals (new, modifications or upgrades), Consultant shall:

a. Use ODOT standards to assess and ensure Project compliance with the Americans with Disabilities Act of 1990 and Section 504 of the Rehabilitation Act of 1973, as amended (collectively “ADA”), including ensuring that all sidewalks, curb ramps, and pedestrian-activated signals meet current ODOT Highway Design Manual standards; and

b. Follow ODOT’s processes for design, modification, upgrade, or construction of sidewalks, curb ramps, and pedestrian-activated signals, including using the ODOT Highway Design Manual, ODOT Design Exception process, ODOT Standard Drawings, ODOT Construction Specifications, providing a temporary pedestrian accessible route plan and current ODOT Curb Ramp Inspection form.

When the Services under this WOC include inspection of curb ramps, sidewalks or pedestrian-activated signals (new, modifications or upgrades), all such inspections shall include inspection for compliance with the standards and requirements in a. and b. above. Inspections must be performed by ODOT certified inspectors (which must include certified environmental inspectors when appropriate). In addition, at Project completion, Consultant shall complete the applicable ramp-specific ODOT Curb Ramp Inspection Form734-5020(A-G) for each curb ramp constructed, modified, upgraded, or improved as part of the Project. Each completed form must be submitted electronically by clicking the “Submit by E-mail” button on the form (and cc APM). The forms are documentation required to show that each curb ramp meets ODOT standards and is ADA compliant. ODOT’s fillable Curb Ramp Inspection Forms and instructions are available at the following address: https://www.oregon.gov/ODOT/Engineering/Pages/Accessibility.aspx

Above references to curb ramps, sidewalks or pedestrian-activated signals also include, when applicable, shared use paths, transit stops, park-and-rides and on-street parking.

b. Website or Web Content Development and Maintenance Standards Consultant shall perform all required web-related Services in conformance with the ODOT Web Standards (available at: https://www.oregon.gov/ODOT/Pages/Web-Toolkit.aspx), which is incorporated into this PA with the same force and effect as though fully set forth herein. ODOT shall have ownership and control of Work Products developed by Consultant as set forth in the terms and conditions of the PA, Part II, Section 7 - Ownership of Work Product.

c. ODOT Communications Standards For any Consultant tasks that require communications functions on behalf of Agency, Consultant shall comply with the ODOT Communications Standards (available at: https://www.oregon.gov/ODOT/Pages/Web-Toolkit.aspx) which is incorporated into this WOC with the same force and effect as though fully set forth herein.

2. Reserved

3. Software Requirements In addition to the software requirements set forth in the PA, the following shall apply to this WOC:

· Basecamp Use of ODOT provided Basecamp software is required for this Project.

· ARCGIS. Use to develop maps and shapefiles

· Microsoft teams or Zoom, easy to use video conferencing software. Alternates can be discussed.

4. Professional Licenses, Registrations and Qualifications

Consultant must have a transportation engineer or planner not involved in this “Project” provide independent review of “All technical calculations.” Consultant is responsible for quality control and quality assurance.

5. General Requirements

· Consultant Quality Plan (“CQP”) for Professional Services and Related Services. A CQP must be approved and on file with Agency before design and related Services may be provided under the WOC. The CQP must be consistent with requirements of Agency’s “Consultant Quality Plan Guidance” available on the Quality Plans and Guides webpage at: https://www.oregon.gov/odot/ProjectDel/Pages/Quality-Guides.aspx.

Consultant shall ensure quality assurance and quality control is performed in conformance with the approved CQP on all Services and deliverables provided under the WOC. Consultant shall submit an updated CQP for approval if there are changes to Consultant’s quality management processes or organizational structure from what is in the approved CQP during the term of the WOC.

· Electronic Documents, Digital Seal and Signature. Consultant shall use ODOT’s APM email for electronic submittal and receipt of files as necessary for the Project, unless otherwise agreed upon. All final documents identified in ORS 671.025, 671.379, 672.020(2), 672.025(2), 672.028(2) and 672.605, as applicable, must bear the digital seal and signature of the Oregon registered professional under whose supervision and control they were prepared. Documents must be submitted in the format specified in the WOC for each deliverable and must comply with OAR 804-030, OAR 806-010, OAR 809-050 and OAR 820-025 requirements, as applicable, for digital seal and signature capable of independent verification, final and draft documents, modifications to designs, and dual stamping of documents.

· Safety Equipment. Consultant shall provide and use all safety equipment including (but not limited to) hard hats, safety vests and clothing if required by State and federal regulations and ODOT policies and procedures for the Services under the WOC.

· Personnel, Materials, and Equipment. Consultant shall provide competent personnel and shall furnish all supplies, equipment, tools, and incidentals required to accomplish the work. All equipment and tools must be in good operating condition and shall be kept in proper adjustment throughout the duration of the WOC. All materials and supplies must be of good quality and suitable for the assigned work.

· Access to ODOT Right-Of-Way. Consultant shall notify and coordinate with Agency District Manager, or Assistant District Manager, having jurisdiction over the Project area at least 48 hours in advance of needing to be on-site. Consultant shall not begin on-site work until approval is received from the district. Consultant shall reschedule the on-site work if requested by the district.

Oregon Department of Transportation Region 2, Area 1 350 W Marine Dr, Astoria, OR 97103 Area Manager – Bill Jablonski

· State-Owned Assets. All State-owned assets, if any, in Consultant’s possession must be promptly returned to Agency when the Services are complete, when the WOC is terminated, or when requested by Agency, whichever occurs first.

· Legal Services and Fees. If Consultant uses legal services to support the Consultant’s performance of any Services under this WOC, that is a decision within the Consultant’s discretion; however, no charges for Consultant legal counsel or for legal services shall be charged to Agency as a subconsultant cost or other cost and any such costs or charges shall be paid for by the Consultant at the Consultant’s sole expense and at no cost to the Agency.

C. REVIEW, COMMENT and SCHEDULE OVERVIEW

· Consultant shall coordinate with Agency staff as necessary and shall revise draft deliverables to incorporate Agency draft review comments.

· Consultant shall return the revised deliverables to Agency staff, with Agency comments incorporated, within 2 weeks of Consultant’s receipt of Agency’s comments, unless a different timeframe is specified for specific tasks or otherwise agreed to in writing by Agency.

D. FORMAT REQUIREMENTS

· Consultant shall submit draft deliverables in electronic format via email (and hard copy if requested).

· Consultant shall also submit all graphic files accompanying reports separately in .jpg or .tif formats unless specified differently by Agency.

· Each draft and final text-based or spreadsheet-based deliverable shall be provided in MS Office file formats (i.e., MS Word, Excel, etc.) and must be fully compatible with version used by Agency.

· All documents (outreach materials and technical memos) must be digitally accessible per state, federal standards.

· Consultants shall furnish written and electronic documentation for all assumptions, data, calculations, and results. This includes paper and computer files (i.e., spreadsheets and analysis software files).

· Additional format requirements may be listed with specific tasks/deliverables in the SOW or in the PA.

E. TASKS, DELIVERABLES and SCHEDULE Unless the WOC is terminated or suspended, Consultant shall complete all tasks and provide all deliverables (collectively, the “Services”) included in this WOC and in accordance with the performance requirements and delivery schedules included in this WOC. For purposes of standardization, the task numbering in this SOW may be non-sequential. Unless otherwise stated in a specific task or deliverable, “up to” in this SOW will be as determined or approved by APM if the quantity requires less than the specified maximum to meet the Project need.

The delivery schedule is listed under each task. All the tasks and deliverables listed within this SOW must be completed within the delivery timeframes detailed in this Contract.

TASK 1: Project Management Consultant shall provide on-going project management and contract administration throughout the Project. Consultant shall lead, manage, and monitor the progress of Consultant’s work towards completion of the tasks described in this SOW.

1.1 Project Administration – Establish Project Management Team and Project Protocols Consultant shall establish a Project Management Team (“PMT”) comprised of Consultant Project Manager (“PM”), a representative from Agency’s traffic team, Agency’s Project Manager (“APM”), and two representatives from County, acting as the respective Participating Communities' County Project Manager. Consultant shall provide a PMT Roster to APM in coordination with County for review and approval.

Note: A Technical Advisory Committee (“TAC”), consisting of representatives from ODOT Region 2 Traffic, ODOT Region 2 Roadway, Planning, Transportation Planning Analysis Unit ("TPAU"), and Active Transportation and four County representatives will be formed to provide oversight and guidance on technical analyses' methodologies and results to maintain consistency between and within jurisdictions as well as maintain compliance with State and regional plans and regulations. As appropriate, members of the TAC will participate in PMT Meetings and will serve as reviewers for the Technical Memoranda.

Consultant shall develop Project protocols, which must be used as the quality assurance/quality control process for all work products and deliverables. Consultant shall review all Project deliverables with a final review conducted by Consultant’s Principal in Charge (“PIC”). Consultant shall ensure all technical calculations are reviewed internally by Consultant’s transportation engineer or planner who is not involved in the Project prior to submittal to Agency for review by the TAC.

1.2 Develop and Maintain Project Management Website

Consultant shall use Agency-provided Basecamp software for use in developing a Project Management Website. Consultant shall maintain the Project Management Website throughout the Project. The Project Management Website must serve as the primary platform for .Consultant’s submittal, review, tracking, and discussion regarding Project deliverables.

1.3 Project Kick-Off Meeting

Consultant shall schedule, participate in and lead 1 virtual Kick-Off Meeting for up to 1.5 hours to include PMT and TAC members. Consultant shall develop an agenda and draft Project schedule for APM approval in advance of the Kick-Off Meeting. The Kick-Off Meeting must include review of Project scope, draft Project schedule, and provide PMT and TAC members an opportunity to share major issues and priorities for the Project. Consultant shall prepare XX Project Schedule updates as requested by APM.

1.4 Prepare Project Branding Template for Deliverables

Consultant shall develop draft and final Project branding, including a Project logo and style guide to be used for all documents and deliverables, including TM, Reports, and PowerPoint presentations. The style guide must be reflective of individual Participating Communities as well as the whole TTSP and include fonts and color selections for all documents prepared, including TM, reports, and PowerPoint presentations. Consultant shall submit all draft Project branding to PMT for review and approval.

1.5 Monthly PMT Calls

Consultant shall schedule, facilitate, lead, participate in and prepare agendas for monthly coordination calls with PMT. Monthly coordination calls must include updates on Project progress, solicit feedback from PMT, provide direction on upcoming deliverables, and discuss key Project milestones.

1.6 Prepare Monthly Progress Reports

Consultant shall prepare monthly progress reports documenting work completed by the PMT. Monthly progress reports must be submitted with Project invoices and must be included in the materials provided for PMT calls.

TASK 1: Deliverables and Schedule:

Consultant shall:

1.1.1Establish PMT Roster; emailed to APM for review and approval within 2 weeks of NTP
1.1.2Develop Project Protocols; emailed to APM for review and approval within 4 weeks of NTP
1.2Develop Project Management Website within one month of NTP and provide ongoing maintenance and file management on Basecamp Platform
1.3.1Prepare agenda, draft Project schedule, and Project Kick-Off Meeting within 4 weeks of NTP; additional Project Schedule updates to be submitted upon request by APM
1.3.2Attend Project Kick-Off Meeting within 5 weeks of NTP
1.3.3Provide Kick-Off meeting notes to APM for review and approval within 5 business days following the Kick-Off meeting
1.4.1Provide draft Project logo and style guide for TM, Reports, and PowerPoint presentations to PMT for review and approval within 4 weeks of NTP
1.4.2Provide final Project logo and style guide within 6 weeks of NTP
1.5.1Participate in up to 20 coordination calls and provide agendas 3 business days in advance to APM for approval
1.5.2Provide discussion summaries after each call to APM within 5 business days following call
1.6Submit Monthly Progress Reports with invoices

TASK 2: Public Involvement Program Consultant shall establish a Public Involvement Program (“PIP”) to gain input through the duration of Project development at key milestones.

2.1 PMT Meeting #1

Consultant shall schedule, facilitate and prepare an agenda for PMT Meeting #1 (PMT#1) to be conducted via Microsoft Teams (or other approved virtual software) for up to 2 hours in length. Consultant shall ensure the PMT#1 addresses a proposed outline for the Public and Stakeholder Involvement Strategy (“PSIS”) (see Task 2.2 below) to ensure the PSIS accurately addresses the needs of the Project. Consultant shall prepare draft meeting notes and distribute them to the PMT for review and approval. Consultant shall prepare final meeting notes based on PMT edits. Up to 3 members of Consultant team are approved to attend.

2.2 Public and Stakeholder Involvement Strategy (“PSIS”) – Technical Memorandum #1 Consultant shall develop a PSIS with input from PMT. Consultant shall ensure the PSIS includes strategies for key community contacts, advertising community events, distributing work products, methods to gather community input, community workshop format and joint Planning Commission/ Council work sessions.

Consultant shall ensure PSIS incorporates key messaging, key stakeholders, communications protocols, and branding standards and the content captured in the final PMT#1 meeting notes.

Consultant shall document the PSIS in draft TM #1 ("TM#1") for review and input from County, Participating Communities and Agency. TM #1 must include an overview of strategies that broadly apply to all Participating Communities and a section detailing individual messaging, stakeholders, and protocols. Consultant shall ensure PSIS guides the overall strategy for Project outreach and identifies specific strategies and outreach points for each of the fourteen Participating Communities.

Consultant shall provide outreach needs and reporting requirements consistent with the Title II, Federal Title VI Program and Environmental Justice Executive Order (“EJEO”) provisions to ensure full and fair participation by all potentially affected community members in the decision-making process, including the potential to participate in the Planning Advisory Committee (“PAC”), and other community outreach events. Consultant’s outreach must include disabled, low-income, limited English proficiency, minority, or other underserved groups within the census area.

Consultant shall perform demographic analysis using U.S. Census data (at the smallest scale possible, e.g., Census Tract or Block Group) and input from the Participating Communities and other service providers to identify Title VI and Environmental Justice (“EJ”) populations in the Project Area. Consultant shall develop and follow outreach and reporting protocols to meet EJEO requirements and directives and to ensure full and fair participation by all potentially affected community members in the decision-making process. Consultant shall ensure Title VI and EJ analysis and documentation is consistent with the ODOT Region 2 Guidelines for Addressing Title VI/Environmental Justice in Transportation Planning. Consultant shall ensure PSIS clarifies roles and responsibilities for the Participating Communities and Consultant staff as approved by Agency and County.

Consultant shall prepare final TM#1 after receipt of input from County, Participating Communities and Agency.

C.2.3 Translation Assistance [Contingency Task, see Section F] If authorized by Agency, Consultant shall provide translation assistance. Specific task language and deliverables will be negotiated with Consultant and incorporated into the final SOW.

2.4 Establish Planning Advisory Committee

Consultant shall coordinate with County and Agency to develop a Planning Advisory Committee ("PAC") roster. Consultant shall coordinate with County and Agency to obtain contact information for prospective PAC members. Consultant shall be responsible for contacting and inviting prospective PAC members to participate in the PAC. The PAC must consist of one representative from each of the following:

· Bureau of Land Management

· Oregon Department of Forestry

· County Board of Commissioners

· County Planning Commission

· School District Representative

· Emergency service provider

· Transit service provider

· Oregon Department of Transportation

· Department of Land Conservation and Development

· Oregon Department of State Lands

· Bicycle/Pedestrian Interest Groups

· Tourist Industry Representatives

· Title VI / Transportation-disadvantaged representative

· Citizens-at-large

· Community Advisory Committees representatives (one representative from each)

2.5 Targeted Outreach to EJ/Title VI Communities

Consultant shall prepare a public handout documenting Project process (“Fact Sheet”) and translated into Spanish for public outreach (“Focus Events”). Consultant shall provide a written summary of each public outreach event in the public handout for Focus Events.

Consultant shall conduct 3 Focus Events (on 2 separate days) to share Project information with Title VI/EJ communities. Consultant shall conduct Focus Events using any two of the following methods:

· having a presence at the Tillamook Transit Center,

· riding the bus to conduct intercept surveys,

· meeting with a Hispanic council to conduct interviews,

· tabling at community events such as farmers markets, or

· meeting with social service providers.

TASK 2: Deliverables and Schedule:

Consultant shall:

2.1.1Schedule, facilitate and prepare an agenda for PMT#1 for review and approval by PMT 3 business days prior the PMT#1 meeting.
2.1.2Prepare and submit PMT#1 meeting notes to APM within 5 business days followingmeeting
2.2.1Submit draft TM#1 electronically to APM within 1 month following PMT#1
2.2.2Submit final TM#1 electronically to APM within 1 week of receiving comments
C2.3[Contingency Task] Provide Translation Assistance upon request of Agency
2.4.1Submit PAC Roster, electronically to APM within 5 weeks of PMT#1
2.5.1Conduct 3 Focus Events (dates and times to be determined)
2.5.2Submit Fact Sheet electronically to APM 5 days prior to Focus Events
2.5.3Submit written summary for 3 EJ/Title VI Focus Events electronically to APM within 3 weeks following Focus Events

TASK 3: Background Plans and Policy Review Consultant shall conduct an overview of existing plans and polices related to the Project. Consultant shall focus on establishing the goals and objectives the TTSP should advance and select the appropriate metrics to evaluate policies and improvements. Consultant shall submit all technical documents to Agency’s traffic team and APM, for reviewed and edits.

3.1 Background Plan & Policy Review

Consultant shall obtain from Agency, County and Participating Communities, as applicable, plans and policies relevant to the Project and review necessary background documents online. The review must include but is not limited to the following:

· Oregon Highway Plan (and subsequent amendments) (1999)

· Oregon Bicycle and Pedestrian Plan (2016)

· Oregon Public Transportation Plan (2018)

· Oregon State Rail Freight Plan (2014)

· Oregon Freight Plan (2017)

· Oregon Transportation Plan (2023)

· Transportation Planning Rules [Oregon Administrative Rules (“OAR”) 660-012-000 – 660-012-0920]

· Statewide Transportation Improvement Program (STIP)

· Oregon Aviation Plan (2018)

· Oregon Transportation Safety Action Plan (2016)

· Statewide Transportation Strategy: A 2050 Vision for Greenhouse Gas Emissions Reduction (2013)

· ODOT Analysis Procedures Manual (2020)

· ODOT Blueprint for Urban Design (2020)

· Oregon TSP Guidelines (2020)

· Access Management Rules (OAR 734-051-1020 – 734-051-7010)

· Oregon Resilience Plan (2013)

· Tillamook County Transportation System Plan (2005)

· City of Tillamook Transportation System Plan (2019)

· Nehalem Bay Transportation System Plan (2023)

· Local Capital Improvement Plans (“CIP”)

· Local Comprehensive Plans

· US 101 Condition Report (2005)

· Oregon Coast Bike Route Plan

· Salmonberry Trail Plan

· Oregon Coast Trail Info

· Tillamook County’s Seismic Resiliency for Bridges Priorities (November of 2017)

3.2 Plan review summary – Technical Memorandum #2

Consultant shall highlight key Project improvement goals, policies, growth assumptions, and regulatory provisions from the documents listed under Task 3.1. Consultant shall use findings and relevancy statements to identify and distinguish regional issues, as they relate to the goals of the regional transportation plan and identify how relevant documents relate specifically to the unique goals of the local TTSP.

Consultant shall prepare a draft TM#2 summarizing the documents and other information reviewed in Task 3.1 for PMT's review and edits. PMT will return draft TM#2 to Consultant with edits and comments within 2 weeks of receiving draft memo. Consultant shall incorporate PMT's edits into a final TM#2 consisting of an overview of the regional plans and a separate appendix detailing the plans.

3.3 Regulatory Review – Technical Memorandum #3

Consultant shall review and identify policy and regulatory gaps in each of County’s Local Comprehensive Plans and Development Codes that need to be updated to bring them into compliance with the Oregon Transportation Plan and the Transportation Planning Rules. Consultant shall review the policies anticipated to be included in the updated TTSP and ensure roadway classifications are compatible with both County and federal classifications and that policies exist to protect the function of roadway facilities and promote alternate modes of transportation (transit, bicycling and walking) and land uses. Consultant shall use findings from this review to develop implementing regulations in Task 6.4.

Consultant shall provide a draft Technical Memorandum #3 (TM#3) detailing the Regulatory Review to PMT for review and comments. PMT will return draft TM#3 to Consultant with edits and comments within 2 weeks of receiving draft memo. Consultant shall prepare a final TM#3 with specific policy and regulatory gaps identified as appropriate.

3.4 PMT Meeting #2

Consultant shall organize, attend, and lead a Microsoft Teams PMT Meeting #2 (PMT#2) of at least 1.5 hours in length for review of TM#2 and TM#3. Consultant shall facilitate this meeting to allow the PMT and appropriate PAC and TAC members to provide feedback on the information documented in both TM#2 and TM#3. PMT#2 must include discussion around policies proposed to be included in the TTSP. Consultant shall prepare draft meeting notes and distribute them to PMT. Up to 4 members of Consultant’s team are approved to attend.

3.5 PAC Meeting #1 – Draft Goals and Objectives

Consultant shall organize, attend, and lead a Microsoft Teams PAC Meeting #1 (PAC#1) of up to 2 hours in length. Consultant shall develop a draft PAC agenda and protocols for discussion, which must include an overview of TM#2 and TM#3 with a focus on goals and objectives from the perspective of PAC members. Consultant shall ensure PAC#1 includes a group discussion on regional goals and policies, followed by break out discussions focused on the goals and objectives. Up to 5 members of Consultant’s team are approved to attend.

3.6 Goals, Objectives and Criteria – Technical Memorandum #4.

Consultant shall prepare a draft and final Technical Memorandum #4 (TM#4) identifying goals, objectives and evaluation criteria that establish the framework for developing the TTSP. Consultant shall draft goals and objectives developed under this task based on TM#2 and TM#3 (Tasks 3.2 and 3.3) and incorporate discussions from the PAC, and PMT, including discussions and review of existing transportation goals and policies in the TTSP or Comprehensive Plan. (Review of the existing goals and policies will provide the basis for potential amendments to the goals and policies to be prepared as part of Implementing Ordinances in Task 6.4.)

Consultant shall draft goals and objectives consistent with the Transportation Planning Rules, County’s Comprehensive Plan and relevant ODOT transportation policies. Consultant shall include draft criteria that provides fair distribution of benefits and impacts of transportation projects and programs to reflect Title VI and EJ Program objectives.

Consultant shall provide a draft TM#4 identifying the goals, objectives and criteria to PMT for review and comments. PMT will return draft TM#4 to Consultant with edits and comments within 2 weeks of receiving draft memo. Consultant shall prepare a final TM#4 incorporating feedback from PMT.

TASK 3: Deliverables and Schedule:

Consultant shall:

3.1Complete Background Plan & Policy Review for County within 7 weeks of Kick-Off Meeting
3.2.1Prepare draft TM#2 and submit electronically to APM within 7 weeks of Kick-Off Meeting
3.2.2Submit final TM#2 electronically to APM within 1 week of receiving comments
3.3.1Prepare and submit Draft TM #3 electronically to APM within 7 weeks of Kick-Off Meeting
3.3.2Submit final TM # 2 electronically to APM within 1 week of receiving comments
3.4.1Organize and attend PMT#2 (date and time to be determined)
3.4.2Prepare and submit PMT#2 meeting notes
3.5.1Organize, attend and prepare agenda for PAC#1 (date and time to be determined)
3.6.1Prepare draft TM#4 and submit electronically to APM within 3 weeks of PAC#1 and PAC#2
3.6.2Submit final TM#4 electronically to APM within 1 week of receipt of comments

TASK 4: Existing and Forecasted System Conditions Consultant's conditions analysis must focus on understanding the existing and future needs of the transportation system within each Participating Community within County and ODOT Region 2.

4.1 Evaluate Existing Conditions – Technical Memorandum #5

Consultant shall conduct an existing transportation system conditions analysis to determine existing conditions, problems, and deficiencies for all modes of travel (within the Project Area). Traffic analysis must follow methods in the Highway Capacity Manual ("HCM") 7th edition published by the Transportation Research Board ("TRB") or as approved by Agency. All traffic analysis software programs used must follow HCM 7th edition procedures. Consultant shall ensure signalized intersection volume capacity (“v/c”) be computed manually unless software-calculated. Consultant’s existing transportation system analysis methodology must be approved by ODOT Traffic and TPAU prior to any analysis within Technical Memorandum #5 (TM#5).

Consultant shall:

· Prior to beginning the Existing Conditions analysis, develop a methodology for developing traffic volume at identified Project Area locations which must be approved by Agency, prior to beginning the existing conditions analysis with locations to be determined. Consultant’s TM#5 must include a review of available data sources and a methodology for adjusting available data as necessary to represent peak conditions within the Project Area.

· Evaluate count data and analyze Level of Service (“LOS”) and v/c ratio for 30th-highest hour conditions.

· Consultant shall obtain access to RITIS through Agency and pull data for use in further describing operational characteristics on major corridors by analyzing variations in travel speeds and travel times during peak and non-peak travel periods.

· Screen the street network for crash trends by analyzing the most recent 5 years of available and complete crash data for all arterial and collector roadways in the Participating Communities. Analysis must include calculation of critical crash rates and excess proportion of specific crash types at all Project Area intersections as outlined in Chapter 4 of ODOT’s Analysis Procedures Manual. Top 10% ODOT Safety Priority Index System (“SPIS”) sites must be identified. The crash analysis at the top 10% SPIS locations must identify any crash patterns and suggest potential countermeasures.

· Review ODOT’s State Highway Crash Rate Tables and identify highway segments experiencing crash rates greater than the statewide average for similar facilities.

· Give special consideration to potential causes of problems at locations with high bicycle/pedestrian crash frequencies and locations that are identified as bicycle/pedestrian crash risk factors as defined in National Cooperative Highway Research Program (“NCHRP”) 893.

· Evaluate crash trends in the Participating Communities and identify low-cost systemic safety measures that could be considered to reduce fatal and serious injury crashes.

· Assess existing driveway and intersection spacing on the following highways: US101, OR131, OR18, OR6, OR22, OR130, and OR53 by comparing an aerial photo inventory to access spacing standards and validate with a windshield survey or ODOT Digital Video Log as needed.

· Review funding revenue information provided by each Participating Community to determine the average transportation funding sources and expenditures in each Participating Community over the past five years. Consultant’s analysis must identify both flexible and restricted funds and their usage. Expenditures must be converted to Base Year (2024) dollars.

· Review pedestrian facilities and volumes (collected as part of the PM peak hour traffic counts at Project Area intersections) to determine existing system gaps and key pedestrian volume locations.

· Analyze bicycle and pedestrian operations for all collector and arterial roadways in the Project Area with the Qualitative Assessment and the BLTS/PLTS shown in ODOT’s Analysis Procedure Manual v2 Addendum G.

· Review established tsunami evacuation routes and congregation areas.

· Review the tsunami/earthquake sufficiency ratings of the local bridges, tsunami inundation maps, and other relevant existing data.

· Determine the vulnerability of existing routes, and any other gaps or deficiencies.

· Review truck routes and identify truck percentages at Project Area intersections. Highway 101 north of Tillamook is a Reduction Review Route, and Highways 6 and 18 are Oregon Highway Plan Freight Routes.

· Review heavy rail facilities and identify volume and schedule.

· Document pedestrian and bicycle deficiencies on collector and arterial roadways.

Consultant shall use an Oregon-registered professional engineer (civil or traffic) to perform or oversee all traffic analysis Services. Consultant shall obtain all required data license agreements.

Consultant shall document the results system conditions analysis in draft TM#5 in accordance with the ODOT approved transportation system analysis methodology and ODOT's Analysis Procedures Manual, version 2. Consultant shall submit draft TM#5 for review and approval by Agency and County including the appropriate TAC members and the Participating Communities (comments are due within 2 weeks of submittal of draft TM#5).

Consultant shall incorporate the information listed below, as available and provided by County, to be incorporated into the draft TTSP Update (see Task 6):

· Tax lot parcels with County assessor’s data

· Locations of schools, parks, libraries, and other key public areas

· Locations of key shopping areas and other key locations as identified by Participating Communities staff

· Aerial Photography

· Parcel zoning

· Comprehensive Plan designations

· Street-view files for all County roadways

· Street centerlines

· Existing off-street trails

· Pavement Conditions

· Street, shoulder, and right-of-way widths (as available)

· Jurisdiction of roadways within the Project Area

· Roadway traffic volume and speed data

· Location of transit stops and routes

· Bridges (including conditions and restrictions)

· Rail lines, crossing locations, and crossing controls

· Air facilities

· Water facilities

· Goal 5 resources and setbacks

· Topography

· Lifeline routes

· Tourist Routes and Congestion Points

· Tsunami evacuation routes and congregation areas

· Pipeline facilities

· Known configuration or maneuvering problems (Participating Communities to provide, qualitative)

· Sidewalk presence and condition and buffer presence and type.

Consultant shall not conduct any new inventory other than the TTSP update of supplemental data noted below, to be incorporated into the draft TTSP Update, including:

1) Road Inventory: For arterials and collectors within County and Participating Communities, Consultant shall describe:

a) functional classifications, designations, and important uses (e.g., freight routes)

b) ODOT, County or city in jurisdiction

c) typical right-of-way widths, typical cross-sections, turn lane locations, and posted speeds

d) lane configurations and traffic controls at Project Area intersections

e) access densities along the following highways: US101, OR131, OR18, OR6, OR22, OR130, and OR53

f) pavement types and conditions (where data is made available by Participating Communities and ODOT)

g) bridge locations and conditions (where data is made available by Participating Communities and ODOT)

h) intelligent transportation systems infrastructure

2) Public Transportation Inventory: Providers of public transportation routes, transit stops, service characteristics, use of services, transit policies, etc.

3) Rail Inventory: For active rail lines, type of service, owner/operator of rail line, location of rail line and terminals, classification of the line (I, II, III), number of trains, daily/schedules, industries serviced and commodities handled, passengers served, track conditions, train speeds, crossing locations and controls.

4) Bicycle/Pedestrian Inventory: Conditions, locations, and use of bicycle facilities and pedestrian facilities on arterial and collector roadways, including locations of marked crossing locations and wheelchair ramps at Project Area intersections, location and trip characteristics of major pedestrian generators, Bicycle Level of Traffic Stress (“BLTS”) and Pedestrian Level of Traffic Stress (“PLTS”), and consistency of facilities with federal/State standards.

5) Marine Transportation Inventory: Navigable waterways, minimum channel depths, port locations, services provided and commodities transported.

6) Aviation Inventory: Airport locations, ownership and classifications and types of aircraft served (including drones).

7) Additional Inventories:

a) Major Truck Freight Routes

b) Major activity centers schools inside of Participating Communities and surrounding infrastructure inventory that could focus on potential Safe Routes to Schools program.

c) Locations of Title VI and EJ populations (identified by Consultant) and transportation facilities and services used by these populations.

Consultant shall prepare a revised draft TM#5, incorporating Agency and County edits and comments., and submit to APM for approval.

Consultant shall prepare an APM-approved final TM#5 stamped by a Professional Engineer.

4.2 Future Traffic Forecast – Technical Memorandum #6

Consultant shall draft Technical Memorandum (TM#6) ensuring the Methods and Assumptions portion of TM#5 addresses the use of Enhanced Zonal Cumulative Analysis or Future Volumes Tables and pulls Oregon Statewide Integrated Model "SWIM" data. Consultant shall submit methodology to TPAU for approval prior to TM#6. If methodology is approved by TPAU and APM, Consultant must use Analysis Procedures Manual TPAUs Statewide Integrated Model.

Consultant, as approved by Agency, shall coordinate with County staff to identify expected land development within the Urban Growth Boundary (“UGB”) and planned UGB expansion areas as identified in the Project Area’s Comprehensive Plan. Consultant’s future forecasts must be consistent with the 20-year population projections from Tillamook County’s Economic Opportunities Analysis. Consultant shall develop a base year (2024) and future year (2045) land use forecast for residential, employment, and school uses in coordination with Participating Communities staff for the Transportation Analysis Zones. Population projections used for the 2045 land use inputs must be based on control totals prepared by Portland State University.

Consultant shall consider traffic growth from planned local development, along with expected through traffic growth on US 101 and other major state highways located within Tillamook County, based on ODOT Future Traffic Volume estimates. Growth rates must be developed based on either historical count data or forecasts developed for roadways with similar characteristics (e.g., traffic volume, land use, location). Other recent studies or tools may be utilized for traffic forecasting, as appropriate, including the City of Tillamook TSP update and the Nehalem Bay TSP.

Consultant shall develop forecasted traffic volumes for average weekday AM and PM peak hour conditions, midday peak hours as appropriate, as well as seasonal peak conditions to estimate 30th-highest hour volume conditions. These forecasting methods must reflect and maintain consistency with countywide and city population projections.

Consultant shall develop future year 2045 baseline motor vehicle volumes for Project Area intersections and post-process them using National Cooperative Highway Research Program Report 255 guidelines, as coordinated with ODOT’s TPAU. The future 20-year baseline scenario must include only those transportation improvements in County's adopted plans with committed funding sources.

Consultant shall document the forecasting methods and results in draft TM#6 for comments and edits by Agency, TAC and County (due within 2 weeks of submittal of draft TM#6). Consultant shall prepare a final TM#6 incorporating feedback from Agency and County.

4.3 Project Management Team Meeting #3

Consultant shall organize, attend, and lead PMT Meeting #3 with appropriate TAC members to review GIS mapping, results of existing conditions analysis, and preliminary forecasting results. Consultant shall prepare draft meeting notes within 1 week following the meeting and distribute them to the PMT. Meeting is assumed to be 2 hours using Microsoft Teams. Up to 3 members of Consultant team are approved to attend.

4.4 Future…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .