Municipal shared mobility programs serve multiple stakeholders with conflicting priorities: citizen convenience, budget accountability, regulatory compliance, political visibility, and service reliability. Procurement requires vendor stability, transparent reporting, and evidence of real-world deployments—not startup pitches
Transportation departments, finance offices, citizen services, and elected officials all require different reporting and oversight capabilities
Restricted parking areas, speed limits, vehicle capacity caps must be enforced automatically, not through user education
Every trip, every vehicle, every cost must be auditable with export capability for financial systems
Procurement offices need evidence of platform stability, backward compatibility guarantees, and escape hatches from vendor lock-in
Multi-tenant federation architecture allows cities to run multiple programs (citizen car-sharing, municipal fleet, public transit integration) from one platform with separate budgets, separate reporting, and separate policies. Zone-level governance enforces parking restrictions, speed limits, and capacity rules automatically—violations gate billing and route to review queues. Audit trails log every administrative action with timestamp and reason capture. Versioned API with backward compatibility eliminates forced upgrades and integration breakage. Export center dumps complete data sets for budget reconciliation and compliance reporting.
Federation model: independent programs under unified management
Zone enforcement: real-time policy compliance with automated violation detection
Role-based access control: menu-level and action-level permissions per admin user
Audit logs: immutable activity trails on all major entities
Export center: full data dumps filterable by period and status
