Personal Information Access (Subsystem*)

The Personal Information Access Subsystem (PIAS) provides the capability for travelers to receive formatted traffic advisories from their homes, place of work, major trip generation sites, personal portable devices, over multiple types of electronic media. These capabilities also provide basic routing information and allow users to select those transportation modes that allow them to avoid congestion, or more advanced capabilities to allow users to specify those transportation parameters that are unique to their individual needs and receive travel information. This subsystem provides travelers with the capability to receive route planning from the infrastructure at fixed locations such as in their homes, their place of work, and at mobile locations using personal portable devices and vehicle-based devices. In addition to end user devices, this subsystem may also represent a device that is used by a merchant or other service provider to receive traveler information and relay important information to their customers. This subsystem also provides the capability to initiate a distress signal and cancel a prior-issued manual request for help.

Functionality
Inputs/Outputs
Security
Subsystem Interfaces Diagram
Terminator Interfaces Diagram

Subsystem Interfaces Diagram

This is a context diagram for the entity Personal Information Access Subsystem that shows the interfaces to subsystems and every architecture flow that this entity sends or receives, as defined in the National ITS Architecture. A complete list of all architecture flows shown on this diagram, is available under the Inputs/Outputs section on this page.

Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.

Terminator Interfaces Diagram

Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.

Security Considerations:

Security considerations for Personal Information Access include the measures necessary to safeguard the personal and financial information that may be entered by individual users. Personal Information Access subsystem equipment is typically privately owned and operated, and includes the use of portable or handheld devices. Devices such as these are prone to theft and misuse. Information coming from these personal devices should be authenticated to verify that the requester is who they say they are and that the information they are given is limited to the information requested or to information that is available to the public. In general, the Personal Information Access Subsystem handles personal and financial information that needs a relatively low degree of confidentiality to safeguard the information. In addition, it is important but not essential that the information is available. The integrity of the information is also important in order to prevent improper financial transactions and accessibility to unauthorized information.

Functionality: Equipment Packages* and PSpecs*

Personal Autonomous Route Guidance (Equipment Package*)
PSpecs:
- 6.8.1.1.3-Provide Personal Portable Device Autonomous Guidance
- 6.8.1.2-Provide Personal Portable Device Guidance Interface
- 6.8.1.4-Update Traveler Navigable Map Database
- 6.8.3.4-Update Traveler Personal Display Map Data
Personal Basic Information Reception (Equipment Package*)
PSpecs:
- 6.8.3.2-Provide Traveler with Personal Travel Information
- 6.8.3.3-Provide Traveler Personal Interface
Personal Interactive Information Reception (Equipment Package*)
PSpecs:
- 6.8.3.1-Get Traveler Personal Request
- 6.8.3.2-Provide Traveler with Personal Travel Information
- 6.8.3.3-Provide Traveler Personal Interface
- 7.5.3-Provide Personal Traveler Card Interface
- 7.6.6.3-Provide VMT Services Personal Interface
Personal Location Determination (Equipment Package*)
PSpecs:
- 6.8.1.3-Process Personal Portable Device Location Data
Personal Mayday I/F (Equipment Package*)
PSpecs:
- 6.8.1.5-Provide Traveler Emergency Message Interface
- 6.8.2.1-Build Traveler Personal Security Message
- 6.8.2.2-Provide Traveler Emergency Communications Function
Personal Trip Planning and Route Guidance (Equipment Package*)
PSpecs:
- 6.8.1.1.1-Determine Personal Portable Device Guidance Method
- 6.8.1.1.2-Provide Personal Portable Device Dynamic Guidance
- 6.8.1.2-Provide Personal Portable Device Guidance Interface
- 6.8.1.4-Update Traveler Navigable Map Database
- 6.8.3.1-Get Traveler Personal Request
- 6.8.3.2-Provide Traveler with Personal Travel Information
- 6.8.3.3-Provide Traveler Personal Interface

Inputs/Outputs: Architecture Flows* and Data Flows*

Emergency Management Personal Information Access

emergency acknowledge (Architecture Flow*) - Acknowledge request for emergency assistance and provide additional details regarding actions and verification requirements.
Data Flows*:
- emergency_request_personal_traveler_acknowledge

Information Service Provider Personal Information Access

