00010599 Final Sample WOC.docx

Form C004-B122723R1

ATTACHMENT B – SAMPLE WORK ORDER CONTRACT

SOLICITATION NOTE: This Attachment contains a Sample Work Order Contract (“WOC”) with a Sample Statement of Work (“SOW”). The selected Proposer shall use the SOW as a baseline document during WOC negotiations to develop a proposed SOW which must identify all Work and Services described in the Mini-RFP and address all design considerations and requirements described for the Project. The selected Proposer shall add sufficient detail to Tasks and Deliverables that are included in the Services and omit any not needed for the Project. Items left highlighted in this baseline document will be negotiated or filled in at the time of WOC execution.

Once finalized and approved by ODOT, the negotiated SOW will become the final SOW for the WOC for the Project.

[SAMPLE]

WORK ORDER CONTRACT #: (ORBuys PO #: )

PRICE AGREEMENT (“PA”) #: (ORBuys #: ) Project Name/Location: CITY OF CORVALLIS

SOUTHWEST CORVALLIS AREA PLAN

TGM 2B-22

This Work Order Contract (“WOC”) is entered into by and between the State of Oregon (“State”), by and through its Oregon Department of Transportation (“Agency” or “ODOT”), and an [Enter the state of incorporation if consultant is a corporation] corporation (“Consultant” or “Contractor”).

This WOC incorporates by this reference:

a. all of the Terms and Conditions contained in Part II of the above referenced PA;

b. the provisions from the PA Exhibits with the exception of: E, E.1 and K;

c. the attached Statement of Work and Delivery Schedule (“SOW”);

d. Attachment A - Acronyms & Definitions - Reserved;

e. Attachment C – Disadvantaged Business Enterprise (“DBE”) Provisions; and

f. Attachment C.1 - Committed DBE Breakdown and Certification Form(s)-AE.

Attachment B, the Breakdown of Costs for Services (“BOC”), is kept in the WOC file and is not incorporated into the WOC.

WOC EXPIRATION DATE:____________. The required schedule for performance under the WOC is specified in the SOW.

Certified Small Business Aspirational Target (for State-only funded WOCs over $100,000, including as amended; see PA Exhibit K): N/A

Expenditure Account (“EA”)

# TG22LA10000

The Total Not-to-Exceed (“NTE”) amount for this WOC. This total includes: all allowable costs, profit, and fixed-fee amount (if any), shown in Section H.4 of the SOW; and $__________ for contingency tasks, each of which must be separately authorized by Agency.

This WOC is effective on the date it has been signed by the Parties and all required State approvals have been obtained. No Payment shall be made for tasks and deliverables specified in the SOW of this WOC (collectively, the “Services”) that are performed before: i) the WOC effective date and ii) a Notice-To-Proceed (“NTP”) has been issued by Agency.

CONSULTANT CERTIFICATION:

A. Any individual (the undersigned) signing on behalf of Consultant hereby certifies under penalty of perjury:

(1) Consultant has provided its correct taxpayer identification number to Agency for the above-referenced PA.

(2) Consultant is not subject to backup withholding because (a) Consultant is exempt from backup withholding, (b) Consultant has not been notified by the IRS that Consultant is subject to backup withholding as a result of a failure to report all interest or dividends, or (c) the IRS has notified Consultant that Consultant is no longer subject to backup withholding.

(3) The undersigned is authorized to act on behalf of Consultant, the undersigned has authority and knowledge regarding Consultant’s payment of taxes, and to the best of the undersigned’s knowledge, Consultant is not in violation of any Oregon tax laws. For purposes of this certification, "Oregon tax laws" means: (i) all tax laws of this State, including but not limited to Oregon Revised Statute (“ORS”) 305.380(4), ORS 305.620 and ORS chapters 316, 317, and 318; and (ii) any tax provisions imposed by a political subdivision of this State that apply to Consultant, to Consultant’s property, operations, receipts, or income, or to Consultant’s performance of or compensation for any work performed by Consultant; and (iii) any tax provisions imposed by a political subdivision of this state that apply to Consultant, or to goods, services, or property, whether tangible or intangible, provided by Consultant; and (iv) any rules, regulations, charter provisions, or ordinances that implement or enforce any of the foregoing tax laws or provisions.

