13. For the Transit Bus Automation Demonstrations, can you clarify the types of data that are expected to be collected? (7/9/2019)
Appropriate data will vary according to the scope and goals of the proposed project. Applicants should consider the feasibility of obtaining and sharing data in preparing their proposals. In addition, appropriate data should be collected to support evaluation of the demonstrated system. The following is an illustrative list of possible data types and elements:
- Vehicle performance data with respect to operations and maintenance (e.g., dwell time, total service provided (vehicle-miles/vehicle-hours), percentage of automated vs manual operation, fuel efficiency, battery life, emissions, travel times, and average vehicle speed)
- Automation component and system data (e.g., number and types of sensors and actuators, human-machine interface [HMI] design, confidence information in object detection and classification)
- Safety data (e.g., notifications, disengagements, emergency driver takeover, incidents, and edge cases/near-misses, rules-of-the-road compliance; boarding and alighting incidents)
- Costs (e.g., vehicle procurement, operation, maintenance, storage; infrastructure improvements; labor and training; other ongoing operational costs; vehicle out-of-service time)
- Mobility impacts (e.g., passenger counts, percentage of scheduled trips completed, on-time arrival, average passenger wait time, and major origin-destination patterns, and rider demographics)
- Human factors (e.g., on-board attendant experience and alertness, customer experience and satisfaction, accessibility metrics, and passenger safety metrics)
- Data from ancillary systems that support non-driving bus operator functions (e.g., fare collection, ramp deployment and retraction, wheelchair securement, occupant detection, and passenger information assistance)
- Infrastructure and system performance data (e.g., vehicle-to-infrastructure [V2I] communications and equipment, congestion, average traffic speed)
- Cybersecurity (e.g., cybersecurity assessments [which may include threat analysis and risk assessment (TARA) results, cybersecurity mitigation measures, penetration testing results, etc.], incident frequency and response time, vulnerability data, staffing/training levels)