Hartford Area ITS Architecture Update

Element Expanded Functional Requirements: CTRIDES.COM

Functional Area: Infrastructure Provided Dynamic Ridesharing
  1. The center shall accept requests from traveler interface systems for ridesharing as part of a trip plan request.
  2. The center shall provide a rideshare match based on origin and destination of the traveler's proposed trip, any routing constraints, preferences specified by the traveler, compatibility of this rideshare with rideshares confirmed by other travelers, the requesting traveler's eligibility data, and traffic data.
  3. The center shall process rideshare requests by balancing the relative benefits of the rideshare to each rideshare participant.
  4. The center shall arrange connections to transit or other multimodal services for portions of a multi-segment trip that includes ridesharing.
  5. The center shall provide a confirmation of the traveler's rideshare match and provide the capability to support a payment transaction for the rideshare service.
  6. The center shall store all rideshare matches and traveler eligibility data.
Functional Area: Infrastructure Provided Trip Planning
  1. The center shall provide the capability to provide specific pre-trip and enroute directions to travelers (and drivers), including costs, arrival times, and transfer points.
  2. The center shall include bicycle routes, walkways, skyways, and multi-use trails in the pre-trip and enroute directions it provides to travelers.
  3. The center shall support on-line route guidance for travelers using personal devices (such as PDAs).
  4. The center shall support on-line route guidance for drivers in vehicles.
  5. The center shall support on-line route guidance for specialty vehicles, such as commercial vehicles.
  6. The center shall generate route plans based on current and/or predicted conditions of the road network, scheduled maintenance and construction work activities, and work zone activities.
  7. The center shall generate route plans based on transit services, including fares, schedules, and requirements for travelers with special needs.
  8. The center shall generate route plans based on current asset restrictions, such as height and weight restrictions on tunnels or bridges.
  9. The center shall generate route plans based on current or forecasted weather.
  10. The center shall generate route plans based on ferry, rail, air, or other multimodal transportation data.
  11. The center shall exchange route segment information with other centers outside the area served by the local center.
  12. The center shall generate trips based on the use of more than one mode of transport.
  13. The center shall use the preferences and constraints specified by the traveler in the trip request to select the most appropriate mode of transport.
  14. The center shall provide the capability for the traveler to confirm the proposed trip plan.
  15. The center shall log route plans, particularly for special vehicles such as those containing hazardous materials, over-sized vehicles, or motorcades, with a traffic center.
  16. The center shall support an interface with a map update provider, or other appropriate data sources, through which updates of digitized map data can be obtained and used to determine vehicle and non-vehicle routes, trip planning, and on-line vehicle guidance.
  17. The center shall provide the capability for center personnel to control route calculation parameters.