1-Request for Proposals SLCI26039 Dockless Shared Mobility.pdf

Salt Lake City Corporation Request for Proposals, RFP No. SLC26039 Dockless Shared Mobility Device Services Department of Community and Neighborhoods, Transportation Division

I. REQUEST FOR PROPOSALS (RFP) OVERVIEW

Issued By: Salt Lake City Corporation, Purchasing Division Salt Lake City Corporation (the "City") is soliciting competitive sealed proposals from qualified offerors to safely and responsibly provide dockless shared mobility devices for hire within the municipal jurisdiction of Salt Lake City. Such dockless shared mobility devices may consist of motor-assisted scooters, bicycles, and/or electric bicycles that users are not required to return to a docking station at the conclusion of a ride.

The City’s procurement processes, including this competitive solicitation, are governed by Salt Lake City Code Chapter 3.24 and Salt Lake City Administrative Rules for Procurement Article 53-1A.

Issue Date: Date stated in U3P posting

Question Due Date: Date stated in U3P posting

Close Date: Date stated in U3P posting

Purpose of this Solicitation

The purpose of this RFP is to competitively select an offeror or offerors (Offeror or Offerors) to enter into a contract with City to perform the “scope of work” (Attachment 2).

It is anticipated that the City shall select up to two (2) capable and qualified contractors to provide dockless shared mobility devices (devices) for hire. Successful contractors are expected to meet the service requirements indicated in Attachment 2: Scope of Work.

Potential contractors will be evaluated on their ability to incorporate recommended system elements and self-initiated elements into their operations. Contractors are encouraged to and will also be evaluated on their ability to provide additional elements that will enhance the safe and efficient use of dockless shared mobility devices within Salt Lake City. The City encourages contractors to propose elements that utilize new and evolving technology and/or provide upgrades to the operation and safety of the devices to meet the City’s shared mobility goals, which are:

1. Reduce automobile vehicle miles traveled to improve air quality and health.

2. Promote safety in alignment with the City’s Vision Zero efforts, responsible riding, and consumer protections.

https://codelibrary.amlegal.com/codes/saltlakecityut/latest/saltlakecity_ut/0-0-0-44693 https://codelibrary.amlegal.com/codes/saltlakecityut/latest/saltlakecity_manual_ut/0-0-0-3321

3. Advance transportation justice.

Salt Lake City understands there are many different dockless shared mobility companies with different methodologies for system ownership, business models, and system operations and the City invites any and all providers of devices to respond to this request with a proposal for Salt Lake City’s consideration.

Term

The contract resulting from this RFP will be for a term of five (5) years.

RFP Contents

RFP document (this document)

Attachment 1: Sample Agreement

Attachment 2: Scope of Work

Attachment 3: Score Sheet

All proposals submitted in response to this RFP MUST be submitted electronically through the Utah Public Procurement Place (U3P) website as detailed in Section III, Proposal Submission, below.

Proposal Submission Deadline: The deadline is the date and time listed in U3P. The upload of all proposal documents MUST be fully complete by the date and time deadline or the proposal will not be accepted.

NO LATE PROPOSALS WILL BE ACCEPTED.

II. GENERAL INFORMATION

a. Sample Agreement. Any contract resulting from this RFP will include, but not be limited to, the Sample Agreement (Attachment 1). Exceptions and/or additions to the Sample Agreement are strongly discouraged. For more information regarding exceptions, please see Section III, Proposal Submission, below.

b. Insurance Requirements. Offerors should review the required insurance coverage and notice of policy cancellation requirements that will be part of the resulting contract(s). Such insurance information is provided under Paragraph 5 of the Sample Agreement (Attachment 1). Proposed pricing must include associated insurance costs. The selected Offeror will be required to provide insurance certificates meeting all requirements at the time of notification of conditional selection.

For insurance policies listed in Paragraph 5 that require Offeror to include Salt Lake City Corporation as an additional insured, you will be required to have the policy endorsed to provide either 30-days “Notice of Cancellation to a Third Party” or 30-days “Notice of Material Change to a Third Party.” A copy of the endorsement must be provided with the

