Interface: User Personal Information Devices - Trans Network Co-op (TNC) Centers

User Personal Information Devices to Trans Network Co-op (TNC) Centers Interface Diagram

Information Flow Definitions

actuate secure payment  (Existing)  

Initiation of a payment action based on an encrypted token or biometric marker.

emergency traveler information  (Planned)  

Public notification of an emergency such as a natural or man–made disaster, civil emergency, or child abduction. This flow also includes evacuation information including evacuation instructions, evacuation zones, recommended evacuation times, tailored evacuation routes and destinations, traffic and road conditions along the evacuation routes, traveler services and shelter information, and reentry times and instructions.

emergency traveler information request  (Planned)  

Request for alerts, evacuation information, and other emergency information provided to the traveling public.

evacuation assistance information  (Planned)  

Information on evacuation resources including self–evacuation options, anticipated pickup time and location if a transportation asset is to be deployed, destination shelter, and supporting information on what to bring, estimated reentry date/time.

evacuation assistance request  (Planned)  

A request for evacuation assistance, which may be registered in advance or issued during an evacuation. It specifies the location, number of people that need to be evacuated, and any special needs/requirements.

interactive traveler information  (Existing)  

Traveler information provided in response to a traveler request. The provided information includes traffic and road conditions, advisories, incidents, restrictions, payment information, transit services, parking information, weather information, and other travel–related data updates and confirmations.

registered secureIDs  (Existing)  

Cryptographically protected identifier indicating that the user associated with the identifier is entitled to use a particular service.

shared use confirmation  (Planned)  

Confirmation that traveler is going to use the shared use asset now or at a future time.

shared use request  (Planned)  

Request for shared use asset (e.g., car or bicycle) now or as a reservation for future use.

shared use response  (Planned)  

Response from shared use provider regarding availability of the shared use asset now or in the future. Includes any payment requirements.

shelter recommendations  (Planned)  

Recommendation identifying the shelter or shelters best suited to the requestor. Hotels/motels may also be included as potential sheltering options. This flow may also include shelter assignments/reservations.

shelter request  (Planned)  

A request for shelter information, recommendations, or assignment/reservation. Information provided my include name, current location, number of people in the group, additional requirements (e.g., evacuating with pets, needed medical support).

travel services information  (Planned)  

Travel service information and reservations for tourist attractions, lodging, dining, service stations, emergency services, and other services and businesses of interest to the traveler.

travel services request  (Planned)  

Request for travel service information including tourist attractions, lodging, restaurants, service stations, and emergency services. The request identifies the type of service, the area of interest, optional reservation request information, parameters that are used to prioritize or filter the returned information, and sorting preferences.

traveler alerts  (Existing)  

Traveler information alerts reporting congestion, incidents, adverse road or weather conditions, parking availability, transit service delays or interruptions, and other information that may impact the traveler. Relevant alerts are provided based on traveler–supplied profile information including trip characteristics and preferences.

traveler payment information  (Existing)  

Information provided for payment of road use charges, tolls or parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested. The information exchange normally supports an account debit to pay fees, but an account credit may be initiated where pricing strategies include incentives.

traveler payment request  (Existing)  

Request for information supporting payments. For fee structures that include incentives, the request may support either an account debit or an account credit or reimbursement.

traveler request  (Existing)  

A request for traveler information including traffic, transit, toll, parking, road weather conditions, event, and passenger rail information. The request identifies the type of information, the area of interest, parameters that are used to prioritize or filter the returned information, and sorting preferences.

traveler sourced updates  (Planned)  

Traveler posts on traffic and road conditions, parking availability, transit services, traveler services, shelter information and other real–time crowd–sourced data that may be shared with other travelers.

trip confirmation  (Planned)  

Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations. Conversely, this flow may also reject the proposed trip plan. Confirmations include the selected route and subsequent trip confirmation messages will be issued for route changes.

trip feedback  (Planned)  

Information provided at the conclusion of a trip that supports performance monitoring and system optimization. Information provided may include a record of the trip including HOV/HOT lane usage and user provided feedback at the conclusion of the trip.

trip plan  (Planned)  

A travel itinerary identifying a route and associated traveler information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information. This flow also includes intermediate information that is provided as the trip plan is interactively created, including identification of alternatives, requests for additional information.

trip request  (Planned)  

Request for trip planning services that identifies the trip origin, destination(s), timing, preferences, and constraints. The request may also include the requestor's location or a request for transit and parking reservations and ridesharing options associated with the trip. The trip request also covers requests to revise a previously planned trip and interim updates that are provided as the trip is interactively planned.

user account reports  (Existing)  

Reports on services offered/provided and associated charges.

user account setup  (Existing)  

Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes.

user profile  (Planned)  

Information provided to register for a travel service and create a user account. The provided information includes personal identification, traveler preferences (e.g., maximum transfer wait time, maximum walking distance, mode preferences, special needs), device information, a user ID and password, and information to support payment transactions, if applicable.