broadcast traveler information (Architecture Flow*) - General traveler information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveler information.
Data Flows*:
emergency traveler information (Architecture Flow*) - 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.
Data Flows*:
interactive traveler information (Architecture Flow*) - Traveler information provided in response to a traveler request. The provided information includes traffic and road conditions, advisories, incidents, payment information, transit services, parking information, weather information, and other travel-related data updates and confirmations.
Data Flows*:
travel services information (Architecture Flow*) - Travel service information and reservations for tourist attractions, lodging, dining, service stations, emergency services, and other services and businesses of interest to the traveler.
Data Flows*:
- traveler_personal_transaction_confirmation
- traveler_personal_travel_services_provider_data
traveler alerts (Architecture Flow*) - 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.
Data Flows*:
trip plan (Architecture Flow*) - 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.
Data Flows*:

Location Data Source Personal Information Access

position fix (Architecture Flow*) - Information which provides a traveler's or vehicle's geographical position.
Data Flows*:
- From_Location_Data_Source

Map Update Provider Personal Information Access

map updates (Architecture Flow*) - Map update which could include a new underlying static or real-time map or map layer(s) update.
Data Flows*:

Payment Administration Personal Information Access

traveler payment request (Architecture Flow*) - Request for payment for road use charges.
Data Flows*:
- traveler_personal_vmt_payment_request
user VMT account reports (Architecture Flow*) - Reports on VMT charges
Data Flows*:
- traveler_personal_vmt_account_reports

Personal Information Access Emergency Management

emergency notification (Architecture Flow*) - An emergency request for assistance automatically initiated by a vehicle or originated by a traveler using an in-vehicle or personal device.
Data Flows*:
- emergency_request_personal_traveler_details

Personal Information Access Information Service Provider

emergency traveler information request (Architecture Flow*) - Request for alerts, evacuation information, and other emergency information provided to the traveling public.
Data Flows*:
- traveler_personal_emergency_information_request
travel services request (Architecture Flow*) - 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.
Data Flows*:
traveler profile (Architecture Flow*) - Information about a traveler including equipment capabilities, personal preferences, and traveler alert subscriptions.
Data Flows*:
- traveler_personal_alert_subscriptions
- traveler_personal_profile
traveler request (Architecture Flow*) - 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.
Data Flows*:
trip confirmation (Architecture Flow*) - Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
Data Flows*:
trip request (Architecture Flow*) - Request for trip planning services that identifies the trip origin, destination(s), timing, preferences, and constraints. The request may also include a request for transit and parking reservations and ridesharing options associated with the trip.
Data Flows*:
- traveler_personal_trip_request
- traveler_route_request

Personal Information Access Map Update Provider

map update request (Architecture Flow*) - Request for a map update which could include a new underlying map or map layer updates.
Data Flows*:

Personal Information Access Payment Administration

traveler payment information (Architecture Flow*) - Payment information for road use charges.
Data Flows*:
- traveler_personal_vmt_payment_info
user VMT account setup (Architecture Flow*) - Billing information, vehicle information (or registration information), and requests for reports.
Data Flows*:
- traveler_personal_vmt_account_setup_info

Personal Information Access Transit Management

transit information user request (Architecture Flow*) - Request for special transit routing, real-time schedule information, and availability information.
Data Flows*:
- transit_services_personal_request
- transit_trip_request_from_user
trip confirmation (Architecture Flow*) - Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
Data Flows*:
- transit_trip_confirmation_from_user

Personal Information Access Traveler

traveler interface updates (Architecture Flow*) - Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler.
Data Flows*:

Personal Information Access Traveler Card

request for payment (Architecture Flow*) - Request to deduct cost of service from user's payment account.
Data Flows*:
- ttc-debited_payment_at_personal_device
traveler card update (Architecture Flow*) - Information updated concerning traveler's personal data including items such as address, trip records, and profile data.
Data Flows*:
- ttc-traveler_personal_information_update

Transit Management Personal Information Access

personal transit information (Architecture Flow*) - General and personalized transit information for a particular fixed route, flexible route, or paratransit system.
Data Flows*:
trip plan (Architecture Flow*) - 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.
Data Flows*:
- transit_trip_plan_for_user

Traveler Personal Information Access

traveler inputs (Architecture Flow*) - User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service.
Data Flows*:

Traveler Card Personal Information Access

payment (Architecture Flow*) - Payment of some kind (e.g., toll, parking, fare) by traveler which, in most cases, can be related to a credit account.
Data Flows*:
- ftc-traveler_personal_input_credit_identity
traveler card information (Architecture Flow*) - The traveler personal information such as name, address, license number, and trip records and profile data.
Data Flows*:
- ftc-traveler_personal_information