Certificate of Insurance. (Note: Either endorsement may be conditioned to allow 10-days notice if the reason for the cancellation is non-payment of premiums).

c. The selected Offeror must be registered with the following websites prior to signing the

Agreement.

i. Business Registration with the State of Utah: www.corporations.utah.gov

ii. System for Award Management: Sam.gov

iii. E-Verify: https://www.e-verify.gov/e-verify-employer-search

d. Offerors or their agents are instructed not to contact selection committee members, City officials or employees, or attempt to externally manipulate or influence the procurement process in any way, other than through the instructions contained herein, from the date of release of this RFP to the date of execution of the Agreement resulting from this solicitation. City, in its sole discretion, may disqualify Offerors who violate this paragraph.

e. Offerors or their agents are instructed not to submit any gifts or promotional items with

Offeror’s proposal. City employees are not allowed to accept such items regardless of their value.

f. Cost of Developing Proposals. All costs related to the preparation of the proposals and any related activities are the sole responsibility of the Offeror. The City assumes no liability for any costs incurred by Offerors throughout the entire selection process.

g. Proposal Ownership. All proposals, including attachments, supplementary materials, addenda, etc., shall become the property of the City and will not be returned to the Offeror.

h. No proposal shall be accepted from, or contract awarded to, any person, firm or corporation that is in arrears to the City upon a debt or contract or that is in default, as surety or otherwise, upon any obligation to the City, or that may be deemed irresponsible or unreliable by the City. Offerors may be required to submit satisfactory evidence that they have the necessary financial resources to perform and complete the work outlined in this

RFP.

i. Proposal Submission.

Subject to any exceptions Offeror identifies pursuant to subparagraph III(2)(c), Offeror’s submission of a proposal or other offer or submission constitutes the Offeror's agreement to all of the terms, conditions and provisions of the proposal package, or other solicitation documents. By the submission of proposal or other offer or submission, the Offeror represents that the matters stated in such proposal, offer, or submission are true and correct.

By submitting a proposal, offer, or submission; Offeror also acknowledges that the Offeror is willing to enter into the agreement if awarded the contract.

By submitting this proposal, the Offeror does hereby offer to perform such services on behalf of the City in the manner described and subject to the terms and conditions set forth in the attached proposal. Services will be performed at the rates set forth in said proposal.

http://www.corporations.utah.gov/

By submitting this proposal, Offeror acknowledges that it has viewed all materials published on U3P, including any addenda to this RFP.

j. The City reserves the right to reject any or all proposals received. Furthermore, the City shall have the right to waive any informality or technical defect in proposals received when in the best interest of the City.

k. Samples. Samples of items, when required, must be furnished by the Offeror free of expense to the City. If not destroyed by testing, samples may be returned at the Offeror's expense, if return is requested, in writing, at the time the sample is furnished.

l. Brand Names. Brand names and numbers, when used, are for reference only. They are intended to identify the performance level, characteristics, and quality desired. Other brands, of approved equal quality, may be considered for award. In the event of substitution, Offeror’s proposal must clearly describe the article and the proposal must state the brand name and product number of the substitution offered. The determination of the Chief Procurement Officer, in consultation with the ordering department, shall be final and conclusive in determining the equality of alternates.

When the brand name, model number, or level of quality is not stated by the Offeror, it is understood that the services, supplies, or equipment offered are exactly as specified herein.

III. PROPOSAL SUBMISSION

a. U3P Registration and Submission

i. Registration

Registration is required for electronic submission. It is the Offeror’s responsibility to register for notification to receive any changes, corrections, question/answer documents, and addendums issued for RFP documents.

Offeror must complete a one-time registration by providing their company information through Bonfire. Click this link and select “Register” to complete the registration process.

