Home > Architecture > User Services >

2.3 Personalized Public Transit (User Service*)

The Personalized Public Transit user service supports flexibly routed transit vehicles. Small, publicly or privately operated vehicles provide on-demand routing to pick up passengers who have requested service and deliver them to their destinations. Route deviation schemes, where vehicles would leave a fixed route for a short distance to pick up or discharge passengers, is another approach employed to improve service. Vehicles providing this service can include small buses, taxicabs, or other small, shared-ride vehicles.

---

User Service Requirements*:

2.3.0	ITS shall include a Personalized Public Transit (PPT) function.
	PSpecs*: 10 , 10 , 4.1.8 , 4.2.1.1 , 4.2.1.2 , 4.2.1.3 , 4.2.1.4 , 4.2.1.5 , 4.2.1.6 , 4.2.3.3 , 4.2.3.5 , 4.2.3.6 , 4.2.3.7 , 4.5.2 , 4.5.5 , 4.6.1 , 4.6.4 , 5.1.5 , 6.1.1 , 6.3.2 , 6.3.3 , 6.4.4 , 6.8.3.2 , 6.8.3.3 , 7.3.1.3 , 7.4.1.2
2.3.1	The PPT shall include a Rider Request function.
	PSpecs*: 4.2.1.1 , 4.2.1.4 , 6.1.1 , 6.3.2 , 6.3.3 , 6.4.4 , 6.8.3.2 , 6.8.3.3
2.3.1.1	Rider Request shall provide the capability for an individual rider to request a trip by specifying the trip origin and destination, time and date.
	PSpecs*: 4.2.1.1
2.3.1.2	Rider Request shall provide the capability for an individual to specify a rider's special equipment or handling requirements.
	PSpecs*: 4.2.1.1 , 6.1.1
2.3.1.3	Rider Request shall provide the capability to notify a requester of the fact that a trip assignment has been made including the time at which the vehicle is expected at the point of departure.
	PSpecs*: 4.2.1.4 , 6.3.2 , 6.4.4 , 6.8.3.2
2.3.1.4	Rider Request shall include the capability to notify the requester that the transit vehicle's arrival is imminent.
	PSpecs*: 6.3.2 , 6.4.4 , 6.8.3.2
2.3.2	The PPT shall include a Vehicle Assignment function.
	PSpecs*: 4.1.8 , 4.2.1.1 , 4.2.1.2 , 4.2.1.3 , 4.2.1.4 , 4.2.3.3 , 4.2.3.6 , 4.2.3.7
2.3.2.1	Vehicle Assignment shall utilize vehicle availability, special requirements and rides requested information to determine vehicle assignments and routing.
	PSpecs*: 4.2.1.3
2.3.2.2	For random route operations Vehicle Assignment shall assign trip origin and destination.
	PSpecs*: 4.2.1.3 , 4.2.1.4 , 4.2.3.3 , 4.2.3.6
2.3.2.3	For flexible route operations Vehicle Assignment shall control how fixed route buses are detoured.
	PSpecs*: 4.2.1.3 , 4.2.1.4 , 4.2.3.3 , 4.2.3.6
2.3.2.4	For reservation based random-route operations Vehicle Assignment shall provide the capability to plan routes that optimize vehicle schedules while considering passengers' needs.
	PSpecs*: 4.2.1.3
2.3.2.5	Vehicle Assignment shall provide the capability to select the best match between riders' needs and the available vehicles.
	PSpecs*: 4.2.1.3
2.3.2.6	Vehicle Assignment shall provide services to both publicly owned and privately owned, publicly licensed vehicles.
	PSpecs*: 4.2.1.2 , 4.2.1.3
2.3.2.7	In order to service travelers in low-demand time (e.g., night time and weekends) Vehicle Assignment shall provide services 24 hours per day, 7 days per week.
	PSpecs*: 4.2.1.1 , 4.2.1.2 , 4.2.1.3
2.3.2.8	Vehicle Assignment shall assign vehicle routes within 4 blocks of rider's trip origin point.
	PSpecs*: 4.2.1.3
2.3.2.9	Vehicle Assignment shall be a real-time system.
	PSpecs*: 4.2.1.3
2.3.2.10	Vehicle Assignment shall provide the capability to accommodate immediate trip requests when enough capacity is available for the added rider pickup and delivery.
	PSpecs*: 4.2.1.3
2.3.2.11	Vehicle Assignment shall provide the capability to provide a protected transfer between routes.
	PSpecs*: 4.1.8 , 4.2.3.7
2.3.3	The PPT shall include a Data Collection function.
	PSpecs*: 4.2.1.5 , 4.6.1 , 4.6.4 , 7.3.1.3
2.3.3.1	Data Collection shall include on-board sensors to monitor, but not be limited to, the following:
	PSpecs*: 4.2.1.5 , 4.6.1 , 4.6.4 , 7.3.1.3
2.3.3.1(a)	Vehicle location.
	PSpecs*: 4.2.1.5
2.3.3.1(b)	Passenger loading.
	PSpecs*: 4.2.1.5
2.3.3.1(c)	Fare collection.
	PSpecs*: 4.2.1.5 , 4.6.1 , 4.6.4 , 7.3.1.3
2.3.3.2	Data Collection shall process and store collected data so that it is available for:
	PSpecs*: 4.2.1.5
2.3.3.2(a)	Real-time schedule adjustments.
	PSpecs*: 4.2.1.5
2.3.3.2(b)	Off-line analysis and planning.
	PSpecs*: 4.2.1.5
2.3.3.3	Data Collection shall support the off-line billing for fares paid by agencies.
	PSpecs*: 4.2.1.5 , 7.3.1.3
2.3.4	The PPT shall include an Information Processing function.
	PSpecs*: 10 , 10 , 4.2.1.3 , 4.2.1.4 , 4.2.3.5 , 4.5.2 , 4.5.5 , 5.1.5 , 7.4.1.2
2.3.4.1	PPT shall be implemented such that Information Processing may be located either centrally or distributed.
	PSpecs*: 10 , 10
2.3.4.2	Information Processing shall use information to attempt to minimize the amount of time each passenger must ride.
	PSpecs*: 4.2.1.3
2.3.4.3	Information Processing shall provide the capability to automate the assignment of drivers to vehicles.
	PSpecs*: 4.2.1.4 , 4.5.2 , 4.5.5
2.3.5	The PPT shall include a Communications function.
	PSpecs*: 4.2.1.6
2.3.5.1	The Communications function shall provide the capability to link all PPT services into a single entity.
	PSpecs*: 4.2.1.6
2.3.5.2	The Communications function shall provide a two-way communications capability between vehicles and a central base for:
	PSpecs*: 4.2.1.6
2.3.5.2(a)	Voice communications.
	PSpecs*: 4.2.1.6
2.3.5.2(b)	Data communications.
	PSpecs*: 4.2.1.6
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.
	PSpecs*: 4.2.1.6
2.3.5.4	The Communications function shall provide the capability for data to be transferred between dispersed points and central base including:
	PSpecs*: 4.2.1.6
2.3.5.4(a)	Data from vehicles.
	PSpecs*: 4.2.1.6
2.3.5.4(b)	Data from locations where passengers are located.
	PSpecs*: 4.2.1.6