B. Any individual (the undersigned) signing on behalf of Consultant hereby certifies the undersigned is authorized to sign this WOC and that:

(1) Consultant has read, understands and agrees to comply with the requirements set forth in the PA and in all Exhibits and other documents incorporated by reference in the PA.

(2) Consultant understands and agrees that any exhibits or other documents not physically attached to the PA that are incorporated by reference have the same force and effect as if fully set forth herein.

(3) Consultant has made all required Conflict of Interest (“COI”) disclosures, if any.

(a) Consultant understands and has provided to all Associates (as defined in the COI Guidelines) the ODOT COI Guidelines and COI Disclosure Form available at: https://www.oregon.gov/ODOT/Business/Procurement/Pages/PSK.aspx. Consultant and, to the best of the undersigned’s information, knowledge and belief, Consultant’s Associates, are in compliance with and have no disclosures required per the COI Guidelines (as may revised from time to time by Agency); or

(b) If disclosures regarding this WOC or the related Project are required per the ODOT COI Guidelines, Consultant has made such disclosures to Agency on a properly prepared and submitted COI Disclosure Form and, if determined necessary by Agency, a mitigation plan has been approved by Agency.

(5) Consultant has, and gives employees a written notice of, a policy and practice that meets the requirements described in ORS 279A.112. Such policy both prohibits, and prescribes disciplinary measures for, conduct that constitutes sexual harassment, sexual assault and discrimination against employees who are members of a protected class. Consultant agrees, as a material term of the WOC, to maintain the policy and practice in force during the entire WOC term (see additional information and sample policy template at https://www.oregon.gov/DAS/Procurement/Pages/hb3060.aspx).

(6) Consultant has no undisclosed liquidated and delinquent debt owed to the State or any department or agency of the State.

(7) Consultant is an independent contractor as defined in ORS 670.600 and as described in IRS Publication 1779 (https://www.irs.gov/pub/irs-pdf/p1779.pdf).

(8) In the event that Consultant is a general partnership or joint venture, Consultant signature(s) on this WOC constitutes certifications to the above statements pertaining to the partnership or joint venture, as well as certifications of the above statements as to any general partner or joint venturer signing this WOC.

Electronic Signatures.

The Parties agree that signatures showing on PDF documents, including but not limited to PDF copies of the PA, WOC and amendments, submitted or exchanged via email are “Electronic Signatures” under ORS Chapter 84 and bind the signing Party and are intended to be and can be relied upon by the Parties. Agency reserves the right at any time to require the submission of the hard copy originals of any documents.

Accessibility: The Oregon Department of Transportation is committed to complying with all statutory requirements to ensure that it is providing information that is more accessible to people with disabilities, as required by Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d), and 36 C.F.R. 1194 Appendix A. To request reasonable accommodation for access, due to a disability, to information related to this document, please contact the Oregon Department of Transportation’s Procurement Office at OPOAdministration@odot.oregon.gov or phone #503-986-2710.

CONSULTANT:

Signature Title Date

DOJ LEGAL REVIEW for ODOT: (Approved by via email dated _____)

ODOT (Procurement Authority)

Signature Print Name Date

STATEMENT of WORK and DELIVERY SCHEDULE for WOC # __________ under PA # __________

CITY OF CORVALLIS

SOUTHWEST CORVALLIS AREA PLAN

TGM File Code: 2B-22

Name:

Address:

Phone:

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:

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:

City Project Manager [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 the 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 planning project: Southwest Corvallis Area Plan, TGM 2B-22 (the “Project”):

Project Purpose/Transportation Relationship and Benefits The purpose of the Project is to develop a specific plan, the Southwest Area Plan, through a public process for adoption by the Corvallis City Council that refines land uses and provides an orderly plan for the development of local street networks and alternative transportation options to create safe, low-stress, and convenient navigation through the area. The Southwest Area Plan is intended to refine land uses in response to urbanization patterns in the area, state rulemaking on middle housing and Climate Friendly and Equitable Communities (“CFEC”), and local changes to land use zoning options. The expected outcome is a plan for Southwest Corvallis that establishes thoughtful zoning patterns, local street networks and alternative transportation options, and a sense of community and neighborhood character for the area.

Project Area The Project Area corresponds with the City of Corvallis (“City”) Planning Study Area B as shown in Figure 1 below.

Figure 1

Background The Corvallis Strategic Operational Plan identified the need for a Southwest Area Plan to address land use and transportation planning at the neighborhood scale. The Project Area is still urbanizing, with substantial vacant areas north of Western Boulevard/West Hills Road, west of 53rd Street, and along the western and southern fringe of the Project Area. The Project Area also has potential for infill development, most notably southwest of the intersection of US 20 and Brooklane Drive, where there is potential for development related to nearby Oregon State University.

The Project Area is developed in a manner that is typical for North America in the mid- to late-twentieth century. Residential development is largely single-family with some mid-rise multi-family, and commercial development is largely in the form of retail shopping centers and low-density office parks. Local streets often lack connectivity across land subdivisions and funnel traffic onto collector and arterial streets. Many older local streets lack sidewalks. There is an off-street path system in the area south of US 20, but this system is incomplete and lacks connectivity to major destinations, including Oregon State University and the Sunset Shopping Center. The result is that the transportation system in the Project Area is dominated by the automobile.

The Southwest Area Plan must be consistent with State goals and policies including recent changes related to middle housing and CFEC. Oregon House Bill 2001 (“HB 2001”), passed in 2019, required the City to allow all middle housing types in areas zoned for residential use that allow for the development of detached single-family dwellings. Middle housing is defined as duplexes, triplexes, quadplexes, cottage clusters, and townhouses. The Corvallis City Council adopted ordinances implementing the middle housing development recommendations in May 2022. HB 2001 allows local governments to regulate siting and design of middle housing. The Project will identify areas where development of middle housing is likely to occur and engage the public to determine if additional plan policies or projects are needed to reflect this development.

In 2022, the Land Conservation and Development Commission amended Oregon Administrative Rules (“OAR”) to adopt the CFEC program. The rules require cities in eight metropolitan areas, including Corvallis, to change their local transportation and land use plans to:

· designate climate-friendly areas of walkable mixed-use development;

· reform or eliminate parking requirements for development;

· provide a range of transportation options and implement other measures to reduce per-capita vehicle miles traveled; and

· improve equity to ensure that transportation, housing, and planning serve all Oregonians including traditionally underserved populations.

Efforts by the City to implement CFEC are underway. To date, the City has reformed parking requirements and completed Phase 1 of a study of potential climate-friendly areas. One of the potential climate-friendly areas in Corvallis is in the Project Area, centered around the Sunset Shopping Center Area and the intersection of Philomath Boulevard and SW 53rd Street. Development of the Southwest Area Plan will coordinate with the City’s efforts to implement CFEC to ensure that infrastructure and development in the Project Area will complement and support CFEC objectives.

Project Objectives Project Objectives include the following:

· Refine land uses to create lively neighborhoods with a mix of housing types, workplaces, shops, schools, and parks for people of all ages, incomes and abilities.

· Creating a sense of community and neighborhood character for the area.

· Provide a plan for the development of local street networks and alternative transportation options to create safe, low-stress, and convenient travel conditions for all modes.

· Implement recent legislation on middle housing and updated Transportation Planning Rules (OAR Chapter 660 Division 12).

· Deliver an adoption-ready Southwest Area Plan that meets all key objectives and expected outcomes identified within this SOW.

Acronyms and Definitions

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)

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

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

· 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. Software Requirements In addition to the software requirements set forth in the PA, the following shall apply to this WOC:

· Basecamp;

· See Section D – Format Requirements of this SOW; and

· As otherwise stated within tasks.

3. Professional Licenses, Registrations and Qualifications

a. Registered Professional Engineer (Civil or Traffic)

4. General Requirements

a. Endorsement of Data. Consultant shall place their official Oregon Registered Engineer seal and signature on all engineering design drawings and specifications furnished to ODOT, as well as any other materials specified in ORS 671.025, 671.379, 672.020(2), 672.025(2), 672.028(2) and 672.605, as applicable, that require such seal and signature.

b. 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.

c. 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.

d. 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.

e. 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.

f. General Requirements for Project Management Consultant and City shall each provide a Project Manager throughout the Project and other adequate staff to complete the Project in accordance with the anticipated timeline. APM, City Project Manager (“CPM”) (or alternate), and Consultant Project Manager (“PM”) shall serve as the Project Management Team (“PMT”) and may invite others to participate. City shall maintain effective communication and coordination between Agency and Consultant throughout the Project.

Consultant and City shall use Basecamp, a project management application administered by ODOT, to store Project-related files, facilitate Project-related communications, and coordinate review of Project deliverables.

g. General Requirements for Written and Graphic Deliverables All documents must be written concisely, in plain language, and use an easily understood format. Where possible, Consultant shall present information in tabular or graphic format, with a simple and concise accompanying narrative. All documents must be readable and usable in non-colorized text.

Consultant shall write materials intended for the public, such as meeting presentations, at no higher than a high school grade level using the Flesch–Kincaid Grade Level Formula. Consultant shall translate online Public Events and other event materials into Spanish. Community Advisory Committee (“CAC”) materials must not be translated.

Written deliverables must include the Project name, a title that refers to the WOC deliverable, draft number, subtask number, and date of preparation.

h. General Requirements for Revised and Final Deliverables City shall provide consolidated non-conflicting written comments of public and other reviewers to Consultant before preparation of revised and final deliverables. If City cannot reconcile conflicting comments, APM will determine which comments will be kept.

Revised and final deliverables must not include names and logos of Consultant, Transportation and Growth Management Program, ODOT, or Oregon Department of Land Conservation and Development or project codes except on the acknowledgement page.

The following text must appear in the final version of all revised and 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 Highway Administration, 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.”

i. General Requirements for Meetings and Public Events:

Meetings must be held in person, by video/virtual conference, by telephone, or any combination of the aforementioned, as determined by the APM. Meetings may include, but are not limited to: kick-off, project coordination, committee and public meetings or work sessions.

Public Events include any public outreach opportunities, but are not limited to: open houses, workshops, tabling, focus groups, small group or one-on-one briefings, interviews, and public meetings.

“Arrange” meetings and Public Events includes, but is not limited to: scheduling dates and times with participants, distribution of agendas and relevant materials in advance of the meeting or Public Event, reserving a suitable location, placing advertisements in local media, and posting notices in public locations (such as City buildings and libraries). Unless otherwise stated within specific tasks, “arrange” includes attendance.

Unless specified for specific tasks or otherwise agreed to in writing by Agency, City is responsible for meeting arrangements. City shall, in accordance with City standards regarding meetings, prepare and distribute all staff reports, agendas, relevant materials, necessary public notices, and notifications, and provide public outreach for community involvement. City shall arrange, schedule and pay for meeting room accommodations; coordinate and pay for meeting materials and refreshments, including printed materials and postcards that will be mailed to residents (postage also paid by City). Additionally, City shall coordinate, print and distribute advertising materials and information in City social media accounts, citywide utility bills and other City controlled medium, as appropriate.

“Conduct” meetings and Public Events includes, but is not limited to: preparing agendas and relevant materials, making presentations, facilitating discussion of relevant issues, and preparing summaries.

City shall ensure that all meetings are noticed and held in accordance with City standards and ORS Chapter 192 - Records, Public Reports and Meetings.

Meeting locations must be accessible by people with disabilities. Meeting notices must include an offer to make accommodations for people with disabilities with sufficient advance notice, and translation services upon request, with contact information for such notification.

j. General Requirements for Public Involvement When conducting the public involvement in this Project, the City and Consultant shall consider environmental justice, which is the fair treatment and meaningful involvement of all people regardless of race, color, national origin, or income with respect to the development, implementation, and enforcement of environmental laws, regulations, and policies.

Fair treatment means that no group of people, including a racial, ethnic, or a socioeconomic group, should bear a disproportionate share of the negative environmental consequences resulting from industrial, municipal, and commercial operations or the execution of federal, state, local, and tribal programs and policies.

Meaningful involvement means that: (1) potentially affected community residents have an appropriate opportunity to participate in decisions about a proposed activity that will affect their environment and health; (2) the public's contribution can influence the regulatory agency's decision; (3) the concerns of all participants involved will be considered in the decision-making process; and (4) the decision makers seek out and facilitate the involvement of those potentially affected.

The Project must include specific steps to provide opportunities for participation by federal Title VI communities and Underserved Populations as defined in OAR 660-012-125. City and Consultant shall use the ODOT Guidelines for Addressing Title VI and Environmental Justice in Transportation Planning (January 2015) and the Equitable Community Engagement Guide to identify Title VI and Underserved populations, formulate public involvement strategies, and report outreach efforts to and participation by members of these populations.

Consultant shall work with City to identify effective methods of engagement with Spanish-speaking and other Title VI communities in the Project Area. Based on recommendations in the Public Involvement Plan, Consultant shall:

• provide a Spanish interpreter for Targeted Outreach and Public Event meetings as needed.

• provide public involvement materials for Targeted Outreach and Public Events in English and Spanish.

Project meeting locations for in-person meetings must be accessible by people with disabilities. Notices for in-person meetings must include an offer to make accommodations for people with disabilities with sufficient advance notice, with contact information for such notification. City will pay for any incentives or thank you gifts for public participation including but not limited to gift cards, bus passes, meals, refreshments, etc.

Consultant shall compile email addresses and comments provided by visitors to the Project Website and provide these to City before each PMT meeting. Consultant shall post notices of Project Meetings and summaries of Project meetings to the Project Website.

City shall seek to have participation in Project meetings reflect the composition of the community. City shall make efforts to include representatives of underserved communities in Project meetings.

All meetings in the Project are in person with the ability for people to attend online unless otherwise specified in the subtask. City is responsible for providing staff, equipment, and software needed to allow online participation in Project meetings.

k. General Requirements for Traffic Analysis

· Consultant, by and through an Oregon registered Professional Engineer, shall perform or oversee all traffic analysis services. Final memoranda containing traffic analysis must be stamped by a Professional Engineer with license being current and in good standing, with expertise in civil or traffic engineering.

· Traffic analysis must comply with ODOT’s Analysis Procedures Manual available at: https://www.oregon.gov/odot/Planning/Pages/APM.aspx

C. REVIEW, COMMENT and SCHEDULE OVERVIEW

1. Consultant shall coordinate with Agency staff as necessary and shall revise deliverables to incorporate review comments. APM will determine what constitutes a “minor” or “major” edit. Consultant is not required to make major revisions without an approved WOC amendment. This provision does not limit the right of Agency to require correction of deliverables that do not meet the standards and specifications outlined in this SOW.

2. Unless otherwise specified in a given task, the following review, schedule, and comment overview shall apply:

D. FORMAT REQUIREMENTS

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

· Consultant shall submit all written (text) and graphic deliverables (draft and final) electronically in Microsoft Word (.doc) or PowerPoint and final deliverables in Microsoft Word (.doc) and Portable Document Format (.pdf). Written deliverables must include the project name, a title that refers to the contract deliverable and date of preparation. Any deliverables specified for posting on the Project Website must be posted in .pdf format. Each draft and final spreadsheet-based deliverable must be provided in MS Excel file format and must be fully compatible with version used by Agency.

· Graphic deliverables submitted for review must be converted to .doc or .pdf for readability. All graphic deliverables must be well documented, with project name, a title that corresponds to the contract deliverable, draft number, a legend, and the date of preparation.

· Electronic versions of base and plan maps must be in color, and in a color scheme that ensures readability in black and white and in a color-blind safe palette. Display-sized maps must be printed in color when important to public comprehension.

· Maps must be at scale legible in the final document and include details necessary to ensure usability, such as city limits, Urban Growth Boundaries, street names, relevant environmental and cultural features, legend, date, etc.

· Display-sized maps for Project meetings must be printed in color when important to public comprehension and must be mountable on foam core to allow display on an easel or wall.

· Consultant shall provide City and APM with any Geographic Information Systems (“GIS”) data sets or updated data sets developed for this Project.

· 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 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.

Consultant understands that the City has significant tasks related to, and involvement with, the Project. As such Agency has entered into a separate Intergovernmental Agreement (XXX) (“Project IGA”) with the City to provide services to the Project as described in this SOW that are not the responsibility of the Consultant. Information regarding the City deliverables and responsibilities is for informational purposes only.

For meeting requirements, including the defined meanings of “conduct” and “arrange”, refer to Section B, part 4, subsection i., of this SOW, under General Requirements for Meetings.

For tasks or subtasks noted as [CITY TASK], Consultant has no tangible deliverables associated with these tasks.

The General Project Delivery Schedule is consolidated in Table 1 at the end of Section E.

TASK 1 PROJECT INITIATION AND ADMINISTRATION

1.1 PMT Meetings

Consultant shall arrange and conduct approximately two PMT Meetings each month during the Project, for a total of up to 36 PMT Meetings. At least one Consultant staff must attend each PMT Meeting. Consultant shall provide an agenda 3 business days prior to each PMT Meeting and a short summary of issues resolved and action items within 3 business days after each meeting.

1.2 Project Initiation Meeting and Site Tour

City shall arrange and Consultant shall conduct a Project Initiation Meeting with CPM, PM, APM, and others invited by City. CPM shall present an overview of City’s goals for the Project and provide a tour of key sites in the Project Area.

Consultant shall review the draft Refined Project Schedule and identify background data and materials needed for Project at the Project Initiation Meeting.

1.3 Refined Project Schedule

Consultant shall prepare a draft Refined Project Schedule and deliver it to City and APM for review at Project Initiation Meeting. City shall and APM will provide comments within 5 business days following receipt of draft Refined Project Schedule. Consultant shall make revisions that reflect discussion and comments to create the revised Refined Project Schedule. The revised Refined Project Schedule must conform to the General Project Delivery Schedule shown in Table 1, at the end of Section E, and the milestone dates provided in this Contract. Where reasonable, Consultant shall schedule and perform tasks concurrently to minimize time. The revised Refined Project Schedule must identify dates for the Task 2 Community Advisory Workgroup (“CAW”) and Technical Advisory Workgroup (“TAW”) meetings, Public Events and other Task 2 activities. Consultant shall update the revised Refined Project Schedule as needed, at APM’s request, and distribute the updated schedule to City and APM.

City Deliverables

Consultant Deliverables

TASK 2 OUTREACH

2.1 Draft Memorandum #1: Public Involvement Plan

Consultant shall prepare Draft Memorandum #1 that adds detail to the Public Involvement framework established in this SOW. Draft Memorandum #1 must identify Title VI and Underserved Populations in the Project Area and identify strategies for engaging these populations consistent with requirements for an engagement-focused equity analysis in OAR 660-012-0135(3). This must include methods to:

· Engage with members of Title VI and Underserved Populations to develop key community outcomes.

· Gather, collect, and value qualitative and quantitative information from the community on how proposed change benefits or burdens Title VI and Underserved Populations.

· Understand where and how intersectional discrimination compounds disadvantages.

· Integrate feedback from Title VI and Underserved Populations into project prioritization and selection of performance measures.

2.2 Initial Project Website Development

Consultant shall develop a Project Website that is available to the public for the entire duration of the Project. Consultant shall coordinate with the City to determine the structure and format for the Project Website. Consultant shall host and obtain a stand-alone URL for the Project Website. City shall maintain a link from City’s website to the Project Website.

Consultant shall prepare initial content for the Project Website that includes an overview of Project Objectives, a Project Schedule showing major Project tasks and tentative dates for public meetings, and ways to provide comment and to be added to the Interested Parties List established in Task 2. The Project Website must include a Spanish-language landing page with initial content in Spanish.

Project Website must include an online comment form with a map of the Project Area to allow public input linked to specific locations on the map. Consultant shall compile email addresses provided by visitors to the Project Website expressing interest for notification of Project progress, meetings, and presentations and provide to City to create and maintain the Interested Parties List (Task 2.4). Consultant shall provide email addresses and submitted comments to City before Project meetings and events.

Consultant shall provide draft initial content for the Project Website to City and APM and incorporate revisions resulting from 1 consolidated round of City and APM review before the Project Website revised initial content is made available to the public. The City’s and APM’s review shall consist of a single list of non-contradictory comments (and specific direction for each comment).

2.3 Committee Rosters [CITY TASK]

City shall prepare a roster for a CAW with area residents and interested parties. City shall compile a list of community members and local organizations who may be interested in the Project and invite them to participate. People invited on the CAW may include:

· Area residents

· Local Business Representatives

· Pedestrian and bicycle advocates

· Elderly and youth

· Low-income individuals

· Disabled individuals

· Transportation Options and Public Transportation providers

· Other people in Underserved Populations identified in OAR 660-012-0125 and in Draft Memorandum #1

City shall prepare a roster for a TAW that reviews technical issues including those related to implementation of OAR 660-012 and transportation modeling. City shall identify organizations and agencies for inclusion on the TAW, including representatives of:

· City Council

· City Planning Commission

· Benton County

· Corvallis Area Metropolitan Planning Organization (“CAMPO”)

· ODOT Region 2 Planning and Traffic

· Oregon Department of Land Conservation and Development

· Corvallis School District

· Oregon State University

· Fire and Emergency Service Providers

· Corvallis Police and Benton County Sheriff’s Office

· City Public Works

2.4 Interested Parties List [CITY TASK]

City shall maintain an Interested Parties List that includes CAW members and other parties expressing interest in the Project for notification of Project progress, meetings, and presentations.

2.5 CAW Meetings

City shall arrange and conduct 6 CAW Meetings to provide an overview of the Project and review Project deliverables. Consultant shall attend CAW Meetings via videoconference to make presentations about the content of Project deliverables and to seek input from meeting participants to inform development of the Southwest Area Plan. CAW Meetings must cover the following content:

· Meeting #1 must provide an overview of the Project, adopt the committee charter, and review Draft Memoranda #1 and #3. Consultant shall seek input on methods for reaching underserved populations identified in Draft Memorandum #1, the goals in Draft Memorandum #3, and the relative importance of the goals developed in Draft Memorandum #3.

· Meeting #2 must review the existing conditions identified in Draft Memorandum #4. Consultant shall seek input on existing conditions in the Project Area and on the multimodal gap analysis identified in Draft Memorandum #4.

· Meeting #3 must review the land use and transportation alternatives developed in Draft Memorandum #5. Consultant shall seek input on how the land use and transportation alternatives address Project goals developed in Revised Memorandum #3. Meeting #3 must occur at least one week before Public Event #2 to allow the event materials to be modified based on CAW feedback.

· Meeting #4 must review the preferred land use and transportation alternative while Revised Memorandum #5 is under development. Consultant shall seek input on whether any refinements to the preferred land use and transportation alternative are needed.

· Meeting #5 must review the public investments identified in Draft Memorandum #6 and multimodal mobility impact analysis developed in Draft Memorandum #7. Consultant shall seek input on priorities for public investments and transportation impacts resulting from the preferred land use and transportation alternative.

· Meeting #6 must review proposed plan designations, zoning, and development code amendments developed in Draft Memorandum #8. Consultant shall seek input on priorities for plan and code amendments needed to implement the preferred land use and transportation alternative.

CAW Meetings are expected to be 2 hours in duration. For each CAW Meeting, City shall prepare a draft agenda and hold a one-hour review and preparation meeting online with Consultant to review the agenda and meeting presentation content. City shall send agenda and any meeting materials to CAW members at least 1 week prior to the meeting. At least two Consultant staff shall attend each meeting. Consultant shall provide meeting summaries that include key issues discussed at meetings and any implications for Project Schedule or deliverables to City and APM within 5 business days following each CAW Meeting.

2.6 TAW Meetings

City shall arrange and conduct 6 TAW meetings to provide a review of Project deliverables. Consultant shall attend TAW Meetings via videoconference to make presentations about the content of Project deliverables and to seek input from meeting participants to inform development of the Southwest Area Plan. TAW Meetings must cover the following content:

· Meeting #1 must provide an overview of the Project, adopt the committee charter, and review Draft Memoranda #1 and #2. Consultant shall seek TAW input on the Public Involvement Plan developed in Draft Memorandum #1, including strategies to reach underserved populations in the Project Area. Consultant shall seek TAW input on coordination of the Project with applicable plans and policies including those identified in Draft Memorandum #2.

· Meeting #2 must review Project goals developed in Draft Memorandum #3 and existing conditions identified in Draft Memorandum #4, including the results of the multimodal transportation gap analysis.

· Meeting #3 must review land use and transportation alternatives developed in Draft Memorandum #5. TAW Meeting #3 must occur at least one week before Public Event #2 to allow the event materials to be modified based on TAW feedback.

· Meeting #4 must review the preferred land use and transportation alternative while Revised Memorandum #5 is under development. Consultant shall seek TAW feedback on whether any refinements to the preferred land use and transportation alternative are needed.

· Meeting #5 must review the public investments identified in Draft Memorandum #6 and multimodal mobility impact analysis…