Transportation Information Center --> Transit Management Center:
trip confirmation

Definitions

trip confirmation (Information Flow): 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.

Transportation Information Center (Source Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.

Transit Management Center (Destination Physical Object): The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems.

Included In

This Triple is in the following Service Packages:

• PT03: Dynamic Transit Operations
• TI04: Trip Planning and Payment

This triple is associated with the following Functional Objects:

• TIC Trip Planning
• Transit Center Connection Protection
• Transit Center Paratransit Operations

This Triple is described by the following Functional View Data Flows:

• paratransit_service_confirmation
• transit_trip_confirmation

This Triple has the following triple relationships:

Communication Solutions

• US: TOMP - Secure Internet (ITS) (3)
• (None-Data) - Secure Internet (ITS) (32)
• (None-Data) - Apache Kafka (36)
• (None-Data) - OMG DDS (36)
• (None-Data) - OASIS MQTT (42)
• (None-Data) - OASIS AMQP (45)

Selected Solution

(None-Data) - Secure Internet (ITS)

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Bundle: SNMPv3 MIB	Facilities Development needed	Security Secure Session Alternatives
	TransNet IP Alternatives Internet Transport Alternatives
	Access Internet Subnet Alternatives

Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.

Characteristics

Security