Once registered the Offeror may go to this link: Utah Public Procurement Place (U3P), to search and select any RFP project listed, log-in, download the project documents, ask questions, confirm an intent to respond, and respond to solicitations published there. Failure to register and log-in with an intent to respond to a RFP constitutes an automatic waiver of Offeror’s right to receive a direct notification of any changes, corrections or addenda for a RFP.

ii. Submission

ELECTRONIC SUBMISSION REQUIRED. THERE IS NO OPTION TO SUBMIT

A PAPER RESPONSE.

All proposals submitted in response to this RFP MUST be submitted electronically and MUST be submitted through the U3P website. The deadline for submission stated https://utah.bonfirehub.com/portal/?tab=openOpportunities https://utah.bonfirehub.com/portal/?tab=openOpportunities https://utah.bonfirehub.com/portal/?tab=openOpportunities is a hard deadline. If a proposal response is not fully and completely uploaded at the stated date and time, the proposal will not be accepted by the U3P website and will not be considered.

Deadline for submission: The deadline for complete proposal submission, including all uploads is listed in U3P.

Responses through the U3P website require uploading of electronic attachments. The U3P site will accept a variety of document types, including but not limited to Word, Excel, and PDF attachments, but not all document types are necessarily compatible with the U3P website. You MAY NOT submit documents that are embedded (zip files), movies, wmp, mp3 or mp4 files or password protected files, etc. Such actions may cause your response to be deemed as “non-responsive”.

After uploading your response file, Offerors MUST go to “Submit and Finalize” and click “SUBMIT & FINALIZE MY SUBMISSION” to complete the process.

Please allow sufficient time to complete initial registration, including any online forms, and to upload documents. The solicitation will end at the closing time published. If you are in the middle of uploading your documents at the closing time, the system will stop the process and your response will not be received by the system.

It is recommended that the submission process be completed the day prior to the due date, with the understanding that any subsequent changes/updates to that initial submission will still be accepted up to the due date and time for complete proposal submission.

b. Proposal Content

Upload cover sheet and response document as described below to the U3P website. Your proposal must be uploaded and the electronic submission completed by the time and date specified. Other uploaded documents such as an exceptions document, declarations of confidentiality, or other reference documents related to the primary response criteria are allowed but should be minimal. Do not include links to Offeror’s website in Offeror’s response.

DO NOT submit all pages of this RFP document with response. Include only the response sections described below:

i. Cover Sheet including the following information:

Company Name: ________________________________________________ Doing business as: [ ] an individual [ ] a partnership [ ] a corporation [ ] a limited liability company (mark appropriate box), duly organized under the laws of the State of _________________.

Name of Authorized Representative:

PRINCIPAL OFFICE ADDRESS:

Telephone:

Email Address:

Indicate if Offeror is registered with the following websites State of Utah Department of Commerce business search, Sam.gov, and E-Verify as further described in Section II.c above.

ii. Minimum Mandatory Requirements and Technical Response

When preparing proposals, Offeror shall reply to each of the minimum mandatory requirements and technical scoreable criteria in the order listed. Restate each numbered point listed below followed by Offeror’s response in full, narrative sentences and provide any requested materials.

c. Exceptions

i. Exceptions and/or additions to the Sample Agreement (Attachment 1) are strongly discouraged.

Any exceptions submitted or required acceptance of an Offeror’s terms and conditions may render the submission as non-responsive to the requirements listed. The City shall be the sole determiner of the acceptability of any exception. Exceptions shall be considered in the evaluation and the award processes.

The City may refuse to negotiate exceptions and/or additions that are determined to be excessive; that are inconsistent with similar contracts of the procurement unit; to warranties, insurance, or indemnification provisions that are necessary to protect the procurement unit after consultation with the City Attorney's Office or other applicable legal counsel; where the solicitation specifically prohibits exceptions and/or additions;

or that are not in the best interest of the procurement unit.

An award resulting from this RFP is subject to successful contract terms and conditions negotiation (if required). The City may reject a proposal if execution of the Agreement by the Offeror is unduly delayed. In a multiple award, the City reserves the right to negotiate exceptions and/or additions to terms and conditions in a manner resulting in expeditious resolutions. Contracts may be executed and become effective as negotiations are completed.

