Regional Architecture Logo
 

Send Your Comments

E-Mail

Transit Data Collection Equipment Package

Architecture Geographic Scope

Description:

Collection and storage of transit management data. For use by operations personnel or data archives in the region.

 

Included in:

BTD Transit Dispatch

Functional Requirements:

1The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit operations, transit vehicle maintenance data, etc.
2The center shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.
3The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data itself.
4The center shall be able to produce sample products of the data available.
  

User Service Requirements (fully or partially addressed):

7.0INFORMATION MANAGEMENT
7.1ARCHIVED DATA FUNCTION
7.1.0ITS 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.3The 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.1DIV shall be capable of importing selected ITS Operational data from the ITS Operational Repositories.
7.1.3.1.4DIV 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.9DIV 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.
  
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

Last updated on 05-25-2005 using Ronald C. Ice and Associates Web Spinner Technology.