4-SLCI27031 Attachment 2 Scope of Work.pdf

SCOPE OF WORK

MICROMOBILITY TRACKING SOFTWARE

FOR THE SALT LAKE CITY TRANSPORTATION DIVISION

I. OBJECTIVE

a. The City operates a dockless shared mobility program that provides devices for hire within Salt Lake City’s municipal jurisdiction. Contractor shall provide a cloud-based Micromobility Tracking Software (SaaS) system for the Transportation Division to monitor, audit, regulate, and report on dockless mobility device use, in support of the City’s program goals: reducing automobile vehicle miles traveled (VMT), promoting safety and Vision Zero alignment, and advancing transportation justice.

II. RESPONSIBILITIES OF CONTRACTOR

The responsibilities of Contractor include, but shall not be limited to, the following:

a. Contractor shall provide Micromobility Tracking Software for City’ s Transportation Division for the purpose of monitoring, auditing, regulating, and reporting the use of dockless mobility devices from the providers of dockless mobility services.

b. Micromobility Tracking Software shall have the following functionality:

i. Contractor-hosted, cloud-based Software as a Service (SaaS) system, accessible from a standard web browser, with unlimited City user accounts and on-demand availability for City staff.

ii. Have the ability to ingest the Mobility Data Specification (MDS) version

2.1 or later, whichever is most current, and General Bikeshare Feed Specification (GBFS) data, version 3.0 or later, whichever is most current.

iii. Capable of ingesting any new data standards, including MDS/GBFS, that are released. This includes being capable of ingesting and visualizing all MDS 2.1 and GBFS 3.0 or newer data, including, but not limited to, updated vehicle modes and incidents and crash data.

iv. Have unlimited data storage.

v. Have the ability to ingest data from multiple dockless shared mobility companies and, as needed, local bikeshare operators.

c. The privacy & security features of Micromobility Tracking Software shall:

i. Apply de-identification methods to ensure no personally identifiable information is viewable to any user of the data.

ii. Ensure the security of the data through security protocols per named, current industry standards

iii. Ensure that sensitive data cannot be accessed by an outside entity without proper authorization.

d. Functional Requirements: Micromobility Tracking Software shall have the ability to:

i. Display operator data in near-real time updates.

ii. Display of:

1. vehicle location

2. vehicle ID

3. operator

4. vehicle type

5. operational status

6. last reported location

7. last data transmission

8. battery level (if available)

9. parking duration in accessible location within software interface

iii. Creation, editing, and visualization of geospatial data to demarcate geographic zones and geofences through polygons, points, and lines.

iv. Display, import and export of geospatial data in a tabular formats

(.csv, etc.).

v. Display, import and export of geospatial data in a standard GIS formats(.json, .geojson, .kml, .kmz, .shp, .shx, .dbf, etc.).

vi. Zone types including, at minimum:

1. no-ride

2. no-parking

3. slow-speed

4. preferred or mandatory parking

5. deployment

6. equity

7. transit station area

8. special-event

9. construction or temporary closure

10. park, pedestrian, or accessibility-sensitive zones

vii. Apply filters to specify or aggregate data by various geographic boundaries (e.g. City limits, community planning areas, commercial areas, geofencing, etc.).

viii. Apply filters to specify or aggregate data by individual dockless shared mobility companies, device types, trip routes, etc.

ix. Summarize (mean, median, sum, etc.) and generate data based on standard timeframes (day, month, quarter, year, am/pm, etc.) and user-defined timeframes.

x. Access historical and time-series data.

xi. Generate a variety of mobility metrics, including but not limited to routes, parking, origin/destination, trip length (both time and distance), overall trip volume, daily trips per device, accidents/incidents, etc.

xii. View ridership maps of shared mobility transit corridors, including heatmaps trips, parking events, trips starts and ends, operator drop-offs, etc.

xiii. Generate customizable reports of above data metrics and export those reports.

e. Micromobility Tracking Software shall assist with dockless shared mobility program monitoring by maintaining the ability to:

i. Calculate per-ride use fees, by shared mobility company, as required by the City, based on standard timeframes (e.g. day, month, quarter, year, am/pm, etc.) and user- defined timeframes.

ii. Monitor operator compliance with the City's established policies, including the ability to generate compliance reports.

iii. Monitor usage and efficacy of designated scooter parking corrals/deployment zones.

iv. Implement scooter parking corral vehicle maximums and minimums.

v. Create policies, both zone-based and otherwise, that govern the operation of micromobility devices in the city.

vi. City can publish its relevant policies and regulations to a public map to share with municipal partners.

vii. Ability to create and share a public-facing micromobility dashboard to share pertinent information with the public.

f. Contractor shall provide product/technical support as follows:

i. Contractor shall provide a competent, well-trained, and experienced contact person as a point of contact.

ii. Provide an initial onboarding session for City staff members.

iii. Provide ongoing support via a regular scheduled meeting with above point of contact and via phone and/or email during operating hours.

iv. Provide ongoing on-boarding for new City users.

v. Provide training materials (recorded trainings, written material, etc.)

on how to use the Provider’ s solution.

vi. Optional additional services, priced separately in Exhibit “B” (Price

Schedule), available on City request.

g. With regards to data ownership and end-of-contract period, the contract shall abide by the following:

i. All data, reports, configurations, and exports generated under this Agreement are the property of the City, which shall own the copyright.

ii. Contractor may retain reproducible copies for reference and customary marketing/public relations use, subject to Section VIII (Disclosure of City Records).

iii. Following the termination of this Contract, SLC reserves the right to request a complete and secure (i.e. encrypted and appropriately authenticated) download file of all data, including, but not limited to, all Data, schema and transformation definitions, or delimited text files with documented, detailed schema definitions along with attachments in its native format. After SLC has been provided and confirmed as acceptable a complete download, or declines a download and requests immediate destruction, Contactor shall Destroy all Data collected, generated, or inferred as a result of this Contract. Should SLC not request a complete download, Contractor shall Destroy the Data immediately after thirty (30) days post termination of the Contract. The Contractor shall notify SLC in writing of the date upon which all of the Data is destroyed.

iv. Contractor shall not use City data to build or train proprietary AI/ML models, and shall not use City materials in generative AI queries, without prior written City approval; any GenAI use in performance of this Agreement must be disclosed at signing, with any new or previously unreported use disclosed to the City within seven business days of identification.

h. Optional Features

i. Display and monitor issues about shared mobility devices submitted by the public.

ii. Deploy standard surveys to shared mobility operators and the general public to assess trip purpose, mode choice, and other key mobility issues, such as safety.

iii. Curb Management services data collection, visualization, and policy creation.

iv. Any other service or feature provided by the Contractor that helps further the Objective.