ii. Offeror must provide the City’s Sample Agreement for this solicitation in Microsoft

Word format with redline edits along with Offeror’s proposal as a separate and distinct document and clearly marked “Exceptions or Additions to RFP documents”.

Additional terms or documents must be submitted in separate Microsoft Word documents. Offeror must also provide the name, contact information, and access to the person(s) that will be directly involved in legal negotiations.

Exceptions and/or additions submitted after the date and time deadline for receipt of proposals will not be considered.

Offerors may not submit requests for exceptions and/or additions by reference to an Offeror's website or URL. URLs provided with a proposal may result in that proposal being rejected as non-responsive.

d. Confidentiality

If applicable to Offeror’s proposal submit the following:

i. A written claim of business confidentiality accompanied by a concise written statement of reasons supporting the claim of business confidentiality. Blanket claims that the entire RFP is confidential will be denied and the proposal may be considered non-responsive. (Please use the form provided with this RFP).

ii. One redacted version of the proposal for public release, with all protected business confidential information either blacked-out or removed, clearly marked as “Redacted Version”.

iii. One non-redacted version for evaluation purposes clearly marked as “Protected Business Confidential Information Included Within”.

All three of the foregoing items must be submitted concurrently with the records (with the initial proposal submission and with any other records submitted by Offeror during the evaluation process).

All responses, inquiries, and correspondence relating to this RFP and all reports, charts, displays, schedules, exhibits, and other documentation produced by the Offeror that are submitted to the City, as part of the proposal or otherwise, shall become the property of the City when received by the City and may be considered public information under applicable law. The City is subject to the disclosure requirements of the Government Records Access and Management Act, Title 63G, Chapter 2, Utah Code Annotated (GRAMA). The City generally considers proposals and all accompanying material to be public and subject to disclosure.

The City cannot guarantee that any information will be held confidential. If the Offeror makes a claim of business confidentiality, the City, upon receipt of a request for disclosure, will determine whether the material should be classified as public or nonpublic, and will notify the offeror of such determination. The Offeror is entitled under GRAMA to appeal an adverse determination. The City is not obligated to notify the Offeror of a request to see the Offeror’s proposal, and will not consider a claim of confidentiality, unless the Offeror's claim of confidentiality is made at the time of proposal submission in accordance with GRAMA.

e. Cost Proposal

Offeror must upload a completed cost proposal form through U3P. If an Offeror fails to upload a completed cost proposal form, then its proposal will be considered non-responsive and the proposal will be rejected.

Failure to submit cost or pricing data separately may result in Offeror’s proposal being judged as non-responsive and ineligible for contract award.

Offerors must not include costs or pricing data in their responses to the mandatory minimum requirements and the technical response.

VI. QUESTIONS AND CLARIFICATION

If Offerors have questions, need clarification of provisions, or think the City has omitted anything from this RFP which is necessary to a clear understanding of the work, or should it appear that various instructions are in conflict, then the Offeror shall submit questions online through the U3P website prior to the questions due date and time listed in U3P.

No interpretation of the meaning of any provision in this RFP, nor correction of any apparent ambiguity, inconsistency, error, or any other matter pertaining to this RFP shall be made to the Offeror orally. All questions requesting clarification or interpretation of any section or sections of this RFP must be submitted online through the solicitation on the U3P website prior to the date and time listed in U3P.

Questions received after the question submission date identified above may not be considered nor receive a response. If questions prompt the need for changes to the RFP document(s), the City will issue a written addendum. Any Q & A information and/or written addendums issued by the City shall be available for interested Offerors to view or download through the U3P website within a reasonable period of time following the above referenced deadline.

VII. PROPOSAL CONTENT

