Transportation Information Center --> TIC Operator:
TIC operations information presentation
Definitions
TIC operations information presentation (Information Flow): Presentation of information to the TIC Operator including current operational status, parameters for broadcast information settings, route selection controls, and travel optimization algorithms.
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.
TIC Operator (Destination Physical Object): This 'TIC Operator' represents the person or people that monitor and manage traveler information services provided by the Transportation Information Center.
Included In
This Triple is in the following Service Packages:
- PS10: Wide-Area Alert
- PS14: Disaster Traveler Information
- TI01: Broadcast Traveler Information
- TI02: Personalized Traveler Information
- TI03: En-Route Guidance
- TI04: Trip Planning and Payment
- TI06: Shared Use Mobility and Dynamic Ridesharing
- TI08: Personal Wayfinding
- TI09: Travel Services Information and Reservation
- WX03: Spot Weather Impact Warning
This triple is associated with the following Functional Objects:
- TIC Connected Vehicle Traveler Info Distribution
- TIC Data Collection
- TIC Dynamic Ridesharing
- TIC Emergency Traveler Information
- TIC Interactive Traveler Information
- TIC Road Weather Advisories and Warnings
- TIC Travel Services Information and Reservation
- TIC Traveler Information Broadcast
- TIC Traveler Telephone Information
- TIC Trip Planning
- TIC Wayfinding Information Dissemination
- TIC Wayfinding Planning
This Triple is described by the following Functional View Data Flows:
- ttico-archive_status
- ttico-data_collection_parameters
- ttico-route_selection_parameters
- ttico-trav_info_equip_status
- ttico-travel_services_operator_information
- ttico-traveler_data_collected
- ttico-traveler_information_parameters
- ttico-traveler_services_data
- ttico-trip_planning_data
- ttico-trip_planning_parameters
This Triple has the following triple relationships:
| None |
Communication Solutions
No communications solutions identified.Characteristics
| None defined |
| Interoperability | Description |
|---|---|
| Not Applicable | Interoperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability. |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Moderate | High | High | |
| Basis | Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | |