|
|
Equipment Package: Transit Data Collection |
| Description: |
This equipment package collects and stores transit information that is collected in the course of transit operations performed by the Transit Management Subsystem. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. |
| Included In: |
Capital Corridor Train Operations Center
Capitol Corridor Train Stations
El Dorado Transit Dispatch
e-tran Transit Center
Folsom Stage Lines Transit Dispatch
Light Rail Transit Management Center
Local Transit Dispatch Centers
Paratransit, Inc.
Roseville Transit Management Center (Dispatch)
RT Transit Management Center
Unitrans Transit Dispatch
Yolo Bus Dispatch Center
Yuba-Sutter Transit Center
|
| Processes: |
4.2.4 - Manage Transit Archive Data
|
| User Service Requirements: |
7.0 -
INFORMATION MANAGEMENT
7.1 -
ARCHIVED DATA FUNCTION
7.1.0 -
ITS shall provide an Archived Data Function to control the archiving and distribution of ITS data. The Archived Data User Service provides the Historical Data Archive Repositories and controls the archiving functionality for all ITS data with five major functions: 1) the Operational Data Control function to manage operations data integrity; 2) the Data Import and Verification function to acquire historical data from the Operational Data Control function; 3) the Automatic Data Historical Archive function for permanently archiving the data; 4) the Data Warehouse Distribution function, which integrates the planning, safety, operations, and research communities into ITS and processes data products for these communities; and 5) the ITS Community Interface which provides the ITS common interface to all ITS users for data products specification and retrieval. ADUS helps achieve the ITS information goal of unambiguous interchange and reuse of data and information throughout all functional areas.
7.1.3 -
The Archived Data Function shall include a Data Import and Verification (DIV) function to acquire historical data from the Operational Data Control function.
7.1.3.1 -
DIV shall be capable of importing selected ITS Operational data from the ITS Operational Repositories.
7.1.3.1.4 -
DIV shall be capable of importing ITS Transit and Ridesharing data to include:
7.1.3.1.4(a) -
Transit usage data.
7.1.3.1.4(b) -
Transit route data including schedule deviations.
7.1.3.1.4(d) -
Multimodal Origin/Destination.
7.1.3.1.4(e) -
Fares
7.1.3.1.4(f) -
Vehicle maintenance
7.1.3.1.4(g) -
Personnel management data
7.1.3.1.9 -
DIV shall be capable of importing data on ITS Physical Characteristics of Transportation Infrastructure to include:
7.1.3.1.9(b) -
Transit network attributes.
7.1.3.1.9(c) -
Equipment maintenance status
7.1.3.1.9(d) -
Transportation facilities.
7.1.3.1.9(e) -
GIS map of network.
|
Last updated: 04-29-05 |