When preparing proposals, Offeror shall reply to each of the following minimum mandatory requirements and technical scoreable criteria in the order listed. Restate each numbered point listed below followed by Offeror’s response in full, narrative sentences and provide any requested materials. The score sheet has been attached to this RFP as Attachment 4: Score Sheet. The score sheet states the relative weight that will be given to each technical scoreable criteria. Proposals should be no more than 30 pages, inclusive of all content. Proposals that exceed the page limit will be evaluated only on the first 30 pages.

a. Minimum Mandatory Requirements

Offerors must demonstrate the ability to meet or exceed the mandatory minimum requirements outlined below by providing a narrative point-by-point response, in the order listed, to each requirement.

The following mandatory minimum requirements must be met in order for a proposal to be considered responsive:

i. City Ethics Requirement. Offeror must include the following two paragraphs in

Offeror’s proposal including Offeror’s own written acknowledgement that Offeror has read the first two paragraphs and agrees to comply with the terms thereof. Failure to do so will result in disqualification of Offeror.

Representation regarding ethical standards for city officers and employees and former city officers and employees. The offeror represents that it has not: (1) provided an illegal gift or payoff to a City officer or employee or former City officer or employee, or his or her relative or business entity; (2) retained any person to solicit or secure this contract upon an agreement or understanding for a commission, percentage, or brokerage or contingent fee, other than bona fide employees or bona fide commercial selling agencies for the purpose of securing business; (3) knowingly breached any of the ethical standards set forth in the City's conflict of interest ordinance, Chapter 2.44, Salt Lake City Code; or (4) knowingly influenced, and hereby promises that it will not knowingly influence, a City officer or employee or former City officer or employee to breach any of the ethical standards set forth in the City's conflict of interest ordinance, Chapter 2.44, Salt Lake City Code.

It is the City’s policy that City employees are prohibited from personally accepting gifts, incentives, or marketing or promotional items from suppliers and that suppliers shall not offer such items to City employees. Such offers from suppliers are inappropriate and may result in suspension or debarment of the supplier from the City's procurement processes.

ii. Offeror certifies that Offeror has five (5) years of experience similar to the work described in Attachment 2: Scope of Work; and has provided similar services for at least five (5) markets with a jurisdictional population of at least 200,000 and a scooter fleet of at least 1,000 vehicles and in which Offeror operated for at least one (1) year.

iii. Shared mobility device operators are required to have all of the insurance as listed in paragraph 5 of Attachment 1: Sample Agreement, for compliance with Utah Code 41- 6a-1115.1. If a proposal is awarded a contract, Offeror agrees to provide evidence of all the required insurance.

All of the items described in this section are non-negotiable. However, if a manufacturer's specification is used or identified above, then a proposal may include, in sufficient detail, that its proposal contains an equivalent brand.

b. Technical Scorable Criteria

i. Qualifications

1. A statement of the firm's experience and qualifications to meet the requirements of the City as outlined herein. Include a general overview and history of your company, number of years in business, number of employees, corporate headquarters location, type of business, names of the firm’s chief officers (include an organizational chart if possible), and where you do business.

2. Identify proposed staff members who would be involved in providing the services requested herein, where the staff members will be located, and submit statements or resumes detailing their qualifications. Your proposal should include information on levels of training received by each staff member and descriptions of their involvement with projects of similar or identical scopes.

3. If applicable, identify any of the work that you intend to subcontract to others and identify the proposed subcontractors including names, specific assignments, and the qualifications of the subcontracting firm and its key personnel.

4. Detail your firm’s experience in providing the services requested with dates of performance and/or completion, jurisdiction name, contact person, email address(es), and telephone number(s). If Offeror has worked in Salt Lake City, include Salt Lake City in this section. By providing such references you agree that neither the City nor the clients referenced shall have any liability regarding the provision of such references or the City’s use of such references in making selections under this RFP . This may be presented as narrative or in a table, and should include:

1) Client contact information

2) Size of the system by number of vehicles and brief description of models/form factors of devices and the name of the vehicle vendor(s) used

3) Number of years Offeror has operated the system and total length of permit(s) and/or contract(s)

4) Brief description of ownership model (e.g., municipally owned, privately owned system, etc.)

