A typical deployment is sequenced over a year, subject to procurement, approvals, and readiness. Each phase produces artefacts the city can review before expanding scope.
Policy design and system integration
Select a phase to read a concise summary and jump to the matching timeline section.
The first phase establishes the operational and policy framework. City leadership defines programme goals such as reducing peak-hour congestion, encouraging carpooling, promoting off-peak travel, and supporting shared mobility. Institutional coordination begins across transportation authorities, traffic management, urban planning, and digital governance teams.
MTSAi is designed to integrate with existing city infrastructure including digital tolling systems, traffic monitoring, urban command centres, and mobility data sources. At the end of this phase, the city has a defined policy model and an integrated system environment.
Evidence & success criteria
- Published programme goals and corridor scope for the pilot
- Institutional roles and approval gates documented
- Integration readiness checklist for tolling, traffic monitoring, ICCCs
- Versioned policy model ready for audit and procurement review
A controlled pilot begins on one or two selected high-congestion corridors. Public communication explains how incentives work, how commuters participate, and how data is used and protected. Initial incentives are configured for verified carpooling, off-peak travel, and shared mobility usage.
The pilot begins generating operational data and behavioural insight on a defined, time-bounded basis.
Evidence & success criteria
- Public communication materials and participation pathway published
- Pilot corridor instrumentation + integration verified
- Incentive configuration and eligibility rules recorded
- Baseline metrics defined for evaluation (traffic, participation, equity)
The city reviews pilot metrics such as peak-hour traffic volumes, carpool participation rates, commuter response to incentives, and corridor travel times. Policy parameters can then be adjusted — including incentive levels, eligibility conditions, and target corridors.
This iterative process allows cities to improve effectiveness while maintaining public confidence.
Evidence & success criteria
- Evaluation report with outcomes, risks, and public feedback summary
- Policy adjustments logged and justified with audit trails
- Appeal/dispute pathways tested and documented
- Decision memo: continue, adjust scope, or halt
If pilot performance is stable and evaluation supports continuation, the city can plan expansion to additional congestion corridors, new incentive categories, shared mobility provider integration, and broader commuter participation.
At this stage the system can transition from pilot to operational demand-management tool, subject to the city's own evaluation findings and procurement decisions.
Evidence & success criteria
- Expansion corridors and categories scoped with governance approvals
- Updated integration plan for partners and enforcement workflows
- Budget model for incentives and ongoing operations
- Procurement-aligned rollout plan and accountability controls
Continuous Oversight and Accountability
Throughout deployment the city retains:
These capabilities are designed to ensure mobility policies remain transparent, accountable, and adjustable throughout every phase.
The 12-month structure above describes how MTSAi is designed to support a phased city deployment. Actual timelines, scope, and outcomes depend on procurement processes, regulatory approvals, local infrastructure readiness, and the city's own evaluation findings. MTSAi does not claim outcomes in advance of deployment.