Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.
Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.
OCR for page 12
12 Table 3. Vendor workshop participants. This thrust, in its effort to accelerate the cycle of develop- ment, had two facets: TriTAPT and improved analysis tools. Type Participants Delft University's software package TriTAPT contains analy- Vendor Dirk van Dijl, ACIS sis tools related to running time and passenger counting. Representatives Alain de Chene, Infodev Carol Yates, Orbital Under the terms of this project, this software will be available George Mount, NextBus with no license fee for 4 years to transit agencies in the United Andreas Rackebrandt, INIT Neil Odle, IRIS States and Canada. In the course of the project, it was tested by Anil Panaghat, US Holdings three agencies (Tri-Met, Metro Transit, and the Massachusetts Vijay Raganath, consultant with Bay Transportation Authority [MBTA]); and the feedback was Delaware Transit Hershang Pandya, US Holdings used to help adapt it to U.S. practice. Rohit Patel, Intelect Corporation The second facet was the development of improved analy- Mike Kushner, Logic Tree sis tools. Improved tools for running time analysis were Panel Members, Jim Kemp, NJ Transit (panel chair) Liaisons, and Wei-Bin Zhang, Univ. of California developed within TriTAPT, while prototype tools for ana- Additional PATH program lyzing passenger waiting time and crowding were developed Reviewers Fabian Cevallos, Broward County Transit on a spreadsheet platform. Gerald Pachucki, Utah Transit Authority Tom Friedman, King County Metro Kimberly Slaughter, S.R. Beard 1.4 Report Outline Erin Mitchell, Metro Transit Yuko Nakanishi, Research and This chapter describes the historical background, the Consulting Sarah Clements, FTA research objective, the research approach, and the case Bob Casey, U.S.DOT Volpe Center study sites. Stephan Parker, TRB Chapters 2 and 3 review systems used to collect data. Chap- Eric Bruun, consultant Case Study Site Steve Callas, Tri-Met ter 2 covers the core vehicle location system including on- Representatives Kevin O'Malley, CTA board computer and communication. Chapter 3 covers other (in addition to Michel Thérer, STM panel members on-board devices that can be part of a data collection system. Glenn Newman, NJ Transit already listed) These chapters analyze how the design of an AVL system affects the types and quality of data that it delivers. 1.3.2 Analysis of Data Systems Chapter 4 reviews actual and potential uses of archived and Opportunities AVL-APC data, analyzing for each use the kind of AVL-APC data it requires. With the previous two chapters, it provides the The second thrust of the research was identifying actual and logical progression from data use to data collection system potential ways that archived AVL-APC data could be used and (i.e., what kind of data is needed to perform a certain type of analyzing these identified ways in terms of needs for data cap- analysis and what kind of data collection system is needed to ture, accuracy and sample size, data structures, and analysis collect that data). methods. At the same time, data collection and database sys- Chapters 5 through 7 describe specific analysis tools that tem designs were analyzed in terms of their capability for sat- were developed in the course of this project: tools for analyzing isfying those needs. Based on that comparison, the researchers running time, passenger waiting time, and passenger crowding. developed guidance regarding system design. Chapters 8 and 9 focus on passenger count data. Chapter 8 Another part of this thrust was the development, as a proof deals with schedule matching, trip parsing, and load bal- of concept, of one innovative data structure for analyzing serv- ancing methods and includes some newly developed pars- ice on a trunk shared by multiple patterns or lines. ing and balancing methods. Chapter 9 deals with sampling issues and, in particular, how APC data can be used to esti- 1.3.3 Development and Demonstration mate annual systemwide passenger-miles in order to satisfy of Improved Tools NTD requirements. If there is no good archived data, there appears to be no Chapters 10 and 11 offer guidance on the design of auto- need to develop tools to analyze it. And if there are no useful matic data collection systems (Chapter 10) and on the design of tools to apply, there appears to be no need to purchase a sys- software used to store and analyze archived data (Chapter 11). tem to gather the data. Because of this chicken-and-egg rela- Chapter 12 discusses organizational issues associated with tionship between analysis tools and the practice of capturing AVL-APC data collection and archiving. Chapter 13 offers and archiving data, the third main thrust of this project was conclusions. to develop and demonstrate the use of improved analysis Appendixes A through I, previously published as part of tools that take advantage of archived AVL-APC data. TCRP Web-Only Document 23, are case studies.
OCR for page 13
13 Part of this project was the development of software analy- Other products of this project were three papers published sis tools. Spreadsheet tools for analyzing passenger waiting time in Transportation Research Record: Journal of the Transportation and crowding, described in Chapters 6 and 7, are available on Research Board. the project description web page for TCRP Project H-28 on the TRB website (www.trb.org). TriTAPT, which contains a suite of · "Designing Automated Vehicle Location Systems for analysis tools including running time analysis tools developed Archived Data Analysis" (6) contains material that is sum- in this project, is available with no license fee to U.S. and Cana- marized in Chapters 2, 3, 4, and 10. dian transit operators through the end of 2009; to request a · "Making Automatic Passenger Counts Mainstream: Accu- copy including documentation, sample data files, and a set racy, Balancing Algorithms, and Data Structures" (7) con- of input data conversion routines, please e-mail a request to tains material that is reproduced in Chapters 8 and 9. email@example.com. The conversion routines were developed · "Service Reliability and Hidden Waiting Time: Insights for the native format of input data used by those agencies that from AVL Data" (8) contains material that is covered in until now have used TriTAPT; agencies may have to adapt them Chapter 6, as well as theoretical material that is not repeated to their particular input file formats. in this report.