Demand-Responsive Transit in public transportation
Demand-responsive transport (DRT) is a flexible mode of transportation that adapts to passengers’ requests. The operating principle is as easy as pie.
It involves users requesting a trip via web browser, mobile application or calling a booking service which plans their route according to specified pick-up and dropoff locations and times. Initially DRT was designed to improve transit access for people with limited mobility, on a small scale and mainly as a private service. Nowadays it is increasingly entering the mass transit market that builds on this experience to enhance accessibility and quality of service to these user groups. Over the past year, DRT has expanded to enable a wide spectrum of services and to have several benefits.
One major benefit is overall improved access to public transit through shorter walking distances and waiting times, making it a more viable alternative to driving and reducing the number of vehicles on the road, as seen from our own commuter bus line, Kussbus.
Last but not least, our solution aims to maximise pooling and minimise detours and thereby reduce emissions per passenger kilometer, as well as overall kilometers traveled by buses. DRT solutions like ours allow existing public transport systems to continue improving energy efficiency and sustainability measures towards the next generation of public transport.
A demand-responsive transit service is an alternative to a fixed route system but it does not mean that it must completely replace public transportation. On the contrary, flexible routes can compliment flexible routes and vice versa.
UFT can combine the two approaches without making it complex. In one click, a public transit operator can handle a dispatch schedule, and/or routing of a vehicle to accommodate incoming users requests through the UFT platform. Operators can also decide to configure multiple service types such as scheduling buses in fixed route system or directly to passengers doorsteps. In other cases, vehicles can run on a predetermined route without a fixed schedule and may stop only during a subset of predetermined stop groups, based on requests.