2.0 | PUBLIC TRANSPORTATION MANAGEMENT |
2.3.0 | ITS shall include a Personalized Public Transit (PPT) function. |
2.3.3 | The PPT shall include a Data Collection function. |
2.3.3.1 | Data Collection shall include on-board sensors to monitor, but not be limited to, the following: |
2.3.3.1(a) | Vehicle location. |
2.3.3.1(b) | Passenger loading. |
2.3.3.1(c) | Fare collection. |
2.3.3.2 | Data Collection shall process and store collected data so that it is available for: |
2.3.3.2(a) | Real-time schedule adjustments. |
2.3.3.2(b) | Off-line analysis and planning. |
2.3.3.3 | Data Collection shall support the off-line billing for fares paid by agencies. |
2.3.5 | The PPT shall include a Communications function. |
2.3.5.1 | The Communications function shall provide the capability to link all PPT services into a single entity. |
2.3.5.2 | The Communications function shall provide a two-way communications capability between vehicles and a central base for: |
2.3.5.2(a) | Voice communications. |
2.3.5.2(b) | Data communications. |
2.3.5.3 | The Communications function shall provide the capability for sensor data (either raw or processed) to be transmitted from vehicles to a central headquarters or dispatch station. |
2.3.5.4 | The Communications function shall provide the capability for data to be transferred between dispersed points and central base including: |
2.3.5.4(a) | Data from vehicles. |
2.3.5.4(b) | Data from locations where passengers are located. |
| |