emergency transit schedule information Quintuple

Bidirectional?: False

emergency transit schedule information (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between two application objects: 'Transit Evacuation Support', and 'TIC Data Collection'. In this case, there is only a single Layer 2 flow associated with this interconnect, so the Layer 1 application interconnect name and the Layer 2 information flow name are both 'emergency transit schedule information'. This application interconnect is uni-directional since the underlying layer 2 information flows go from 'Transit Management Center' to 'Transportation Information Center'.

Transit Management Center (Source 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 allow for communication between transit departments and with other operating entities such as emergency response services and traffic management systems.

Transit Evacuation Support (Source Application Object): "Transit Evacuation Support" manages transit resources to support evacuation and subsequent reentry of a population in the vicinity of a disaster or other emergency. It supports coordination of regional evacuation plans, identifying the transit role in a regional evacuation and identifying transit resources that would be used. During an evacuation, it coordinates the use of transit and school bus fleets, supporting evacuation of those with special needs and the general population. Transit service and fare schedules are adjusted and updated service and fare information is made available through traveler information systems.

Transportation Information Center (Destination 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 Data Collection (Destination Application Object): "TIC Data Collection" collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers.