university of oregon (“university”) request for proposal

40
RFP for Website Redesign (PCS# 226000-01273-RFP) Page 1 of 24 UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL (“RFP”) RFP Title: RFP for User Interface Design Developers: Website Redesign RFP Number: PCS# 226000-01273-RFP Issuing Office: Purchasing and Contracting Services 1600 Millrace Dr., Suite 306 Eugene, OR 97403 [email protected] Closing Date and Time: May 1, 2018 at 5:00 p.m. (Pacific Time) Proposals must be received by the Issuing Office, no later than the Closing Date and Time. Postmarks will not be considered.

Upload: others

Post on 05-Apr-2022

0 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 1 of 24

UNIVERSITY OF OREGON (“University”)

REQUEST FOR PROPOSAL (“RFP”)

RFP Title: RFP for User Interface Design Developers: Website Redesign RFP Number: PCS# 226000-01273-RFP Issuing Office: Purchasing and Contracting Services

1600 Millrace Dr., Suite 306 Eugene, OR 97403 [email protected]

Closing Date and Time: May 1, 2018 at 5:00 p.m. (Pacific Time)

Proposals must be received by the Issuing Office, no later than the Closing Date and Time. Postmarks will not be considered.

Page 2: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 2 of 24

SECTION 1 - GENERAL INFORMATION 1.1. Scope of Procurement.

The University of Oregon, on behalf of the Oregon Career Information System (“University” or “CIS”), is seeking Proposals from qualified User Interface Design developer(s) to redesign its website Interface as more specifically described in this RFP.

1.2. Background.

CIS is a statewide consortium housed at the University of Oregon. It was first used by Oregon schools in 1972 and is the longest-running outreach center under the College of Education. CIS is used by a variety of stakeholders throughout the state, including state agencies, private companies, and public educational institutions. CIS provides a seamless connection between education, workforce, career, and reskilling. CIS assists state agencies, schools, community organizations, and private businesses to remove barriers to career planning, provide comprehensive information about opportunities, tools that teach career self-management skills, and information specific to Oregon’s labor and education markets. CIS functions as an e-Learning platform and provides personalized tools for users to create transition plans between education, workforce, career, and reskilling. The personalized account transfers among the many CIS sites become a lifelong career management tool for individual Oregonians. CIS uses a train-the-trainer model to provide support to the stakeholder organizations that are part of our consortium. For a brief overview of the system, view this online video: https://oregoncis.uoregon.edu/tutorials/CIS_Navigation.htm. CIS is an ASP.NET Webform application and data is stored in SQL Server. CSS Stylesheets manage the layout of content. Primary users include dislocated workers, Self-Sufficiency recipients, Vocational Development clients, Counselors, administrators, middle and high school students, teachers, college instructors, case workers, parole offices, employed adults, librarians, and human resource professionals. Primary users also include CIS staff who provide training support and customer service to consortium members implementing the system. Secondary users include administrators, staff in partner CIS States, and parents of students. CIS has refactored its code to allow for responsively designed CSS stylesheets to be implemented so that users can optimally access CIS using a variety of personal devices. However, the information architecture and current interface reflect the desktop version, which requires users to rely on text to explain concepts as opposed to meaningful information graphics and interactive tools. Funding for CIS activities is provided by annual license fees from consortium members, grants from federal government agencies, state grants, and state and local contracts.

1.3. Closing Date and Time. All Proposals must be received by University’s Issuing Office on or before May 1, 2018 at 5:00 p.m. (Pacific Time) (“Closing Date and Time”). Postmarks will not be considered. Electronic submissions of Proposals are encouraged. The Issuing Office’s mailing/delivery address and email address are listed on the cover page and in the “Issuing Office” Section below.

Page 3: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 3 of 24

1.4. Issuing Office. The University’s Purchasing and Contracting Services department is

the Issuing Office for this RFP. Proposals may be submitted manually or electronically to the Issuing Office at the following addresses:

Purchasing and Contracting Services 1600 Millrace Dr., Suite 306 Eugene, OR 97403 [email protected]

Issuing Office hours for receipt of manually submitted Proposals are Monday through Friday 8:00 a.m. to 5:00 p.m. Eugene, Oregon local time.

1.5. General Responsibilities of Proposers.

1.5.1. Clarifications for Proposer. For additional information or clarification of requirements contact (in accordance with the requirements set forth in Section 4.2 below) the requesting University department:

Laura McCoid ED CIS Oregon 1244 University of Oregon Eugene, OR 97403 [email protected]

Additional information or clarifications must be made in writing to the above

contact. University will not respond to oral inquiries.

1.5.2. Monitoring. This RFP will be posted on the University of Oregon Purchasing and Contracting Services (PCS) website, under “Business Opportunities,” accessible at: http://pcs.uoregon.edu/content/business-opportunities. Any Addenda including, without limitations, extensions of the Closing Date and Time will be posted to the PCS website. Proposers are responsible for monitoring the PCS website on a periodic basis for any modifications to the RFP. University is not required to issue individual notifications.

1.5.3. Representations, Certifications and Acknowledgments. For consideration, you

must submit your Proposal with a completed and signed Representations, Certifications and Acknowledgments by the Closing Date and Time. A blank form of the Representations, Certifications and Acknowledgements for you to complete, sign, and submit is attached to this RFP as Exhibit A.

1.6. Voluntary Pre-Proposal Conference. A voluntary pre-proposal conference will be

held on April 16, 2018 from 10:00 a.m. – 11:00 a.m. (Pacific Time). The purpose of the conference is to discuss the technical specifications identified in this RFP and address Proposer questions. The conference is limited to a discussion of technical specifications. University expects all Proposers with technical questions to raise them at this conference.

Page 4: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 4 of 24

Conference Details:

Date: April 16, 2018 Time: 10:00 a.m. – 11:00 a.m. (Pacific Time) Location: Via Zoom Web Conferencing:

Join Conference from a PC, Mac, Linux, iOS or Android:

Go to: https://zoom.us/j/770643714 Enter Meeting ID: 770 643 714 Follow Prompts Conference connection will be available at 9:50 a.m. (Pacific Time).

1.7. Definitions. As used in this Request for Proposal (unless otherwise stated), the

capitalized terms shall have the meanings set forth in UO Policy 580.061, Sec B.

SECTION 2 - SCOPE OF SERVICES 2.1. Statement of Services.

Proposer will design and develop a new website interface for CIS. Proposer will be responsible for updating the brand of CIS, developing information graphics, designing the user interface, designing the user experience, and generating a report to CIS for restructuring the information architecture. Proposer must design an interface with the following properties and functionality:

2.1.1. General Properties/Functionality of Website Redesign. • Cascading Style Sheets (CSS) must be built to create an ideal user experience

while providing basic functionality for those users employing older or limited technology.

• The ability for CIS staff to create and manage easily additional dashboard interfaces.

• Increased visibility to build brand awareness, support outreach efforts, and

increases use of and access to CIS by primary users, secondary users, and consortium member organizations.

• Simple, consistent and intuitive navigation that is consistent with the state of the

art and increases user interaction and participation via online tools.

• CSS style sheet templates that provide a visually appealing interface with an attractive mix of text, graphics and photos.

• Embeds a call-to-action opportunity for user to interact with the data (e.g.,

contact an organization, create a checklist of events leading to qualifications, etc.).

Page 5: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 5 of 24

• Common Theme/Consistent Design. Each section of the site must have a

common, consistent look/theme. Site, tools, and relevant work products will be branded.

• An updated CIS brand with new CSS Style sheets, logo, and design elements.

• Ability for CIS to easily manipulate, edit and update page content, photos, and

graphics.

• Layout must comply with Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. § 794 (d)) and Section 255 of the Communications Act of 1934 (47 U.S. Code § 255). See also, 36 CFR Parts 1193 and 1194; RIN 3014-AA37, World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines (WCAG 2.0), and University accessibility standards.

(https://communications.uoregon.edu/accessibility).

• Must be compatible with current versions of commonly used Internet browsers,

including Google Chrome, Internet Explorer, Safari, and Firefox.

• Must incorporate user and stakeholder insights into the design development

(CIS will provide these).

• Be mobile-friendly and compatible with common digital devices.

• Must provide CSS Style sheets for organizational website and access portal.

• Must be optimized to allow ranking of portal pages and Google analytics on website, but no search engine results on the internal pages of the system.

• Ability to extract legacy website statistics e.g., percent of users on Windows (7

and 10), Chrome, Firefox, Safari, IE, etc.

2.1.2. Style Guide Requirements. • Headers. • Footers.

• Footer pages.

• Fonts.

• Color palette.

• Ability of Customer to customize layouts. See Section 2.1.4.5 of this RFP.

Page 6: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 6 of 24

• Navigation strategies, such as breadcrumbs, to inform users of location.

• Tutorial Standards.

• Outside Link standards.

• Copyright statement(s).

• Help interface/page(s)

• Standard messaging (e.g., page not found, errors).

• Graphics standards.

• Announcement standards.

2.1.3. Graphics Requirements. • Library of informational graphics related to labor market and education data.

• Library of informational graphics reflecting progress and accomplishments for

the end user account dashboard.

• Logo.

• Library of informational graphics reflecting report and reporting functionality for the administration user account dashboard.

• Library of graphic/icons indicating common tasks/resources such as tutorials,

help, like/dislike, etc.

2.1.4. Interface and Functionality Requirements of Design Pages Using CSS Style Sheets.

2.1.4.1. General functionality:

• Login/Organizational Page.

• Generic dashboard for end users without a portfolio.

2.1.4.2. End user dashboard with the following functionality:

• Branding by individual through images and words.

• Three dashboard templates resonate with end-user age: elementary/middle school, high school, adult users. Layout functionality will include customization options by Site Administrator (welcome message, graphic,

Page 7: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 7 of 24

layout choice).

• Ability to review past accomplishments.

• Ability to view and measure progress on assigned career plan activities.

• 2-4 Information graphics reflecting progress and accomplishments.

• Dashboard for end user to display account information to public.

• Interface for managing and editing the account (update password, add emails, etc.)

• Transfer portfolio interface.

2.1.4.3. Staff user dashboard with the following functionality:

• Dashboard with access to reports. • Interface to design reports.

• Interface to generate reports.

• Interface to contact end users.

• Interface to affiliate staff account with groups of end user accounts.

• Interface to manage career plan (and override Career Plan elements for end

user).

• Interface to view saved end-user account content.

2.1.4.4. Advisor/Parent dashboard: • Dashboard with access to select end user account content.

• Ability to generate reports.

• Ability to apply comments or send messages to end user accounts.

2.1.4.5. Administrator Dashboard with the following functionality:

• Dashboard with access to reports. • Interface for customizing end user experience, including uploading course

content from a template, exporting course content into a template, and

Page 8: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 8 of 24

creating pathways from course content.

• Setting custom links within CIS.

• Setting and managing portfolio privacy options.

• Customizing the Career-Related Learning Experiences templates.

• Customizing the end-user dashboard (welcome message, image, etc.).

• Customizing the staff user dashboard.

2.1.4.6. Report interfaces for staff and administrator:

• For end user activity and according to embedded completion metrics.

• Interface for data exporting functionality.

• Interface for data management functionality (merge, hide, transfer, delete accounts; create accounts; assign career plans).

• Interface for creating and managing accounts for end users and users

affiliated with the end users.

2.1.4.7. Report interfaces for District/State Agency Accounts (managing a group of sites):

• Customizing Career Plan for group of sites.

• Setting custom links within CIS.

• Setting and managing portfolio privacy options.

• Customizing the Career-Related Learning Experiences templates.

• Customizing the end-user dashboard (welcome message, image, etc.).

• Customizing the staff user dashboard.

• Access affiliated sites’ administration tools.

• Contact site administrators and staff.

• Generating reports on site progress and usage according to preset completion metrics.

2.1.4.8. Career Plan Interface:

Page 9: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 9 of 24

• Administrator interface providing the process of selecting and modifying

items from an established library. This includes an interface to export and import career plans.

• Staff interface providing instruction and guidance on helping users complete a library item. This interface will include information graphics related to progress and completion.

• User interface providing instruction and links to library items. This interface

will include information graphics related to completion and progress. 2.1.4.9. Formal Career Assessment Tools (Interest Profiler, Interest Profiler

Short Form, SKILLS, Dependable Strengths, Work Importance Locator: 5):

• Introduction pages. • Process pages.

• Results page.

• Print functionality page.

• Interpretation page.

2.1.4.10. Career Sorting Tools and Informal Assessments Tools (Reality

Check, Occupation Sort, School Sort, Certificate Sort, Financial Aid Sort, Lifestyle Priority Chart, Career Decision Maker, Holland Code Sorter, Learning Styles, Employability Skills--10):

• Introduction pages. • Selection pages.

• Process pages.

• Results page.

• Interpretation page.

2.1.4.11. Information Components:

• Landing page/informational page [could become a process-driven interface. • Search/Selection.

• Content page(s).

Page 10: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 10 of 24

• Compare page(s).

• Contact School(s) pages.

• Search functionality pages.

• Print functionality page.

• Filter interface.

• Navigation pages/process among Information Components.

• Action plan creation page.

• Save and comment page(s).

2.1.4.12. Personalized Portfolio Tools:

• Resume Creator.

• Application Tracker.

• Combined Report of Assessments.

• Saved titles from Information components.

• Saved results from Assessments and Sorts.

• Application Tracker “tracks applications.”

• Activities Chart.

• Stored Files and Links.

• Career-Related Learning Experience Planner.

• Senior Project/Extended Application Project

2.1.4.13. Site Reference Guide and Curriculum Activities:

• Dashboard Reference Guide.

• Dashboard for Curriculum Sets:

o Selection pages.

o Content page(s).

Page 11: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 11 of 24

• Glossary page(s).

• Resource pages for specific populations (Recursos para Latinos, etc.)

CIS will provide architecture of current site, research related to user needs, statewide focus group outcomes related to the current design interface, select wireframes, and select example websites.

2.2. Phases of Development1. University expects the services to be performed in the following phases: 2.2.1. Phase 1: Planning, Alignment and Requirements: Phase 1 will include the

development of a project plan with clear milestones and a timeline for review. A design roadmap will be created that will include:

• A Requirements document that maps out the improvements to be made.

• A revised site map/information architecture of portal that incorporates new

design, features, and improvements.

• Team alignment on type and number of wireframes to be designed.

• Completion Date: Mid June 2018.

2.2.2. Phase 2: UX Design. Phase 2 will include the design of the following:

• A components library with code examples Use this link as an example of how to format the library: https://getbootstrap.com/docs/4.0/components/alerts/ (select items from sidebar for rest of components))

• An interactive version of the design hosted on your own website for us to provide feedback. Must be compatible with Zurb.

o Flows and Navigation Maps

- Evaluate and/or replace current mega-menu with new navigation scheme that’s easier for users to follow and works on mobile).

- Breadcrumbs or visuals indicating related and nested content.

- Navigation between a user’s interaction with a tool and content and 1 Work for all phases is subject to ongoing funding. This RFP is not a guaranty that all services will be contracted for. Reservations. University reserves the right to accept or reject Proposals on each line separately, or as a whole, to award items separately or in aggregate, and to contract with one or more vendors, all as determined by University to be in the best interest of University.

Page 12: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 12 of 24

access/return to their personal dashboard.

- Example generic dashboard and experience for end user without a portfolio account;

- Dashboard and example experience for a portfolio user (a data

driven/site administrator/machine-driven personalization) that allows an individual to brand the interface (pictures, goal highlight, level of education goal in transition process and subsequent steps related to that);

- Dashboard and example experience for staff-level user (generate a

report, merge portfolios);

- Dashboard and example experience for Site Administrator (customize Career-Related Learning Experience template).

- Custom flow designs based upon the number of times a person has

experienced the system (and inbuilt form of orientation/navigation). For new accounts or no accounts—prompt to create an account (Onboarding).

- Flow designs for staff, advisor and user account interaction and

communication.

- Flow designs for staff and administrator accounts when generating reports and engaging in user account follow-up.

- Flow designs for announcing updated content or opportunity to users

(e.g., user progress on assigned activities for staff accounts, introduction of new tool to end users accounts).

o Structuring, organization, and labeling reduce user confusion between

specific terminology used by professionals in career development and counseling (e.g. Financial aid, programs of study, etc.) and general/potentially misleading terms by regular users (e.g., Scholarships, majors).

o Finding and managing information e.g., thinking about how the search

results display.

- Saved items in CIS, including assessment results and curriculum.

- Display of how users saved content displays in an actionable form - connecting pieces of related information.

- Commonalities among reports.

o Onboarding process for new users for end-users (students and adults in

Page 13: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 13 of 24

transition) and staff who are learning the new design interface.

• Completion Date: End of July 2018.

2.2.3. Phase 3: Visual Design Requirements:

• Functional, engaging, and clean design.

• Full HTML with CSS Mock-up of all pages that follows CSS Standard practices (see https://gist.github.com/bobbygrace/9e961e8982f42eb91b80).

• Logo & Branding graphics in editable format.

• Completion Date: End of September 2018

2.2.4. Phase 4: Pass Off:

• Proposer will meet with CIS team to review all final deliverables, which would include final annotated wireframes, CSS style sheets, and visual design compositions.

• Proposer will participate in 2 development training and reviews post pass-off -ensuring that the development team is effectively implementing design.

• Completion Date: October 2018.

3. PROPOSER SUBMITTALS AND OTHER REQUIREMENTS 3.1. Overview.

3.1.1. University expects all Proposers to submit the information identified in Sections 3.2 through 3.8 of this RFP. Where the requested submittal is marked (E), the submittal will be evaluated and Proposers are expected to provide comprehensive written responses to the evaluated specifications. Points will be awarded based on the degree to which the University’s evaluators determine that the Proposer meets the evaluated specification. A Proposer that does not respond to an evaluated specification may receive no points for that specification. The determination as to whether the Proposer meets the submittal requirements rests solely with University. If University determines that a Proposer does not meet a submittal requirement as specified, or has not included information relevant to the specific submittal requirement, University may deem the Proposal “non-responsive” and terminate its review of the Proposal.

SUBMITTALS

3.2. Cover Letter. A summary of the Proposal.

Page 14: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 14 of 24

3.3. Contact Information. The name and title of Proposer’s primary contact regarding this RFP, the business name, the primary address, the primary contact’s telephone number, and the primary contact’s email address.

3.4. Entity Verification.

3.4.1. If the Proposer is an entity other than a sole proprietorship, written evidence in the form of a Secretary Certificate (or equivalent documentation) that the individual submitting the Proposal is authorized to act for and bind the Proposer in all matters relating to the Proposal and possible subsequent contract. This type of written documentation is commonly in the form of a Secretary’s Certificate or Officer’s Certificate issued by the board or committee governing the entity. The written documentation, however, is not required to be in any particular form as long as it clearly shows the individual signing the Proposal has authority to bind the Proposer.

3.4.2. If Proposer is an entity other than a sole proprietorship and the entity was not

organized or incorporated in the State of Oregon, written evidence that Proposer is in good standing in its state of organization or incorporation. This type of written documentation is commonly in the form of a certificate of good standing. The written documentation, however, is not required to be a certificate of good standing. For example: A corporation incorporated in California could go to the California Secretary of State’s website, perform a business entity search on itself, and submit with its Proposal a copy of the record retrieved from that site.

3.5. Financial Capability2. Sufficient evidence of financial capability to meet the

responsibilities to perform the contract which may include balance sheets, income statements, financial statements, independent financial compilation/review or other financial information whereby University can determine Proposer’s credit rating or financial capability. It will be at University’s sole discretion to determine if evidence submitted is sufficient to determine financial capability or to deem a Proposer responsible to perform under a contract. University reserves the right to request further information as needed for clarification purposes. The successful Proposer to which the contract is awarded may, at the discretion of University, be required to provide periodic (in no case more than two times per year) updates to the financial capabilities report submitted pursuant to this RFP.

3.6. Qualifications.

3.6.1. Evidence that Proposer has at least five years of experience in providing similar

services to those enumerated in this RFP, including the completion of at least one UI 2 University does not require audited financial documents or extensive proof of one’s financial capability. With respect to corporate entities or LLCs, a proposer may submit An independent financial compilation or report generally prepared by an accountant applying accounting and financial reporting expertise to assist the entity in preparing financial statements and reports without undertaking to obtain or provide any assurance that there are no material modifications that should be made to the financial statements in order for them to be in accordance with the applicable financial reporting framework. The report is completed in accordance with Statements on Standards for Accounting and review Services promulgated by the Accounting and Review Services Committee of the AICPA (American Institute of Certified Public Accountants). It is not an audited statement or a verification of the accuracy of the information provided. In the case of small, sole proprietorships, one may submit proof of confirmation of self-employment status, verification of income from self-employment, a statement of assets, credit references, a current bank statement, and/or a current credit report. This list is not exclusive as University will independently evaluate all documentation received from a proposer.

Page 15: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 15 of 24

modernization project that included design, development, and implementation of similar technologies and operational components. (E)

3.6.2. Evidence that Proposer has at least three years of demonstrated experience in

providing follow up support and training. 3.6.3. A description of Proposer’s experience in working with institutions of higher

learning in connection with the providing of similar and services to that described in this RFP. (E)

3.6.4. A list of three clients and contact information for whom similar projects have been

completed by Proposer within the past five years. These clients may be contacted by University for an evaluation and assessment of the Proposer's performance. (E)

3.6.5. A list of key personnel who will be providing the services described in this RFP.

This list should contain each individual’s name, title, qualifications, areas of expertise, experience with projects of similar scope and nature, and concise business biography or resume.

3.6.6. A full description of full description of (i) how Proposer will approach this project,

and (ii) how Proposer will deliver the services identified in Sections 2 this RFP. (E)

3.6.7. A list of any and all third parties and/or subcontractors that Proposer intends to or

may use in connection with its performance of the services described in this RFP. 3.6.8. A description of how Proposer intends to implement the services described in this

RFP. (E) 3.6.9. A proposed timeline with a breakdown of time allotted for delivery of the services

described in this RFP. (E) 3.6.10. An itemized budget of costs as well as total price for the goods and services

contemplated under this AP. If Respondent is proposing an hourly rate for any services, the Response must include a not-to-exceed amount as well as the hourly rate. The costs include recurring costs such as internal and external labor and/or subcontracts, all maintenance, service and subscription costs. The costs also include non-recurring costs such as travel expenses e.g., airfare, lodging, and meals, and other miscellaneous expenses related to the provision of on-site services. Similarly, expenses related to providing on-site services e.g., computer, printer, and miscellaneous equipment, must be included in the proposed cost – in other words, the out-of-pocket costs Proposer has to pay to perform the services described in this RFP. (E)

3.7. Representations, Certifications and Acknowledgements. Proposer must submit a

completed and signed Representations, Certifications and Acknowledgments. A blank form of the Representations, Certifications and Acknowledgements for you to complete, sign, and submit is attached to this RFP as Exhibit A.

Page 16: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 16 of 24

3.8. Acknowledgement of Addenda. Proposer must acknowledge that Proposer has

received, reviewed, and agrees to all of the terms conditions added to this RFP via any and all Addenda that are posted on the University’s Purchasing and Contracting Services (PCS) website. Any Addenda including, without limitations, extensions of the Closing Date and Time will be posted on the PCS website, under “Business Opportunities,” accessible at:

http://pcs.uoregon.edu/content/business-opportunities

Proposers are responsible for monitoring the PCS website on a periodic basis for any

and all modifications to this RFP.

3.8.1. Addenda Posted Prior to Proposer’s Submission of Proposal. Proposer must either (i) check the “Acknowledgement of Addenda” box on the Representations, Certifications and Acknowledgments, or (ii) sign and submit a copy of each Addendum.

3.8.2. Addenda Posted After Proposer’s Submission of Proposal. If Proposer has already submitted a Proposal, Proposer may (i) modify the previously submitted Proposal (in accordance with the procedures set forth in Section 4 below) to include a signed copy of each Addendum not previously acknowledged, or (ii) withdraw the previously submitted Proposal (in accordance with the procedures set forth in Section 4 below).

4. PROPOSER INSTRUCTIONS AND PROPOSAL PROCEDURES

4.1. Overview. Proposer MUST comply with all Proposal procedures and follow all Proposer

instructions set forth in this Section.

4.2. Requests for Clarification or Change.

4.2.1. Timing. Requests for clarifications, changes or protests of solicitation specifications or contract provisions must be received by University, in writing, no later than seven calendar days prior to the Closing Date and Time. No requests for change or protests of solicitation specifications or contract provisions will be considered after the deadline stated above.

4.2.2. Requirements. If requesting changes or protests, such requests for change or

protests will include the reasons for the request for change or protest, and proposed changes to specifications or provisions. Envelopes or e-mails containing requests for change or protest must be marked SOLICITATION SPECIFICATION REQUEST FOR CHANGE or CONTRACT PROVISION PROTEST, and must identify the RFP Title, RFP Number and the Closing Date and Time. University reserves the right to amend this RFP, extend the Closing Date and Time, or deny the request or protest.

4.2.3. Proposer Requests Not Addenda. Only documents issued as Written Addenda

by University serve to change the RFP in any way. No other direction received by

Page 17: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 17 of 24

the Proposer, written or verbal, serves to change the RFP. University will post Addenda on the PCS website.

4.3. Proposal Preparation.

4.3.1. Completeness. Unless Proposers are specifically authorized by this RFP to take

exceptions or to leave terms open to negotiation, Proposals will be a complete offer and will be subject to the terms of this RFP. Proposals must include all information required herein to be fully responsive to this RFP and to be evaluated and considered for award. Failure to do so may be deemed sufficient cause for rejection of the Proposal as “non-responsive.”

4.3.2. Organization. Proposal responses must follow the organization and format

described in this RFP. Proposal responses must clearly identify the question or request to which the Proposer is addressing and restate the Section number with each response. All responses must be organized in the order in which the question or request was presented in the RFP. Proposals that do not follow the format described in this RFP may at University’s sole discretion be deemed “non-responsive,” and receive no further consideration.

4.3.3. Writing and Signature. Proposals must be in writing and must be signed by an

authorized representative of the Proposer. Alterations or erasures must be initialed in ink by the person signing the Representations, Certifications and Acknowledgments. No verbal Proposals will be accepted.

4.4. Proposal Submission.

4.4.1. Form. Proposals may be submitted manually or electronically.

4.4.1.1. Electronic Submissions. Proposers are encouraged to submit their Proposals

electronically to the e-mail address provided on the cover page and in Section 1, above. The subject line must clearly state that it is a “PROPOSAL”, noting the RFP Title, RFP Number, and the Closing Date and Time. Electronic Proposals must be in MS Word or Excel. Supporting documentation such as graphics, pictures, and financial statements may be in .pdf or other appropriate format. Do not submit electronic copies through use of a Drop Box account or other such Web or cloud based product. All Proposals submitted electronically must be submitted by individuals with authority to legally bind the Proposer.

4.4.1.2. Manual Submissions. Proposers submitting manually must submit two (2)

copies of their Proposal, as well as an electronic version on CD or USB device. All manual submissions must be submitted in a sealed envelope appropriately marked. All envelopes in which the RFP, Representations, Certifications and Acknowledgments, and Proposal are submitted MUST be clearly marked “PROPOSAL”, noting the RFP Title, RFP Number, and the Closing Date and Time. All manual submissions will be made to the address as indicated in Section 1 of this RFP.

Page 18: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 18 of 24

4.4.2. Consistency. Proposers are strongly encouraged to utilize the same method of submission, either manual or electronic, throughout the solicitation process (e.g. if your Proposal was submitted electronically, Proposers are encouraged to submit modifications and requests to withdraw via e-mail; if your Proposal was submitted manually, requests for modification or withdrawal should be submitted manually).

4.4.3. Receipt of Proposal by University. All Proposals must be received by

University’s Issuing Office by the Closing Date and Time. Postmarks will not be considered.

It is Proposer’s responsibility to ensure that the Proposal is received by University at the required delivery point (as indicated in Section 1 of this RFP), prior to the Closing Date and Time, regardless of method used to submit the Proposal.

University will not be responsible for the proper identification and handling of Proposals not submitted in the designated manner or format as required by this RFP.

4.5. Proposer’s Costs. University is not responsible for any costs of Proposers incurred in connection with submitting or presenting a Proposal. All Proposers who respond to solicitations do so solely at their own expense.

4.6. Binding Offer. Submission of a Proposal constitutes a firm, binding and irrevocable

offer for a period of three months following the Closing Date and Time. 4.7. Modification of Proposal by Proposer. Proposers may modify a previously submitted

Proposal prior to the Closing Date and Time. Modifications must be made in writing and signed by an authorized representative. Modifications may be submitted manually or electronically. The envelope or e-mail subject line must be clearly marked “PROPOSAL MODIFICATION,” and must display the RFP Title, RFP Number, and the Closing Date and Time. Verbal modifications or corrections will not be recognized or considered.

4.8. Withdrawal of Proposal by Proposer. Proposals may be withdrawn at any time prior

to the scheduled Closing Date and Time. Withdrawal can only be accomplished by written notification, signed by an authorized representative. Notification of withdrawal may be submitted manually or electronically. The written notification must be received by University prior to the Closing Date and Time. The envelope or e-mail subject line must be clearly identified with the words “PROPOSAL WITHDRAWAL,” and must display the RFP Title, RFP Number, and the Closing Date and Time.

4.9. Public Records / Property of University. All Proposals submitted in response to this

RFP become the property of University. By submitting a Proposal in response to this RFP, Proposer grants the University a non-exclusive, perpetual, irrevocable, royalty-free license for the rights to copy, distribute, display, prepare derivative works of and transmit the Proposal solely for the purpose of evaluating the Proposal, negotiating a contract, if awarded to Proposer, or as otherwise needed to administer the RFP process, and to fulfill obligations under Oregon Public Records Laws. Proposals, including supporting materials, will not be returned to Proposer.

Page 19: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 19 of 24

4.10. Trade Secrets. This RFP and one copy of each original Proposal received in response

to it, together with copies of all documents pertaining to the award of a contract, will be retained by requesting University department for the required retention period, and made a part of a file or record which will be open to public inspection. If a Proposal contains any information that is considered a "trade secret" under ORS 192.501(2), the Proposer must provide an alternative copy of its Proposal with any specific text, drawings, or other markings that are considered a “trade secret”, if any, clearly marked or redacted, and also mark each sheet that contains such information in the Proposal with the following legend:

"This data constitutes a trade secret under ORS 192.501(2), and will not be disclosed except in accordance with the Oregon Public Records Law, ORS Chapter 192."

Failure to provide a marked alternative copy or mark the Proposal as required in this Section will conclusively establish that the information on that page does not constitute a trade secret as defined in ORS 192.501(2).

The Oregon Public Records law exempts from disclosure only bona fide trade secrets, and the exemption from disclosure applies "unless the public interest requires disclosure in the particular instance". See ORS 192.501(2). As such, non-disclosure of documents or any portion of a document submitted as part of a Proposal may depend upon official or judicial determinations made pursuant to the Public Records Law.

Proposals in which the entire document is marked or otherwise identified in its entirety as confidential or a “trade secret” may be rejected. If the Proposal is not rejected, the response will be deemed available for disclosure to the public.

4.11. University’s Right to Amend. University reserves the right, at its option, to amend this RFP. Any Addenda including, without limitations, extensions of the Closing Date and Time will be posted on the PCS website, under “Business Opportunities,” accessible at http://pcs.uoregon.edu/content/business-opportunities . Proposers are responsible for monitoring the PCS website on a periodic basis for any modifications to the RFP. University is not required to issue individual notifications.

4.12. University’s Right to Reject. University reserves the right, at its option, to reject any

or all Proposals. Notification of Proposal rejection will be made in writing. University reserves the right to waive minor informalities and irregularities in Proposals.

4.13. University’s Right to Cancel. University reserves the right, at its option, to cancel this

RFP.

5. EVALUATION AND AWARD

5.1. Evaluation by Committee. Proposals will be evaluated by a committee consisting of representatives of the requesting University department, and/or other interested individuals, as University deems appropriate (“Committee”).

Page 20: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 20 of 24

5.2. Initial Evaluation.

5.2.1. Completeness and Compliance of Proposal. Proposals will be evaluated for

completeness and compliance with the mandatory requirements of this RFP. Those Proposals that meet Mandatory (M) requirements are considered “responsive”.

Those Proposals which are incomplete, which do not meet all Mandatory (M) requirements of this RFP or are otherwise deemed by University to be "non-responsive," will be rejected.

5.2.2. Responsibility of Proposer. Proposers will be evaluated for their demonstrated ability to perform responsibly under a contract awarded pursuant to this RFP. At the discretion of the University, those Proposers who satisfactorily demonstrate their ability to perform responsibly under a contract awarded pursuant to this RFP are considered “responsible”. Those Proposers who are unable to satisfactorily demonstrate to University that they are able to perform responsibly under a contract awarded pursuant to this RFP are considered “non-responsible.”

5.3. Criteria Evaluation. Responsive Proposals received from responsible Proposers will be further evaluated by the Committee. For each of these Proposals, the Committee will allocate points (up to the designated Maximum Available Points) for the following criteria, and calculate the Proposal’s total score:

Criteria to Be Evaluated Maximum Available Points

1 Required Services (Sections 2.1 and 2.2 of this RFP). 40 Points

2 Qualifications (Sections 3.6.1 – 3.6.4, and 3.6.6 of this RFP). 20 Points

3 Qualifications (Sections 3.6.8 – 3.6.9 of this RFP). 15 Points

4 Qualifications (Section 3.6.10 of this RFP). 20 Points

5 Preference, Minority, Women, Veteran, Emerging Small Business. 5 Points

TOTAL: 100 Points

Except for category 5, and to qualify for further review under this RFP, Proposer must receive a minimum score of 70% of the Maximum Available Points for each enumerated criteria.

Although the general criteria to be used for final evaluation has been provided in this

Page 21: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 21 of 24

RFP; it is not intended to limit imagination or creativity in preparing a Proposal that will accomplish the same goals and expectations.

5.4. Competitive Range Evaluation.

5.4.1. Establishing a Competitive Range. Based on the total scores calculated in

accordance with Section 5.3 above, the Committee may proceed directly to Final Determination, as set forth in Section 5.5 of this RFP. Alternatively, the Committee may establish a range of Proposals which are deemed to have a reasonable likelihood of being selected for award (“Competitive Range”). The Competitive Range is expected to consist of no more than three Proposals; however, University reserves the right to expand or reduce the number of Proposals to be included in the Competitive Range.

University will notify a Proposer if it is in the Competitive Range via the email address provided in the Proposal. If no response is received by University within 24 hours after the notification is sent, a follow-up phone call will be made to the Proposer via the phone number provided in the Proposal. If no response is received by University within 48 hours after the initial notification is sent, the Proposal may be removed from the competitive range. University will provide written notice of such removal to the Proposer.

5.4.2. Evaluating Competitive Range Proposals. Proposers of Proposals within the Competitive Range may be asked to prepare and present a live presentation of their Proposal to be delivered to the Committee at University. The Proposers’ presentations will take place after reasonable notice is given to Proposers by University. Any special accommodations required for the live presentations (technical or otherwise) must be communicated to University at least five days prior to the scheduled presentation. University will make all reasonable efforts to accommodate such requests. The purpose of the live presentations will be to allow the Proposers to provide supplemental information in order to provide clarification of the Proposal contents, as well as to inform the Committee as they recommend a Proposer for ultimate award of the contract under this RFP.

5.4.3. The Committee may also consider and assess other factors, including but not

limited to, any information submitted in response to this RFP; best value; experience working with other organizations, including higher education institutions; references; financial condition of the Proposer; resources of the Proposer; clarifications provided in response to inquiries by University; proposed additional terms for providing the service; and experience of persons assigned to this project. University reserves the right to require a “Best and Final Offer” pursuant to UO Policy 580.061, Sec EE from Proposers within the Competitive Range.

5.4.4. Negotiations. University may commence serial negotiations with the highest-

ranked Proposer or commence simultaneous negotiations with all eligible Proposers. University may negotiate:

• The statement of work.

Page 22: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 22 of 24

• The contract price as it is affected by negotiating the statement of

work.

• Any other terms and conditions determined by University in its sole discretion to be reasonably related to those expressly authorized for negotiation. Accordingly, Proposers will not submit and University will not accept for negotiation, any alternative terms and conditions that are not reasonably related to those expressly authorized for negotiation.

Terms and conditions within any proposed contract may be further negotiated after award, but before legal review or execution of the Contract.

5.5. Final Determination. After considering and assessing all factors it deems relevant, the

Committee will determine how to proceed.

University plans to award this project to the firm or individual who best meets the overall selection criteria detailed in this RFP. University reserves the right to make its final decision based upon the solution that best meets the University’s needs. The lowest cost Proposer may not be awarded a contract.

5.6. Notice of Conditional Award. Any award issued pursuant to this RFP is conditional and subject to successful negotiations and a resulting contract with the apparent successful Proposer. The apparent successful Proposer will be notified in writing of its status and negotiations will commence to achieve a final contract which will include terms and conditions substantially as set forth in the University Standard Terms and Conditions found at http://pcs.uoregon.edu/content/forms. All other Proposers will be notified in writing that the apparent winning Proposal has been selected.

All solicitations, proposals, bids, award information, documents, and notices are

confidential and not subject to public disclosure until a contract is executed with the successful vendor or the procurement is canceled.

University anticipates that the Notice of Conditional Award will be released on or about May 15, 2018 (“Anticipated Award Notice Date”).

5.7. Award Protest. University is not required to post selection or award results though, in its sole discretion, may elect to do so. University does not conduct post-award debriefings. All protests of the selection or award must be made pursuant to the conditions and limitations of UO Policy 580.061, Sec CC. Except as provided in Section 5.6 of this RFP, all procurement documents are public records and may be requested from University’s Office of Public Records at:

https://publicrecords.uoregon.edu. 5.8. Use by Other Public Entities. All public agencies or public higher education institutions

may utilize any contract(s) awarded as a result of this Request for Proposal. The other public agencies and other public higher education institutions shall be individually responsible for their obligations to the awarded contractors(s). Likewise, the contractors

Page 23: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 23 of 24

shall be responsible to the public agencies or public higher education institutions for their obligations to those public agencies or public higher education institutions pursuant to any ensuing contract(s). Any such purchases shall be between the contractor and the participating public agencies or public higher education institutions and shall not impact the vendor’s obligation to University of Oregon. University of Oregon makes no representation or guarantee as to the volume of University of Oregon’s purchases or such additional purchases.

6. CONTRACT AWARD

6.1. Anticipated Term. It is anticipated that the term of the contract awarded under this RFP,

will be for

6.2. Other Public Institutions. All public agencies or public higher education institutions may utilize any contract(s) awarded as a result of this RFP. The other public agencies and other public higher education institutions shall be individually responsible for their obligations to the awarded contractors(s). Likewise, the contractors shall be responsible to the public agencies or public higher education institutions for their obligations to those public agencies or public higher education institutions pursuant to any ensuing contract(s). Any such purchases shall be between the contractor and the participating public agencies or public higher education institutions and shall not impact the vendor’s obligation to University of Oregon. University of Oregon makes no representation or guarantee as to the volume of University of Oregon’s purchases or such additional purchases.

6.3. Separate Contract. The contract award will be pursuant to a separate contract which will include terms and conditions substantially as set forth in the draft contract attached to this RFP as Exhibit B.

6.4. Modification of Form Contract. If you have questions, concerns or proposed modifications regarding any of the terms and conditions contained in this RFP, including the attached form of contract, you must address those during the time prescribed for questions, changes, or protests as set forth in Section 4 above.

6.5. No additional or Supplemental Terms or Conditions. Additional or supplemental terms and conditions submitted by a Proposer as part of its response may be evaluated or considered at the sole discretion of University. If additional or supplemental terms and conditions, either intentionally or inadvertently appear separately in a Proposal (e.g. in transmittal letters, specifications, literature, price lists or warranties), it is understood and agreed that the terms and conditions contained in this RFP are the only terms and conditions applicable to this RFP and any ensuing contract, and the Proposer’s authorized signature affixed to its Proposal attests to this.

If you condition your Proposal on any additional terms and conditions, which have not been accepted by a written Addendum to the RFP, your Proposal may be deemed non-responsive.

6.6. University Review. A final contract is conditioned upon the successful negotiation of contract terms. Proposers agree that University will have the right to negotiate, review

Page 24: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Page 24 of 24

and/or require modification of any terms or definitions used in the final contract. Failure to agree to the terms and conditions of a contract may result in cancellation of the intended award.

Page 25: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit A - Page 1 of 2

EXHIBIT A

RFP for User Interface Design Developers:

Website Redesign PCS# 2260000-01273-RFP

(Must Complete, Sign and Submit with your Proposal by the Closing Date and Time)

REPRESENTATIONS, CERTIFICATIONS, AND ACKNOWLEDGEMENTS

By submitting this Proposal in response to this RFP, Proposer represents and warrants that:

1. Proposer has read all of the terms and conditions of this RFP; Proposer understands that by signing below and submitting a Proposal, if awarded the contract, Proposer will be bound by the terms and conditions of this RFP and its Proposal.

2. Prices proposed shall be firm for three months after the Closing Date and Time; and, if awarded the contract, Proposer must furnish any and all goods and/or services at the prices offered within the terms and time specified.

3. Proposer has the power and authority to enter into and perform the contract awarded as a result of this RFP.

4. The individual signing for Proposer is authorized to execute this Proposal on behalf of Proposer.

5. Proposer is an independent contractor and not an employee, partner, or agent of University.

6. Proposer’s name, as it appears in this Proposal, is Proposer’s legal name, as it will appear in the Proposer’s W-9, and if Proposer is an entity rather than an individual that the entity named in this Proposal is validly-existing and in good standing.

7. Proposer has not discriminated against Historically Underrepresented Businesses (defined in UO Policy 580.061, Sec B in obtaining any required subcontracts.

8. No officer, agent or employee of University has participated on behalf of University in preparation of the Proposal, that the Proposal is made in good faith, without fraud, collusion, or connection of any kind with any other proposer for the same work, and that the Proposer is competing solely on Proposer’s own behalf without connection with, or obligation to any undisclosed person or firm.

Acknowledgment of Addenda

By checking this box, Proposer acknowledges Proposer has received, reviewed, and agrees to the all terms and conditions added to this RFP via any Addenda that were posted on the PCS website, under “Business Opportunities,” accessible at:

http://pcs.uoregon.edu/content/business-opportunities.

Page 26: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit A - Page 2 of 2

Business Designation (check one):

Corporation Partnership Sole Proprietorship

Governmental/Non-profit Limited Liability Company

Please indicate your Minority Women or Emerging Small Business (MWESB) Status:

Women Owned Self Report State Certified #

Minority Owned Self Report State Certified #

Emerging Small Business Self Report State Certified #

None of the Above

Signature: ______________________________________________

Dated: ______________________________________________

Name: ______________________________________________

Title: ______________________________________________

Firm: ______________________________________________

Address: ______________________________________________

______________________________________________

______________________________________________

E-mail: ______________________________________________

Phone: (____) ______________

Above information must be provided prior to the Closing Date and Time for the Proposal to be considered responsive.

Page 27: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 1 of 14

EXHIBIT B

RFP for User Interface Design Developers: Website Redesign

PCS# 2260000-01273-RFP

PROPOSED SOFTWARE DEVELOPMEMNT AGREEMENT RFP/AP/RFQ for

TEMPLATE ONLY

NOT TO BE SIGNED

(PCS# [ ])

This Agreement (Agreement) is made and entered into by and between the University of Oregon (University) and [ ], (Consultant), a [ ] organized under the laws of the State of Delaware and authorized to do business in the State of Oregon. University and Consultant are each “Party” and collectively “Parties. RECITALS A. On [ ], University issued a Request for Proposal (RFP) to select a vendor to [ ].

B. On [ ], Consultant submitted its timely proposal. Consultant is the successful proposer

to the RFP.

C. Consultant represents it has the requisite skill, experience and qualifications to perform the services and work as described under this Agreement.

D. University and Consultant wish to enter into this Agreement for work. AGREEMENT In consideration of the above Recitals, which are incorporated into this Agreement, the mutual promises contained in this Agreement and for other good and valuable consideration, the receipt and sufficiency of which is acknowledged by the Parties, the Parties agree as follows: 1. This Agreement is comprised of the following documents:

a. This Agreement along with all exhibits, attachments and/or appendices. b. The Request for Proposal (RFP) [PCS#] c. Consultant’s Proposal (Proposal) in response to the RFP.

Page 28: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 2 of 14

2. Statement of Work.

Consultant will perform the services and provide the work described RFP as it is again set forth in Exhibit A, Statement of Work, which is incorporated by reference. 3. Invoicing and Payment.

Consultant will invoice University and University will pay Consultant in accordance with the invoicing instructions and payment terms included on Exhibit B, “Invoicing and Payment,” which is incorporated by reference. Absent a written and signed amendment to this Agreement, the total compensation under this Agreement, including any reimbursable expenses, will not exceed $ [ ]. 4. Term.

4.1 This initial term of this Agreement will be for a period of [ ] commencing on [ ] or on the date last signed, whichever is later (“Effective Date”). 4.2 At its sole discretion, University may renew this Agreement for [ ] additional [ ] terms. All of the terms and conditions of this Agreement will apply to any renewal terms except fees. The number of renewal term options exercised will be reduced by the number already exercised. Fees for each renewal term may increase by the lesser of the yearly increase of the Consumer Price Index published by the U.S. Bureau of Labor Statistics of the U.S. Department of Labor or three percent. Comparisons shall be made using the index entitled “All Urban Consumers: Portland-Salem, OR-WA” or the nearest comparable data on changes in the cost of living, if such index is no longer published. The change shall be determined by comparison of the figure for a date which is twelve months prior to the adjustment date. 5. Insurance.

Consultant will secure at Consultant’s expense and keep that insurance in effect during the term of this Agreement either comprehensive general liability insurance with a broad form CGL endorsement or broad form commercial general liability insurance with a minimum combined single limit of not less than $1,000,000 for each occurrence and $2,000,000 aggregate, covering bodily injury and property damage, and will include personal and advertising injury liability, products liability, professional negligence and contractual liability coverage for the indemnity provided under this Agreement. Consultant’s professional liability insurance will contain provisions for coverage of allegations of corporal punishment, sexual abuse, and molestation. Consultant will secure at Consultant’s expense and keep that insurance in effect during the term of this Agreement, professional liability insurance with a combined single limit, or the equivalent, of not less than $2,000,000 per occurrence and $5,000,000 aggregate. This is to cover damages caused by error, omission, ore negligent acts related to the professional services to be provided under this Contract. If this insurance is arranged on a “claims made” basis, “tail” coverage will be required at the completion of this Contract for a duration of 24 months.

Page 29: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 3 of 14

Upon request, Contractor agrees to purchase and maintain throughout the term of this Agreement a technology/professional liability insurance policy, including coverage for network security/data protection liability insurance (also called “cyber liability”) covering liabilities for financial loss resulting or arising from acts, errors, or omissions, in rendering technology/professional services or in connection with the specific services described in this Agreement: Violation or infringement of any right of privacy, including breach of security and breach of security/privacy laws, rules or regulations globally, now or hereinafter constituted or amended; Data theft, damage, unauthorized disclosure, destruction, or corruption, including without limitation, unauthorized access, unauthorized use, identity theft, theft of personally identifiable information or confidential corporate information in whatever form, transmission of a computer virus or other type of malicious code; and participation in a denial of service attack on third party computer systems; Loss or denial of service; No cyber terrorism exclusion; with a minimum limit of $5,000,000 each and every claim and in the aggregate. Such coverage must include technology/professional liability including breach of contract, privacy and security liability, privacy regulatory defense and payment of civil fines, payment of credit card provider penalties, and breach response costs (including without limitation, notification costs, forensics, credit protection services, call center services, identity theft protection services, and crisis management/public relations services). Such insurance must explicitly address all of the foregoing without limitation if caused by an employee of [Service Provider] or an independent contractor working on behalf of Contractor in performing services under this Agreement. Policy must provide coverage for wrongful acts, claims, and lawsuits anywhere in the world. Such insurance must include affirmative contractual liability coverage for the data breach indemnity in this Agreement for all damages, defense costs, privacy regulatory civil fines and penalties, and reasonable and necessary data breach notification, forensics, credit protection services, public relations/crisis management, and other data breach mitigation services resulting from a breach of confidentiality or breach of security by or on behalf of Contractor. Upon request by University, Consultant will secure at Consultant’s own expense and keep in effect during the term of this Agreement a Commercial Auto Liability insurance policy with a minimum combined single limit of $1,000,000 per occurrence for each accident and $2,000,000 aggregate. Any requested insurance policies are to be issued by an insurance company authorized to do business in the State of Oregon with a minimum financial rating of an AM Best rating of A- or higher. All liability insurance will be arranged on an “occurrence” basis. No insurance will be allowed on a “claims made” basis. If insurance is required by this Agreement, upon request by University, Consultant must provide a Certificate of Insurance to University from the insuring company evidencing insurance coverage required by this Agreement. The “Description of Operations” must include (using the following exact language) the “State of Oregon, Board of Trustees of the University of Oregon, University of Oregon, and their respective officers, employees, and members” as additional insured. Upon request, Consultant must also provide an endorsement to University from the insuring company, naming (using the following exact language) the “State of Oregon, Board of Trustees of the University of Oregon, University of Oregon, and their respective officers, employees, and members” as additional insured.

Page 30: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 4 of 14

There shall be no cancellation, material change, reduction of limits or intent not to renew the insurance coverage(s) without 30-days' written notice from Consultant or its insurer(s) to University, Contracts Manager at the following address: 1600 Millrace Drive, Suite 306, Eugene, Oregon 97403- 1995 6. Notices.

Except as otherwise expressly provided in this Agreement, any communications between the Parties or notices to be given under this Agreement will be given in writing by personal delivery, facsimile, email, or mailing the same, postage prepaid, to Consultant or University at the address or number as set forth in this Agreement, or to such other addresses or numbers as either Party may indicate. Any communication or notice so addressed and mailed will be deemed to be received five days after mailing. Any communication or notice delivered by facsimile will be deemed to be given when receipt of the transmission is generated by the transmitting machine. To be effective against University, such facsimile transmission must be confirmed by telephone notice to University's representative. Any communication or notice by personal delivery will be given when actually delivered. Any communication or notice by email will be given when the recipient, by an email sent to the email address for the sender stated in this section or by a notice delivered by another method in accordance with this section, acknowledges having received that email, with an automatic “read receipt” not constituting acknowledgment of an email for purposes of this section. All notices shall be addressed to the parties at the following addresses or at such other addresses as the parties may from time to time direct in writing: UNIVERSITY: [ ] With a copy to:

Purchasing and Contracting Services 1600 Millrace Drive, Suite 306 Eugene, OR 97403-1005 Fax: (541) 346-2425 [email protected] CONSULTANT: [ ]

7. Standard Terms and Conditions.

University’s Terms and Conditions of this Agreement are attached as Exhibit C and incorporated herein.

Page 31: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 5 of 14

8. Attachments. All exhibits, attachments, addenda, and schedules which are referred to in this Agreement are incorporated in this Agreement. IN WITNESS WHEREOF, the Parties have entered into this Agreement.

UNIVERSITY

By:

Signature: _________________________________________

Date: _________________________________________

CONSULTANT

By: _________________________________________

Signature: _________________________________________

Date: _________________________________________

Page 32: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 6 of 14

CONSULTANT AGREEMENT STATEMENT OF WORK

(PCS# [ ]) EXHIBIT A TO TEMPLATE

The following services and work are to be provided by the Consultant:3

General Obligations of Consultant.

Specific Obligations of Consultant.

CONSULTANT AGREEMENT

INVOICING AND PAYMENT SCHEDULE (PCS# [ ]-PSC)

EXHIBIT B TO TEMPLATE INVOICING:

[TO BE COMPLETED]

3 The Parties acknowledge that the services and work to be performed under this Agreement may be adjusted as certain data and variables are ascertained. The services and work enumerated herein are designed to define the primary responsibilities of Consultant and correspond to those identified in the RFP and Consultant’s Proposal to the RFP.

Page 33: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 7 of 14

CONSULTANT AGREEMENT

UNIVERSITY TERMS AND CONDITIONS (PCS# [ ]-PSC)

EXHIBIT C TO TEMPLATE 1. DEFINITIONS: (i) “Agreement” and "Contract" mean the entire written purchase order, contract, or agreement attached to these University Standard Terms and Conditions (“Standard Terms”), these Standard Terms, and any other contracts, agreements, sales quotations, order acknowledgements, or similar documents including terms and conditions incorporated in the Contract; (ii) "ORS” means the Oregon Revised Statutes; "OAR" means Oregon Administrative Rules; “UCC” means Uniform Commercial Code; “USC” means United States Code; (iii) “Deliverables” means goods and/or services provided to University by Consultant under this Contract; (iv) "University" and “UO” each mean the University of Oregon, making the purchase pursuant to this Contract, and mean an Oregon Cooperative Procurement Program (“OrCPP”) member if the purchase is being made under the State of Oregon’s cooperative purchasing program authorized by ORS 190.240; (v) "Consultant" means the party named in Contract with whom University has contracted for the purchase of goods or goods and services; (vi) “Unsupervised Contact” with minor students means contact that provides the person opportunity and probability for personal communication or touch with students under the age of 18 when not under direct University supervision; and (vii) University and Consultant are each a “Party” and collectively “Parties”. 2. CONTROLLING TERMS. These Standard Terms shall govern the Contract between the Parties and replace and supersede any conflicting terms and conditions found in the Contract, the RFP, and the Proposal. 3. INDEMNITY. Consultant will be responsible for all damage to property, injury to persons, loss, expense, inconvenience, attorney’s fees, and delay (“Harm”) which may be caused by, or result from, any act or omission of Consultant, its subcontractors, agents, or employees. Consultant will defend, indemnify and hold University harmless, as well as University’s governing board, trustees, directors, officers, agents, employees, and members, with respect to all claims, suits, and actions of any nature, or alleging Harm of any nature, resulting from or arising out of the acts or omissions of Consultant or its subcontractors, officers, agents, or employees. The University has no obligation to and will not indemnify, defend, or hold Consultant harmless with respect to any act or omission, or any Harm resulting therefrom, of the University, its governing board, trustees, directors, officers, agents, employees, and members.

4. INDEMNITY FOR INFRINGEMENT CLAIMS. Except to the extent arising from materials or modifications provided or made by University, which materials are utilized by Consultant in their unaltered form, and without limiting the generality of the indemnification clause above, Consultant expressly agrees to indemnify and hold University harmless, as well as University’s directors, officers, employees, and agents, from and against any and all claims, suits, actions, losses, liabilities, costs, expenses, and damages arising out of or related to any claims that the Deliverables infringe any patent, copyright, trade secret, trademark, trade dress, mask work, utility design, or other proprietary right of any third party. In the event that a court of competent jurisdiction

Page 34: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 8 of 14

determines in a final, non- appealable order that the work is infringing in a manner for which Consultant is obligated to indemnify University pursuant to this Section, Consultant will, at its option: (1) procure for University the right to continue using such infringing work; (2) replace the infringing work with a non-infringing item of like form, fit or function; or (3) modify the work so that it no longer infringes.

5. UNSUPERVISED CONTACT WITH MINOR STUDENTS. Consultant shall ensure that none of its officers, employees, or agents, including subcontractors, will have direct, Unsupervised Contact with minor students while on University property. Consultant will work with University to ensure compliance with this requirement. If Consultant is unable to ensure through a security plan that none of its officers, employees, or agents, including subcontractors, will have direct, Unsupervised Contact with minor students in a particular circumstance or circumstances, then Consultant shall notify University before beginning any work that could result is such contact. Consultant authorizes University to obtain information about Consultant and its history and to conduct a criminal background check, including fingerprinting, of any Consultant officers, employees, or agents, including subcontractors, who will have Unsupervised Contact with minor students. Consultant shall cause its officers, employees, agents, including subcontractors, if any, to authorize University to conduct these background checks. Consultant shall pay all fees assessed by University for processing the background check. University may deduct the cost of such fees from an interim or final payment to Consultant under this Contract, unless Consultant elects to pay such fees directly. 6. INDEPENDENT CONTRACTOR STATUS. Any services rendered under this Contract are those of an independent contractor. Consultant certifies that Consultant is not an employee of the University and neither Consultant nor any of Consultant's agents or employees are entitled to any of the benefits that University provides for its employees. Nothing in this Contract will be construed to create a partnership, joint venture, franchise, agency, or employment relationship between the Parties. 7. OWNERSHIP OF WORK PRODUCT. All Deliverables that result from this Contract (“Work Product”) are the exclusive property of University. University and Consultant intend that such Work Product be deemed "work made for hire" of which University will be deemed the author. If, for any reason, the Work Product is not deemed "work made for hire", Consultant irrevocably assigns to University all its rights, title, and interest in, and to any and all of the Work Product, whether arising from copyright, patent, trademark, trade secret, or any other state or federal intellectual property law or doctrine. Consultant will execute such further documents and instruments as University may reasonably request in order to fully vest such rights in University. Consultant forever waives any and all rights relating to the Work Product, including without limitation, any and all rights arising under 17 USC 106A or any other rights of identification of authorship or rights of approval, restriction or limitation on use or subsequent modifications.

8. EXCLUSIVITY. University is not bound by exclusivity provisions. 9. REPRESENTATIONS AND WARRANTIES. Consultant represents and warrants that (1) Consultant has the power and authority to enter into and perform this Contract; (2) The individual signing for Consultant is authorized to execute this Contract on behalf of Consultant; (3) This Contract, when executed and delivered, will be a valid

Page 35: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 9 of 14

and binding obligation of Consultant, enforceable in accordance with its terms; (4) The work under this Contract will be performed in a good and workmanlike manner and in accordance with the highest professional standards; (5) Consultant will, at all times during the term of this Contract, be qualified, professionally competent, and duly licensed to perform the work; and (6) Consultant’s name, as it appears in this Contract, is Consultant’s legal name, as it will appear in Consultant’s W-9, and if Consultant is an entity rather than an individual, that the entity named in this Contract is validly existing and in good standing. Unless otherwise stated in the Contract, all Deliverables will be new and current models and will carry full manufacturer warranties. Consultant warrants all Deliverables delivered to be free from defects in labor, material, and manufacture and to be in compliance with solicitation specifications. All implied and expressed warranty provisions of the UCC (ORS chapter 72) are incorporated in this Contract. All warranties will inure to the benefit of University. The warranties set forth in this Section are in addition to, and not in lieu of, any other warranties provided. 10. ACCEPTANCE. Deliverables furnished under this Contract will be subject to acceptance by University. If University finds the Deliverables furnished to be incomplete or not in compliance with solicitation specifications, University may reject the Deliverables and require Consultant to either correct them without charge, or provide them at a reduced price, at University’s discretion. If Consultant is unable or refuses to cure any defects in the provided Deliverables within a time deemed reasonable by University, University may reject the Deliverables and cancel this Contract in whole or in part. Nothing in this paragraph will in any way affect or limit University's rights as buyer, including the rights and remedies relating to rejection under ORS 72.6020 and revocation of acceptance under ORS 72.6080.

11. TERMINATION. (a) This Contract may be terminated at any time by mutual written consent of both Parties. (b) University may, at its sole discretion, terminate this Contract in whole or in part upon 30-days’ written notice to Consultant. (c) University may terminate this Contract effective immediately upon delivery of written notice to Consultant, or at such later date as may be established by University if: (i) Consultant is in violation of applicable federal, state, or local laws, rules, regulations, ordinances, or guidelines or any University policy (found at http://policies.uoregon.edu/) (“Applicable Laws”), including, but not limited to any policy related to sexual harassment and sexual misconduct (ii) Applicable Laws are modified or interpreted in such a way that any Deliverables or services to be provided by Consultant under this Contract are no longer allowable or appropriate for purchase by University or are no longer eligible for the funding proposed for payment authorized by this Contract; (iii) any license or certificate required by Applicable Laws to be held by Consultant to provide Deliverables under this Contract is denied, revoked, or not renewed for any reason; (iv) if Consultant becomes insolvent or admits in writing its inability to pay its debts as they mature, or makes an assignment for the benefit of creditors; (v) if a petition under any foreign, state, or United States bankruptcy act, receivership statute, or the like, as they now exist, or as they may be amended, is filed by Consultant; or (vi) if such a petition is filed by any third party, or an application for a receiver is made by anyone and such petition or application is not resolved favorably to Consultant within ninety (90) calendar days. (d) University may terminate this Contract for default (including breach of contract) if (i) Consultant fails to provide Deliverables called for by this Contract within the time specified in this Contract

Page 36: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 10 of 14

or any extension of this Contract; or (ii) Consultant fails to perform any of the other provisions of this Contract, or so fails to pursue the work as to endanger performance of this Contract in accordance with its terms, and after receipt of notice from University, fails to correct such failures within ten business days. (e) Consultant may terminate this Contract upon 30-days’ written notice to University if University fails to pay Consultant pursuant to the terms of this Contract and University does not cure such failure to pay within 30-business days after receipt of Consultant's written notice, or such longer period as Consultant may specify. 12. TERMINATION DUE TO NONAPPROPRIATION OF FUNDS. University may terminate this Contract upon written notice to Consultant if University has not: (a) Received from the Oregon Legislative Assembly appropriations, limitations, or other expenditure authority; or (b) Received allotments pursuant to ORS Chapter 291 sufficient to allow University, in the exercise of its reasonable administrative discretion, to pay the amounts of this Contract. 13. REMEDIES. (a) Consultant's sole remedy under this Contract will be a claim for the sum designated for providing and/or completing the Deliverables multiplied by the percentage of Deliverables provided and/or completed and accepted by University, less previous amounts paid and any claim(s) which University has against Consultant. If previous amounts paid to Consultant exceed the amount due to Consultant under this subsection, Consultant will pay any excess to University upon demand. (b) University’s remedies under this Contract include any remedy available to it in law or equity. If it is determined for any reason that Consultant was not in default of this Contract pursuant to Section 12(d), the rights and obligations of the Parties will be the same as if the Contract was terminated pursuant to Section 12(b). (c) Upon receiving a notice of termination of this Contract, Consultant will immediately cease all activities under this Contract, unless University expressly directs otherwise in writing. Upon termination of this Contract, Consultant will deliver to University all Work Product, documents, information, works-in-progress and other materials that are or would be Deliverables or otherwise the property of University had the Contract been completed. Upon University's request, Consultant will surrender to anyone University designates, all documents, research or objects or other tangible things needed to complete the work. 14. SUBCONTRACTS AND ASSIGNMENTS. Notwithstanding any provision to the contrary, Consultant may not subcontract, assign, transfer, or any of its interest in this Contract or delegate its responsibilities without obtaining prior written approval from University, such consent may be withheld by University in its sole discretion. As a condition to requesting prior written approval, Consultant must provide a written copy of any such proposed assignment or subcontract to University. University's consent to any assignment or subcontract will not relieve Consultant of any of its duties or obligations under this Contract. Any assignment or subcontract in contravention of this Section will be null and void. This Contract will be binding upon and will inure to the benefit of the Parties and their respective authorized successors and assignees.

15. CONFLICT OF INTEREST. Consultant covenants that it presently has no

interest and will not acquire any interest, direct or indirect, which would conflict in any manner with or prohibit Consultant’s full performance of this Contract. Consultant also covenants that in the performance of this Contract no person having any such interest

Page 37: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 11 of 14

will be employed. Consultant further covenants that its performance of this Contract will not cause any employee or volunteer of University to violate ORS Chapter 244. 16. ACCESS TO RECORDS. Consultant will maintain records, sufficient to accurately document its performance of this Contract, including, but not limited to costs claimed to have been incurred and anticipated to be incurred. University and, if applicable, the federal government will have access to the records of Consultant for the purpose of determining compliance with this Contract. Consultant will retain all such records, for a minimum of six years following final payment under or termination of this Contract, or such longer period as may be required by Applicable Laws or to conclude any audit, review, or controversy. 17. OREGON PUBLIC RECORDS LAW. Consultant hereby acknowledges this this Contract is subject to the requirements of Oregon public records law (ORS 192.410 – 192.505) and that information Consultant discloses to University may be subject to public disclosure. University is not in breach of any provision of the Contract if, according to the University’s interpretation of public records law, it discloses or maintains records of any information provided by the Consultant.

18. UNIVERSITY DATA.

18.1. OWNERSHIP. University’s data (“University Data,” which shall also be known and treated by

Service Provider as Confidential Information) shall include: (a) University’s data collected, used, processed, stored, or generated as the result of the use of the Services; and, (b) personally identifiable information (“PII“) collected, used, processed, stored, or generated as the result of the use of the Services, including, without limitation, any information that identifies an individual, such as an individual’s social security number or other government-issued identification number, date of birth, address, telephone number, biometric data, mother’s maiden name, email address, credit card information, or an individual’s name in combination with any other of the elements listed herein. University Data is and shall remain the sole and exclusive property of University and all right, title, and interest in the same is reserved by University. This Section shall survive the termination of this Agreement.

18.2. SERVICE PROVIDER USE OF UNIVERSITY DATA. Service Provider is provided a limited

license to University Data for the sole and exclusive purpose of providing the Services, including a license to collect, process, store, generate, and display University Data only to the extent necessary in the providing of the Services. Service Provider shall: (a) keep and maintain University Data in strict confidence, using such degree of care as is appropriate and consistent with its obligations as further described in this Agreement and applicable law to avoid unauthorized access, use, disclosure, or loss; (b) use and disclose University Data solely and exclusively for the purpose of providing the Services, such use and disclosure being in accordance with this Agreement and applicable law; and, (c) not use, sell, rent, transfer, distribute, or otherwise disclose or make available University Data for Service Provider’s own purposes or for the benefit of anyone other than University without University’s prior written consent. This Section shall survive the termination of this Agreement.

18.3. RETURN OF UNIVERSITY DATA. Upon the termination of this Agreement,

Service Provider shall, within one (1) business day following the termination of this Agreement, provide University, without charge and without any conditions or contingencies whatsoever (including but not limited to the payment of any fees due to Service Provider), with a final extract of the University Data in the format specified by University. Further, Service Provider shall certify to University the destruction of any University Data within the possession or control

Page 38: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 12 of 14

of Service Provider but such destruction shall occur only after the University Data has been returned to University. This Section shall survive the termination of this Agreement. 19. FAMILY EDUCATIONAL RIGHTS AND PRIVACY ACT. Consultant will protect the confidentiality of student education records, including personally identifiable information found in education records, in compliance with the Family Educational Rights and Privacy Act of 1974 (“FERPA”) and its implementing regulations, specifically 20 U.S.C. § 1232g, 34 C.F.R. § 99.1 et seq., and University Policy 571.020. Consultant will not use personally identifiable information from student education records it receives for any purpose other than performing its obligations under this Contract. Consultant may not disclose or redisclose any personally identifiable information from student education records obtained from the University or collected by Consultant on the University’s behalf without the University’s written authorization. Any unauthorized disclosure of student education records or personally identifiable information by Consultant may result in damages owed pursuant to the indemnity section above. 20. EQUAL EMPLOYMENT OPPORTUNITY NOTICES. This Consultant and any subcontractor shall abide by the requirements of 41 CFR 60-1.4(a), 60-300.5(a) and 60-741.5(a). These regulations prohibit discrimination against qualified individuals based on their status as protected veterans or individuals with disabilities, and prohibit discrimination against all individuals based on their race, color, religion, sex, sexual orientation, gender identity or national origin. Moreover, these regulations require that covered prime contractors and subcontractors take affirmative action to employ and advance in employment individuals without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability or veteran status.

21. COMPLIANCE WITH APPLICABLE LAW. Consultant will comply with all Applicable Laws. As required by University policy, Consultant certifies that Consultant has not discriminated against historically underrepresented businesses, including Minority Business Enterprises, Women Business Enterprises, and Emerging Small Businesses. Consultant will, when applicable, have made good faith efforts to work with or obtain materials to be used in performing the Contract from minority-owned, women-owned, and emerging small business enterprises. 22. GOVERNING LAW; JURISDICTION; VENUE. This Contract will be governed and construed in accordance with the laws of the State of Oregon without regard to principles of conflicts of law. Any claim, action, or suit between University and Consultant will be brought and conducted solely and exclusively in the Circuit Court for Lane County for the State of Oregon. However, if any claim, action, or suit must be brought in a federal forum, it will be brought and conducted exclusively in the United States District Court for the District of Oregon. BY EXECUTION OF THIS CONTRACT, CONSULTANT CONSENTS TO IN PERSONAM JURISDICTION OF SUCH COURTS. In no event will any part of this Contract be construed as a waiver by University of its sovereign and governmental immunities.

23. SURVIVAL. All provisions of this Contract that would reasonably be expected to survive the termination of this Contract will do so. 24. SEVERABILTY. If any term or provision of this Contract is declared by a court

Page 39: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 13 of 14

of competent jurisdiction to be illegal or in conflict with any law, the validity of the remaining terms and provisions will not be affected. The Parties agree to attempt to substitute for any illegal or unenforceable provision a valid or enforceable one that achieves the economic, legal, and commercial objectives of the illegal and unenforceable provision to the greatest extent possible. 25. NO THIRD PARTY BENEFICIARIES. University and Consultant are the only parties to this Contract and are the only parties entitled to enforce its terms. Nothing in this Contract gives, is intended to give, or will be construed to give any benefit or right, whether directly, indirectly or otherwise, to third persons, unless such third persons are individually identified by name and expressly described in this Contract as intended beneficiaries. 26. TIME IS OF THE ESSENCE. Consultant agrees that time is of the essence under this Contract. 27. PAYMENT. Unless a different payment date is specified in the Contract, payment for goods and services under the Contract will be made within 45 days following the date the entire order is delivered, services completed, if applicable, or the date the invoice is received, whichever is later. Payment of overdue account charges by University will be subject to University Policy 580.061, Sec. J. Consultant will not be compensated by any other party for work performed under this Contract. 28. LIMITATION OF LIABILITY. Consultant agrees that to the fullest extent permitted by law, University shall not be liable to Consultant for any special, indirect or consequential damages whatsoever, whether caused by negligence, errors, omissions, strict liability, breach of contract, breach of warranty or other cause or causes whatsoever, including but not limited to, loss of profits or revenue.

29. FORCE MAJEURE. Neither University nor Consultant will be held responsible for delay or default caused by fire, riot, acts of nature, terrorist acts, or other acts of political sabotage, or war where such cause was beyond, respectively, University or Consultant's reasonable control. Consultant will, however, make all reasonable efforts to remove or eliminate such a cause of delay or default and will, upon the cessation of the cause, diligently pursue performance of its obligation under this Contract. However, if a default or delay due to a force majeure event continues for an unreasonable time, as determined by the University, then the University is entitled to terminate the Contract. 30. WAIVER. The failure of University to enforce any provision of this Contract will not constitute a waiver by University of that or any other provision. 31. ATTACHMENTS. All attachments, addenda, schedules, and exhibits which are referred to in this Contract are incorporated in this Contract. 32. MERGER. THIS CONTRACT CONSTITUTES THE ENTIRE AGREEMENT BETWEEN THE PARTIES. THERE ARE NO UNDERSTANDINGS, AGREEMENTS, OR REPRESENTATIONS, ORAL OR WRITTEN, NOT SPECIFIED IN THIS CONTRACT REGARDING THIS CONTRACT. NO AMENDMENT, CONSENT, OR WAIVER OF TERMS OF THISCONTRACT WILL BIND EITHER PARTY UNLESS IN WRITING AND

Page 40: UNIVERSITY OF OREGON (“University”) REQUEST FOR PROPOSAL

RFP for Website Redesign (PCS# 226000-01273-RFP) Exhibit B – Template Contract - Page 14 of 14

SIGNED BY ALL PARTIES. ANY SUCH AMENDMENT, CONSENT, OR WAIVER WILL BE EFFECTIVE ONLY IN THE SPECIFIC INSTANCE AND FOR THE SPECIFIC PURPOSE GIVEN. 33. USE OF UNIVERSITY’S PROPRIETARY MARKS AND INFORMATION. Consultant is not permitted to use the University’s marks, logos, trade names or other proprietary information for marketing, advertising, or other any other purpose other than performing the Contract without advance written approval by the University. All such uses must comply with University’s Style and Grammar Guide and University’s brand management strategy available at: https://brand.uoregon.edu/. 34. AMBIGUITIES. Each party has participated fully in the review and revision of this Contract and neither party shall be considered the “drafter” for the purposes of any rule of construction that might cause any provision to be construed against the drafter of this Contract. 35. CAPTIONS. The captions or headings in this Contract are for convenience only and in no way affect the meaning or interpretation of this Contract.

36. EXECUTION AND COUNTERPARTS. This Contract may be executed in counterparts, and via facsimile or electronically transmitted signature (i.e. emailed scanned true and correct copy of the signed Contract), each of which will be considered an original and all of which together will constitute one and the same Contract. At the request of a Party, the other Party will confirm facsimile or electronically transmitted signature by delivering the Contract with an original signature to the requesting Party.