• About
  • Connected Vehicle
  • Architecture
  • Approach
  • Viewpoints
  • Security
• Applications
• Views
  • Enterprise
  • Functional
  • Physical
  • Communications
• Standards
  • CV Standards
  • CV Standards Plan
• Resources
  • Databases
  • Diagrams
  • Documents
  • Presentations
  • Tools
  • Training
• Glossary
  • Acronyms
• Contact Us

transit schedule adherence and incident information Quintuple

Bidirectional?: False

transit schedule adherence and incident information (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between two application objects: 'Transit Center Multi-Modal Coordination', and 'TIC Operational Data Repository'. 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 Center Multi-Modal Coordination (Source Application Object): "Transit Center Multi-Modal Coordination" supports transit service coordination between transit properties and coordinates with other surface and air transportation modes. As part of service coordination, it shares schedule and trip information, as well as transit transfer cluster (a collection of stop points, stations, or terminals where transfers can be made conveniently) and transfer point information between Multimodal Transportation Service Providers, Transit Agencies, and ISPs. An interface to Traffic Management also supports demand management strategies.

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 Operational Data Repository (Destination Application Object): "TIC Operational Data Repository" processes, stores, and distributes real-time information on the state of the regional transportation system. It facilitates sharing of real-time transportation information among transportation system operators. It includes a central repository, data processing, and communication capabilities that provide real-time access to the collected information. Many different implementations are possible including: 1) a web application that provides a web-based interface to system operators, and 2) a networked enterprise database that provides a network interface to remote system applications. Although request and subscription flows are not explicitly included, interactive data services are supported. The data may be broadcast or customized based on the receiving center's specified requests or subscriptions.