5) Brief description of business model (e.g., W2 employees, 1099 independent contractors, subcontractors, franchisees, etc.)

6) Description of Offeror’s ability to sustainably fund all operations, including details on past financing strategies and outcomes and whether the program required any public contributions to support operations

7) Description of Offeror’s approach to data sharing with municipality

8) Compliance with equitable deployment requirements and other equity-related requirements

9) Description of successful approaches to and outcomes of e-scooter share marketing and community engagement to Black, Indigenous, People of Color (BIPOC); people living on low incomes; immigrants and refugees;

and other historically underserved communities

10) Description of experience integrating the e-scooter system and digital apps with public transit and other open-source or proprietary third-party apps

11) For any e-scooter share programs no longer permitted and/or operated by Offeror in North America since January 1, 2020, please provide the reason the permit and/or contract is not active and clarify any loss of permit and/or contract and closure of system.

5. In addition to the information and qualifications specified above, identify any special knowledge or skills provided by your firm that may be related or helpful to the services requested herein.

ii. Proposed approach

Proposals must address the following criteria and include detailed explanations of how the offeror will integrate them as a part of your plan to provide dockless shared mobility device services in Salt Lake City.

1. Overview. Provide a statement of your general understanding of the services to be provided and a general description of your proposed approach to addressing the goals outlined in this document and in Attachment 2, Scope of Work.

2. Program Goals. Please describe your approach to meeting the following goals:

a. Goal 1: Reduce automobile vehicle miles traveled (VMT) to improve air quality and health

b. Goal 2: Promote safety, responsible riding, and consumer protections

c. Goal 3: Advance transportation justice

3. Operations. Provide a response regarding how you will provide the necessary requirements for the products and services as detailed in Attachment 2, Scope of Work, for each subject below, and include any recommended strategies and/or innovations you can offer in these areas as well.

1) Device Safety. Describe how devices will be maintained for safe, convenient, and reliable use, including how you will ensure all items in Attachment 2, Scope of Work, section II.B – Device Safety.

2) User Education and Safety. Describe how users will be educated to improve rider safety and to maintain a safe, convenient, and comfortable city for all users, including how you will ensure all items in Attachment 2, Scope of Work, section II.C – User Education and Safety.

3) Contractor Enforcement/Noncompliance. Describe how policies, laws, and rules governing e-scooter use will be enforced to compliance, including how you will ensure all items in Attachment 2, Scope of Work, section II.D – Contractor Enforcement and Noncompliance.

4) Device User Enforcement and Noncompliance. Contractor shall provide, implement, and proactively utilize an enforcement system that penalizes Device users who fail to comply with the laws governing Dockless Shared Mobility Devices as described in Attachment 2, Scope of Work, section II.E - Device User Enforcement and Noncompliance. Contractor shall provide City with all pertinent data related to enforcement under this subsection. Please describe how you will provide this information to City.

5) Parking. Describe how you will inform users to comply with City parking requirements and manage operations to maintain a safe, convenient, and comfortable city for all users, including how you will ensure all items in Attachment 2, Scope of Work, section II.E – Parking.

6) Operational Requirements and Labor Practices. Describe how operations will be managed to ensure a high-quality and safe experience for all users and non-users of devices, including how you will ensure all items in Attachment 2, Scope of Work, section II.B – Operational Requirements and Labor Practices.

7) Fleet Size, Diversity, and Deployment Zones Management. Describe how you will maintain fleet size and diversity of form factors throughout the city in support of the goals of this program, including how you will ensure all items in Attachment 2, Scope of Work, section II.G – Fleet Size, Diversity, and Deployment Zones Management.

8) Integration with Transit and Broader Transportation System. Describe your experience in integrating devices with transit systems and other non-automobile forms of transportation to reduce automobile vehicle miles traveled, improve air quality, and improve health, including how you will ensure all items in Attachment 2, Scope of Work, section II.H – Integration with Transit and Broader Transportation System.

9) Equity. Describe your approach to increasing equity and transportation justice in Salt Lake City, including how you will ensure all items in Attachment 2, Scope of Work, section II.J – Equity.

10) Marketing, Outreach, and Community Partnerships. Describe your approach to developing community partnerships and marketing to certain populations, including how you will ensure all items in Attachment 2, Scope of Work, section II.K – Equity.

11) Pricing, Payment Options, and Price Accessibility. Describe how you will maintain affordability for all users and provide access to riders living on low incomes and those without smartphones, including what the per-trip cost will be to the end user and how you will ensure all items in Attachment 2, Scope of Work, section II.L – Pricing, Payment Options, and Price Accessibility.

4. Data Management and Privacy - Please respond to the following questions:

1) Have you formally assigned a staff member or third party the responsibility of overseeing your company’s overall security program?

Please identify and their specific responsibilities.

2) Do you seek/receive customer permission before sharing data with third parties?

3) Do all membership auto-renewals meet State and Federal standards for consumer protection?

4) Are all of your financial transactions secure (PCI compliant)? Will you provide copies of all policies upon request?

5) What processes and methods are you using to properly anonymize and encrypt personal data?

6) Please describe your processes for detecting and communicating data breaches.

7) What tools are in place to manage the identification, tracking, and destruction of personal data associated with a User?

8) Do you purge application data according to a defined data retention schedule?

9) Do you have current, documented policies and procedures that include the following? If so, attach (policy doesn’t count toward the 30 page proposal response limit).

a) Enterprise Security Policy

b) Security Incident Response Policy and Supporting Procedures

c) Change Control Policy and Supporting Procedures

d) Acceptable/Responsible Use Policy

e) Privacy Policy

10) Do you perform background checks and/or credit checks for persons with access to confidential data?

11) Please describe (at a high level) the technical and operational controls you have implemented to help you detect and respond to security events and incidents.

12) How frequently do you log and review security-related events?

13) Describe your process for collecting and sharing certain aggregated user data with the City to ensure the program is meeting the goals outlined in section 1 of this document, including results of annual user and customer service surveys, demographics, visitor/resident analysis, ridership among people living with low incomes, accidents, and number of users that have violated Contractor requirements or municipal law.

14) Do you collect and provide efficient access to accurate, high-quality, complete and regularly updated data about the use of devices through APIs that comply with the most current versions of leading data specifications, including but not limited to the Mobility Data Specification (MDS), Curb Data Specification (CDS) and the Global Bikeshare Feed Specification

(GBFS)?

15) Do you currently partner with other open-source developers and third-party transit and mobility aggregation software/apps such as Transit, Moovit, CityMapper, Google Maps, Apple Maps, etc.? If so, please describe how you partner and how these partnerships enhance user experience.

5. Advocacy. Describe plans and any past examples of how your firm may engage riders on advocacy for bike lanes and other active transportation infrastructure.

Include what types of campaigns or policies at various levels of government you anticipate your ridership could support and specific methods for communicating advocacy opportunities.

6. Timeline for Initial Deployment. Describe your proposed timeline for initial deployment, from launch date to how you will reach full deployment of devices with all proposed technologies within no more than 28 calendar days.

7. Risks. Identify the major risks associated with this project. For each risk, identify those activities which can be undertaken to reduce, mitigate or eliminate the risk.

Identify the associated responsibilities. Ensure that these activities are reflected in your project and management plans.

8. Internal claims handling process. Detail your approach to resolve & reduce claims.

Provide forms, strategies, and techniques used.

9. Claims process for a third-party. Describe the claims process for a third-party from beginning to resolution. If applicable, please include required forms, department contacts, etc.

10. Additional Services and Innovations. In addition to the specific service proposals specified above, identify and/or recommend any additional or innovative services and products provided by your firm that may be related to or helpful to the provision of comprehensive dockless shared mobility device services and make progress toward the goals outlined in this document and in Attachment A, Scope of Work. If there is a better way for the City to package or define the services that it has requested herein to obtain better pricing and/or service by making it easier for the selected contractor, please explain what modifications would be necessary to achieve such better pricing and/or service.

