{"resourceId":"cityswift-tfl-bus-journey-time-results","versions":[{"version":"external-a124e2feac3502089578f337441ebfb299a57200f95f9c93c05633b124dcb5ad","resource":{"id":"cityswift-tfl-bus-journey-time-results","title":"Bus passengers save 1.5% in journey time on London routes optimised by CitySwift's AI","organization":"CitySwift (vendor); Transport for London and London bus operators","sector":"Transit agency","geography":"London, United Kingdom","publishedAt":"October 13, 2026","publicationDate":"2026-10-13","eventDate":null,"sourceName":"CitySwift blog","sourceLabel":"CitySwift (vendor)","sourceUrl":"https://www.cityswift.com/blog/bus-passengers-save-journey-time-on-london-routes-optimised-by-cityswifts-ai","evidenceClass":"vendor-claim","outcomeClass":"effective","topics":["knowledge-work","operating-model"],"finding":"CitySwift reports that customer journey times on routes optimised with its AI platform fell 1.5 percent, measured using TfL's Journey Time Metric combining speed and reliability. It says this equals 27 seconds per optimised journey, projects more than 25 million passenger-hours saved over three years valued at over £230 million, and states more than 40 percent of London's bus network has been reviewed with 200 routes improved at no cost since deployment in 2024.","sledRelevance":"A measured, modest result using an agency-defined metric is a useful counterweight to larger projections in transit AI marketing; U.S. agencies can ask vendors for similar agency-metric reporting.","evidence":"Vendor announcement; the metric is TfL's, but the analysis, baseline and attribution method are not published; the hours and value figures are projections.","architectureImplications":"A shared data platform for the authority and multiple operators supports simulating route changes before implementation.","governanceImplications":"Using the authority's own metric for reporting is a good practice for vendor accountability.","securityPrivacyImplications":"Operational data shared between authority and operators on a vendor platform; data terms are not described.","caveats":"Vendor-authored; no independent evaluation; projections of hours and monetary value; London's franchised bus model differs from most U.S. agencies.","streamIds":["transportation"],"roles":{"sales":"The London result is useful because it is modest and tied to the transit authority's own metric: 1.5 percent shorter journeys, about 27 seconds per trip. That supports conversations about realistic scheduling-optimization gains and about requiring agency-defined metrics in vendor contracts. A bounded engagement could design such metrics for a U.S. agency. Treat the 25 million hours and £230 million figures as vendor projections.","engineering":"Technically, the platform combines AVL, schedule and running-time data to simulate route and timetable changes. U.S. fit depends on data quality in CAD/AVL and GTFS feeds and on scheduling software integration. Proof of value should compare optimised routes with matched control routes using the agency's metric. Data-sharing terms for operator and agency data on a vendor platform must be explicit.","delivery":"Delivery means running schedule changes through normal service-change cycles with before-and-after measurement. Interpretation: control-route comparisons and agency-owned metrics are needed to attribute gains. Ownership sits with the agency's service planning and scheduling team, with operators involved where service is contracted. Planners should review each AI-recommended change for operational feasibility, labor rules and rider impact before it enters a service change, and results should be tracked for at least one full service period."},"roleDetails":{"sales":{"customerProblem":"Improving bus journey times and reliability through data-driven schedule and route adjustments.","stakeholders":["Service planning and scheduling","Transit data teams","Contracted operators","Agency leadership"],"discoveryQuestions":["What metric would you require a vendor to report against?","How good is your AVL and running-time data?","How would gains be attributed versus other changes?"],"valueHypothesis":"Schedule optimization can produce small but measurable journey-time gains when tied to agency metrics.","potentialEngagement":"A bounded metric-design and evaluation plan for AI-assisted scheduling.","unsupportedClaims":["Projected hours and monetary savings","Independent validation","Transferability to U.S. operating models"]},"engineering":{"fit":"Fits agencies with mature AVL and scheduling data.","architectureIntegration":"Vendor platform ingesting AVL, schedules and running times to simulate and recommend changes.","prerequisites":["Clean AVL and GTFS data","Agency journey-time metric","Service-change process"],"constraints":["London franchised model","Vendor-reported results","Scheduling labor rules"],"security":"Set data-sharing and retention terms for operational data on the vendor platform.","proofOfValue":["Optimised versus control route comparison","Per-trip journey time change","Reliability metric change"]},"delivery":{"work":"Implement optimised schedules through service changes with matched controls.","dependencies":["Scheduling software integration","Operator agreement","Data quality fixes"],"ownership":"Agency service planning and scheduling.","skillsAdoption":"Train schedulers to review and adjust AI-recommended changes.","governanceCheckpoints":["Metric approval","Service-change review","Post-change evaluation"],"acceptanceCriteria":["Proposed: journey-time change measured against control routes","Proposed: results reported using an agency-defined metric"],"risks":["Gains too small to detect","Attribution confounded by other changes","Overstated projections"]}},"retrievedAt":"2026-10-30T22:10:13-05:00","enrichedAt":"2026-10-30T22:18:05-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Schedulers and planners use the platform; workforce effects are not described.","procurementImplications":"A 'performance partnership' framing suggests outcome-linked contracting, which U.S. agencies could explore.","operatingModelImplications":"Authority and operators work on one platform, which depends on London's contracted operator model.","sourceVerification":{"openedUrl":"https://www.cityswift.com/blog/bus-passengers-save-journey-time-on-london-routes-optimised-by-cityswifts-ai","referenceExcerpt":"For an individual passenger, that 1.5% reduction equates to 27 seconds saved on every optimised journey — a modest gain on any single trip","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}