I’ve been tracking two fare-system projects this year that make an interesting pair, not because they’re similar but because they’re not. Both are North American transit agencies rebuilding how riders pay. Both involve real construction, real vendors, and real money. But the schedules underneath them are almost opposite, and that contrast says more about transit payment modernization project management than either project would on its own.
Start with St. Louis. Bi-State Development’s MetroLink Secure Platform Plan is converting the light-rail system from open, walk-on platforms to gated ones, adding fare turnstiles and doubling security camera coverage across 38 to 39 stations in Missouri and Illinois. It’s a $52 million program, and the funding stack alone tells you something about how these projects actually get financed: about $12 million from bond refinancing earmarked for security, $12 million from Illinois federal stimulus dollars, $17.25 million from Bi-State’s own capital budget plus American Rescue Plan Act funds, and $10.75 million from private sources. Four funding streams, two states, one program office trying to keep them all moving on the same schedule.
The sequencing is the part I’d point to if I were briefing a new PM on how this kind of infrastructure project actually unfolds. The agency didn’t go straight to a construction contract. It first awarded a design contract to HNTB, worth just under $7 million after being negotiated down from HNTB’s original $8.1 million proposal, with more than a year budgeted just to finish design work before construction bidding even opened. Construction itself was then estimated at another 24 to 30 months. That’s a multi-year runway before a single gate goes in the ground, which is the right call when you’re retrofitting safety-critical infrastructure across dozens of stations rather than flipping a software switch.
Even with that runway, the rollout still had to be phased, because you can’t take 38 stations offline at once without stranding riders. Phase 1 activated 13 stations on July 6, split between Missouri and Illinois. Phase 2 added 26 more on July 27. A third phase, covering remaining equipment, was explicitly tied to ticket vending machine delivery, meaning the schedule bent around a vendor’s manufacturing and shipping timeline rather than the other way around. That’s the kind of dependency that looks small on a Gantt chart and becomes the thing you’re explaining to a board when it slips. The design also baked in accessibility from day one rather than as a change order: the turnstiles pair a full-height gate with an ADA-compliant swing door at every station, not a retrofit added after advocacy groups pushed back.
Now compare that to Kansas City. KCATA is moving its RideKC system from a fare-free model to a paid, multichannel fare collection environment, with Genfare supplying validator hardware and back-office software for open-loop bankcard payment, mobile ticketing, and closed-loop smart cards. The implementation-support RFP closed March 9, 2026, and system rollout begins June 1. That’s roughly twelve weeks from bid close to go-live, on a program tied to a hard external deadline: Kansas City is a host city for the 2026 FIFA World Cup, and the agency needs fare collection running cleanly before the tournament brings a surge of unfamiliar riders through the system.
Neither timeline is wrong. They’re solving different risk equations. St. Louis is managing physical construction risk, cross-jurisdictional funding risk, and public-safety accountability, so a deliberate, buffered schedule with a long design phase is the responsible choice. Kansas City is managing a fixed external date it can’t move and a technology deployment that doesn’t require pouring concrete, so compression is the rational trade, provided the implementation-support scope is tight enough to catch integration problems before opening day rather than during it. What both projects share is that neither treated procurement as a single event. St. Louis split design from construction. Kansas City split the fare technology vendor selection from the implementation-support contract that’s supposed to make sure Genfare’s hardware actually works with RideKC’s operations on day one. That separation is easy to skip when a schedule is tight, and it’s usually the first thing cut when a program is under pressure, which is exactly when you need it most.
If you’re working on either side of a fare modernization program right now, whether you’re the one negotiating the design contract or the one trying to compress a vendor timeline against a fixed date, I’d be glad to compare notes. These programs all look similar from the outside, funding stack and phasing plan and vendor scope, but the judgment calls underneath them are rarely the same twice.
Leave a Reply