c. Policy Criteria

Some consideration will be incorporated into the scoring of proposals for the following criteria as further described in Attachment 4: Score Sheet. Provide a point-by-point response to the following questions.

i. Interest in sustainability, recycling, and other environmental matters. The City has an interest in doing business with suppliers that have implemented formal sustainability plans and have operations with minimal adverse impact on the environment. Please state whether your firm has a formal sustainability plan, program or policy and, if so, please attach a copy to your proposal. Any sustainability plan, program or policy should address recycling, re-use of materials, and reduction of waste. Please describe any environmentally friendly measures such as alternative fuel vehicles, recycling measures, and energy reduction measures used by your firm in its operations.

ii. Business Certification. Please indicate all that apply.

1. None

2. (MBE) Minority Business Enterprise

3. (WBE) Women Owned Business Enterprise

4. (SBE) Small Business Enterprises

5. (SDVBE) Service-Disabled Veteran Owned Enterprises

6. (LBE) Local Business Enterprises

iii. Apprenticeships. Has your company conducted an apprenticeship during the twelve

(12) months prior to submitting this offer that is consistent with the requirements of Utah Code Title 35A, Chapter 6 and the requirements of the U.S. Department of Labor Bureau of Apprenticeship and Training?

iv. Is Offeror considered a Local Small Business? (Defined as Offerors that have a fixed office or distribution point within City boundaries, possess a City business license stating a City address, employ no more than thirty (30) full-time employees (meaning employees working 40 hours per week, 50 weeks per year), and have annual gross revenues not in excess of one million dollars ($1,000,000.00).)

VIII. PROPOSAL EVALUATION PROCESS

a. Stage 1: Initial Review

In the initial phase of the evaluation process, City will review all proposals timely received. Non-responsive proposals not conforming to RFP requirements or unable to meet the mandatory minimum requirements will be eliminated from further consideration.

b. Stage 2: Technical Proposal And Policy Criteria Evaluation

Responsive proposals will then be evaluated by an evaluation committee appointed by City against the proposal technical scoreable criteria noted in this RFP. Proposals will be evaluated against the technical scoreable criteria as follows:

# Evaluation Category RFP Section Points

1. Qualifications VII.b.i 20.0

2. Overview and Program Goals VII.b.ii.1,2 5.0

3. Device Safety VII.b.ii.3.1) 15.0

4. User Education and Safety VII.b.ii.3.2) 15.0

5. Contractor Enforcement/Noncompliance VII.b.ii.3.3) 5.0

6. Device User Enforcement and Noncompliance VII.b.ii.3.4) 10.0

7. Parking VII.b.ii.3.5) 15.0

8. Operational Requirements and Labor Practices VII.b.ii.3.6) 10.0

9. Fleet Size, Diversity, and Deployment Zones Management VII.b.ii.3.7) 5.0

10. Integration with Transit and Broader Transportation System VII.b.ii.3.8) 10.0

11. Equity VII.b.ii.3.9) 10.0

12. Marketing, Outreach, and Community Partnerships VII.b.ii.3.10) 5.0

13. Pricing, Payment Options, and Price Accessibility. VII.b.ii.3.11) 10.0

14. Data Management and Privacy VII.b.ii.4 30.0

15. Advocacy VII.b.ii.6 5.0

16. Timeline for Initial Deployment VII.b.ii.7 5.0

17. Risks VII.b.ii.8 5.0

18. Claims Handling Process VII.b.ii.9, 10 5.0

19. Additional Services and Innovations VII.b.ii.11 5.0

20. Policy Criteria VII.c 9.5

TOTAL 199.5

Total Technical Points Possible: 199.5 points

The evaluation score sheet has been attached to this RFP. The attached evaluation score sheet states the relative weight that will be given to each technical scoreable criteria.

It is anticipated that this RFP will result in multiple contract awards. The methodology or formula that will be used to determine the number of contract awards is: contracts will be awarded to the two highest scoring proposals.