​

REAL TIME POLICY IMPROVEMENTS

​

March 13, 2025

HOUSEKEEPING

• Set your name and organization in the Participant list

​

​

• Mute yourself

​

• Introduce yourself in the chat

​

• Use chat to let us know you want to speak, or use the raise hand feature ✋�
• This meeting is being recorded and will be published with notes

AGENDA

​

​

WGSC Roles

Host: Pierre Bouffort, Blue Systems

Facilitator: Michael Schnuerle, OMF

Preparation: Michael Schnuerle, OMF

Outreach: Michael Schnuerle, OMF

Note taker: Michael Schnuerle, OMF

1. Intro and announcements (10 min)
2. Fixed Route Services #927 Recap (5 mins)
3. MDS Real Time Policy Improvements (20 mins)
1. Issue #906 and PR #928
2. New endpoint that allows push of new policies
3. New Notification/Communication push endpoint/API that sends updates from city to operator
4. Discussion/Comments (20 mins)

​

INTRO

Pierre Bouffort, Blue Systems (5 mins)

THE OPEN MOBILITY FOUNDATION

• Created to support cities and industry on our collective digital transformation journey.�
• City founded and city led organization, supported by private sector partners.

​

• Steward common digital language for companies and cities to use to more predictably and dynamically manage the public realm.

​

• Help cities collect better data - not necessarily more data - and create a better experience for people using our streets and sidewalks.

​

• Technology built through public and private sector collaboration with emphasis on transparency and formal approval�
• Working groups and GitHub repositories open-to-all

​

• More competitive markets for mobility services and software tools

​

• Collaboration with other open projects

OMF’S OPEN APPROACH

MDS enables two-way communication between public agencies and shared mobility services operating in the right of way

Vehicles

Events

Trips

Telemetry

Stops

Reports

Geographies List

Geography Detail

Discover

Query

Policies

Jurisdictions List

Jurisdiction Detail

Version 2.0.0 - APIs and Endpoints

Requirements

data from Operators

data from Cities

ANNOUNCEMENTS

OMF Team and Attendees (5 mins)

MDS STEERING COMMITTEE VOTE

New MDS Steering Committee nominations open to a member vote.

• MDS WG mailing list members with receive online voting info
• If you are an OMF member and participate as a Contributor in the MDS WG, you can vote
• The voting form will include information on what is required
• The OMF Bylaws describe this WGSC election process, and feedback from this process will be used to revise them as needed via approval of the OMF Board
• 5 public nominees, 4 non-public nominees (9 total)
• Results announced at next working group meeting

MDS STEERING COMMITTEE CANDIDATES

1. Muyi Zhou, Transportation Planner, San Francisco Municipal Transportation Agency
2. Matt Thrasher, Senior Product Manager, Waymo
3. Deb Gangopadhyay, Co-founder and President (COO, CTO), Beam Mobility
4. Vladimir Gallegos, Supervising Transportation Planner, LADOT
5. Armand Shahbazian, Electric and Automated Mobility Lead, Seattle Department of Transportation
6. Michael Schwartz, General Manager, City Software Solutions, INRIX
7. Pierre Bouffort, Head of Product, Blue Systems
8. Gene Leynes, Enterprise Architect, City of Chicago
9. Joshua Lynch, Regulatory Policy Analyst, Portland Bureau of Transportation

UPCOMING EVENTS

Mark your calendar, grab your tickets, and prepare to discuss transportation and digital infrastructure — we look forward to seeing you at one of these events this year!

​

Keep this guide bookmarked to stay updated on event details and special pricing.

​

openmobilityfoundation.org/2025-calendar/

​

Plus, find details for confirmed OMF events and stay up-to-date on monthly MDS and CDS Working Group meetings on our public Google calendar.

FIXED ROUTE SERVICE - ACTION

PULL REQUEST PROPOSAL DETAILS

Description of Pull Request #927 from SFMTA. Final thoughts now, pushing to dev next week if discussions resolved.

​

Presented by Matt Marwedel, Data Consultant, Taxis, Access & Mobility Services.

REAL TIME POLICY IMPROVEMENTS

Vehicles

Events

Trips

Telemetry

Stops

Reports

Geographies List

Geography Detail

Discover

Query

Policies

Jurisdictions List

Jurisdiction Detail

Version 2.0.0 - APIs and Endpoints

Requirements

data from Operators

data from Cities

MDS POLICY BACKGROUND

The goal of the Policy API specification is to enable agencies to create, revise, and publish machine-readable policies (in real-time if needed), as sets of rules for individual and collective device behavior exhibited by both mobility as a service providers and riders / users. Examples of policies include:

• City-wide and localized caps (e.g. "Minimum 500 and maximum 3000 scooters within city boundaries")
• Exclusion zones (e.g. "No scooters are permitted in this district on weekends")
• Cap allowances (e.g. "Up to 500 additional scooters are permitted near train stations")
• Speed-limit restrictions (e.g. "15 mph outside of downtown, 10 mph downtown")
• Idle-time and disabled-time limitations (e.g. "5 days idle while rentable, 12 hours idle while unrentable, per device")
• Trip fees and subsidies (e.g. "A 25 cent fee applied when a trip ends downtown")
• Real-time emergency notifications (e.g. "A no travel geofence around a fire reported by a 911 call")
• Large event policy rules (e.g. "No AVs or carshare near a planned stadium event, but 25 cent bikeshare subsidy when trips end near event")

​

MDS POLICY INFO

• 67 known jurisdictions around the world publish MDS Policy data feeds
• Dozens of operators consume digital policy from these cities
• Many vendors help cities create these feeds, or help operators ingest the feeds
• Recent MDS Policy Projects:
• Seattle’s real-time 911 for AVs
• LADOT’s large events for AVs
• World Cup cities

REAL TIME POLICY IMPROVEMENTS

Open Issue #906 from May, and Pull Request #928

​

Currently includes the following changes:

​

1. Real-time language clarification and examples
2. Noting that agencies may manage their public Policy feeds, for example with an API key
3. Policy uniqueness note to prevent identical policy duplication
4. last_updated parameter to return only the last updated date
5. active_only parameter to return only current, active policies
6. A Policy object relationship diagram.

REAL TIME POLICY IMPROVEMENTS

Open Issue #906 from May, and Pull Request #928

​

To possibly come in the future:

​

• Additional relevant policy examples
• A push endpoint option
• A new Message/Notification/Communication endpoint/API
• Adding a max_update_interval field like in Requirements to note how frequently the file may update

DISCUSSION

THANK YOU

��openmobilityfoundation.org/about-mds

linkedin.com/company/openmobility

github.com/openmobilityfoundation