Matthew Wigginton Bhagat-Conway , Luke Pullo , Kai Monast
{"title":"Evaluating the effectiveness of automated scheduling at rural transit agencies in north carolina","authors":"Matthew Wigginton Bhagat-Conway , Luke Pullo , Kai Monast","doi":"10.1016/j.cstp.2025.101381","DOIUrl":null,"url":null,"abstract":"<div><div>Demand-response transit is the backbone of many rural transit systems. Demand-response transit provides riders with curb-to-curb service, not following fixed routes or schedules. While automated and semi-automated demand response scheduling has existed for decades, many agencies create schedules manually, using some form of computer-assisted schedule management. However, some transit agencies have recently adopted “microtransit” scheduling software packages that place an increasingly strong focus on fully automating the creation of schedules, and providing same-day service. In this article, we evaluate the recent implementation of automated scheduling software at two rural agencies in North Carolina.</div><div>We visited both agencies and conducted in-depth observations of their scheduling staff’s use of the software, as well as interviews with management. We found that neither agency used automated scheduling features of their software extensively. There were two main reasons for this. Firstly, automated scheduling was not seen as necessary; schedulers are experts on their regions and customers, and can create efficient schedules manually. Secondly, automated scheduling did not always match the service pattern of the agency, for instance by insufficiently prioritizing shared rides.</div><div>Agencies considering software purchases should consider what their needs and desires for a microtransit or automated scheduling system are. This process should involve both management and scheduling staff, to ensure the purchased system meets the needs of the agency. Automated scheduling and microtransit systems may not be a good fit for all agencies, particularly if existing scheduling practices are already working well.</div></div>","PeriodicalId":46989,"journal":{"name":"Case Studies on Transport Policy","volume":"19 ","pages":"Article 101381"},"PeriodicalIF":2.4000,"publicationDate":"2025-01-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Case Studies on Transport Policy","FirstCategoryId":"1085","ListUrlMain":"https://www.sciencedirect.com/science/article/pii/S2213624X25000185","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"Q3","JCRName":"TRANSPORTATION","Score":null,"Total":0}
引用次数: 0
Abstract
Demand-response transit is the backbone of many rural transit systems. Demand-response transit provides riders with curb-to-curb service, not following fixed routes or schedules. While automated and semi-automated demand response scheduling has existed for decades, many agencies create schedules manually, using some form of computer-assisted schedule management. However, some transit agencies have recently adopted “microtransit” scheduling software packages that place an increasingly strong focus on fully automating the creation of schedules, and providing same-day service. In this article, we evaluate the recent implementation of automated scheduling software at two rural agencies in North Carolina.
We visited both agencies and conducted in-depth observations of their scheduling staff’s use of the software, as well as interviews with management. We found that neither agency used automated scheduling features of their software extensively. There were two main reasons for this. Firstly, automated scheduling was not seen as necessary; schedulers are experts on their regions and customers, and can create efficient schedules manually. Secondly, automated scheduling did not always match the service pattern of the agency, for instance by insufficiently prioritizing shared rides.
Agencies considering software purchases should consider what their needs and desires for a microtransit or automated scheduling system are. This process should involve both management and scheduling staff, to ensure the purchased system meets the needs of the agency. Automated scheduling and microtransit systems may not be a good fit for all agencies, particularly if existing scheduling practices are already working well.