Transit Management Center --> Archived Data System:
transit archive data

Definitions

transit archive data (Information Flow): Data used to describe and monitor transit demand, fares, operations, and system performance. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.

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 support communication between transit departments and with other operating entities such as emergency response services and traffic management systems.

Archived Data System (Destination Physical Object): The 'Archived Data System' collects, archives, manages, and distributes data generated from ITS sources for use in transportation administration, policy evaluation, safety, planning, performance monitoring, program assessment, operations, and research applications. The data received is formatted and tagged with attributes that define the data source, conditions under which it was collected, data transformations, and other information (i.e. meta data) necessary to interpret the data. The archive can fuse ITS generated data with data from non-ITS sources and other archives to generate information products utilizing data from multiple functional areas, modes, and jurisdictions. The archive prepares data products that can serve as inputs to federal, state, and local data reporting systems. The 'Archived Data System' may reside within an operational center and provide focused access to a particular agency's data archives. Alternatively, it may operate as a distinct center that collects data from multiple agencies and sources and provides a general data warehouse service.

Included In

This Triple is in the following Service Packages:

• DM01: ITS Data Warehouse

This triple is associated with the following Functional Objects:

• Archive Data Repository
• Transit Center Data Collection

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

• transit_archive_data

This Triple has the following triple relationships:

Communication Solutions

• US: TIDES - Secure Internet (ITS) (3)
• (None-Data) - Secure Internet (ITS) (32)
• US: ADMS - Secure Internet (ITS) (32)
• Data for Distribution (TBD) - Apache Kafka (36)
• Data for Distribution (TBD) - OMG DDS (36)
• (None-Data) - OASIS MQTT (42)
• Data for Distribution (TBD) - OASIS MQTT (42)
• (None-Data) - OASIS AMQP (45)
• Data for Distribution (TBD) - OASIS AMQP (45)

Selected Solution

Data for Distribution (TBD) - OASIS MQTT

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt OASIS MQTT DMP	Facilities OASIS MQTT	Security IP Security Alternatives OASIS MQTT
	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