Maintaining Transit Effectiveness Under Major Financial Constraints (2014) / Chapter Skim
Currently Skimming:
Pages 100-103
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 100... ...
100 The following information was provided by Long Beach Transit in Long Beach, California: • From a service perspective, improvements in the run-cutting algorithm implemented in the 2008 upgrade of our HASTUS scheduling software have resulted in an increase in the number of straight runs available without any corresponding increase in costs. • Information from GFI ridership reports has allowed service to be reduced on poorly performing services in order to be added onto overcrowded services with no effect on ridership and no complaints.
|
From page 101... ...
101 WMATA implemented the Fleetwatch fl uid management system. Fleetwatch monitors fl uids used and mileage in both our revenue and service fl eets.
|
From page 102... ...
102 backed up in an alternate data center. We took this opportunity to make the new solution fault-tolerant and set up fail-over instances in our backup data center.
|
From page 103... ...
103 Business intelligence. The agency is just now implementing this new data analysis technology that will greatly assist in retrieving large amounts of data created primarily by the APTS, ORCA, and Trapeze OPS systems and allow for intuitive data visualization and easy ad hoc/decision support reporting, including the creation of dashboards.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.