DM01: ITS Data Warehouse
This service package provides access to transportation data to support transportation planning, condition and performance monitoring, safety analysis, and research. Configurations range from focused repositories that house data collected and owned by a single agency, district, private sector provider, or research institution to broad repositories that contain multimodal, multidimensional data from varied data sources covering a broader region. Both central repositories and physical distributed ITS data repositories are supported. Requests for data that are satisfied by access to a single repository in the ITS Data Warehouse service package may be parsed by the local repository and dynamically translated to requests to other repositories that relay the data necessary to satisfy the request. The repositories could include a data registry capability that allows registration of data identifiers or data definitions for interoperable use throughout a region.
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
- Implementations
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
| Source | Destination | Role/Relationship |
|---|---|---|
| Alternate Mode Transportation Center Maintainer | Alternate Mode Transportation Center | Maintains |
| Alternate Mode Transportation Center Manager | Alternate Mode Transportation Center | Manages |
| Alternate Mode Transportation Center Owner | Alternate Mode Transportation Center Maintainer | System Maintenance Agreement |
| Alternate Mode Transportation Center Owner | Alternate Mode Transportation Center Manager | Operations Agreement |
| Alternate Mode Transportation Center Owner | Archived Data Administrator | Application Usage Agreement |
| Alternate Mode Transportation Center Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Alternate Mode Transportation Center Owner | Archived Data System Owner | Information Provision Agreement |
| Alternate Mode Transportation Center Owner | Archived Data System User | Service Usage Agreement |
| Alternate Mode Transportation Center Supplier | Alternate Mode Transportation Center Owner | Warranty |
| Archived Data Administrator | Archived Data System | Operates |
| Archived Data System Maintainer | Archived Data System | Maintains |
| Archived Data System Manager | Archived Data Administrator | System Usage Agreement |
| Archived Data System Manager | Archived Data System | Manages |
| Archived Data System Owner | Alternate Mode Transportation Center Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Alternate Mode Transportation Center Owner | Information Provision Agreement |
| Archived Data System Owner | Alternate Mode Transportation Center User | Service Usage Agreement |
| Archived Data System Owner | Archived Data System Maintainer | System Maintenance Agreement |
| Archived Data System Owner | Archived Data System Manager | Operations Agreement |
| Archived Data System Owner | Archived Data User System Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Archived Data User System Owner | Information Provision Agreement |
| Archived Data System Owner | Archived Data User System User | Service Usage Agreement |
| Archived Data System Owner | Asset Management System Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Asset Management System Owner | Information Provision Agreement |
| Archived Data System Owner | Asset Management System User | Service Usage Agreement |
| Archived Data System Owner | Border Inspection Administration Center Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Border Inspection Administration Center Owner | Information Provision Agreement |
| Archived Data System Owner | Border Inspection Administration Center User | Service Usage Agreement |
| Archived Data System Owner | Commercial Vehicle Administration Center Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Commercial Vehicle Administration Center Owner | Information Provision Agreement |
| Archived Data System Owner | Commercial Vehicle Administration Center User | Service Usage Agreement |
| Archived Data System Owner | Emergency Management Center Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Emergency Management Center Owner | Information Provision Agreement |
| Archived Data System Owner | Emergency Management Center User | Service Usage Agreement |
| Archived Data System Owner | Emissions Management Center Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Emissions Management Center Owner | Information Provision Agreement |
| Archived Data System Owner | Emissions Management Center User | Service Usage Agreement |
| Archived Data System Owner | Intermodal Terminal Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Intermodal Terminal Owner | Information Provision Agreement |
| Archived Data System Owner | Intermodal Terminal User | Service Usage Agreement |
| Archived Data System Owner | ITS Roadway Equipment Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | ITS Roadway Equipment Owner | Information Provision Agreement |
| Archived Data System Owner | ITS Roadway Equipment User | Service Usage Agreement |
| Archived Data System Owner | Maint and Constr Management Center Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Maint and Constr Management Center Owner | Information Provision Agreement |
| Archived Data System Owner | Maint and Constr Management Center User | Service Usage Agreement |
| Archived Data System Owner | Other Archived Data Systems Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Other Archived Data Systems Owner | Information Exchange Agreement |
| Archived Data System Owner | Other Archived Data Systems User | Service Usage Agreement |
| Archived Data System Owner | Other Data Sources Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Other Data Sources Owner | Information Exchange Agreement |
| Archived Data System Owner | Other Data Sources User | Service Usage Agreement |
| Archived Data System Owner | Parking Management Center Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Parking Management Center Owner | Information Provision Agreement |
| Archived Data System Owner | Parking Management Center User | Service Usage Agreement |
| Archived Data System Owner | Payment Administration Center Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Payment Administration Center Owner | Information Provision Agreement |
| Archived Data System Owner | Payment Administration Center User | Service Usage Agreement |
| Archived Data System Owner | Surface Transportation Weather Service Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Surface Transportation Weather Service Owner | Information Provision Agreement |
| Archived Data System Owner | Surface Transportation Weather Service User | Service Usage Agreement |
| Archived Data System Owner | Traffic Management Center Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Traffic Management Center Owner | Information Provision Agreement |
| Archived Data System Owner | Traffic Management Center User | Service Usage Agreement |
| Archived Data System Owner | Transit Management Center Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Transit Management Center Owner | Information Provision Agreement |
| Archived Data System Owner | Transit Management Center User | Service Usage Agreement |
| Archived Data System Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Transportation Information Center Owner | Information Provision Agreement |
| Archived Data System Owner | Transportation Information Center User | Service Usage Agreement |
| Archived Data System Owner | Weather Service System Maintainer | Maintenance Data Exchange Agreement |
| Archived Data System Owner | Weather Service System Owner | Information Provision Agreement |
| Archived Data System Owner | Weather Service System User | Service Usage Agreement |
| Archived Data System Supplier | Archived Data System Owner | Warranty |
| Archived Data User System Maintainer | Archived Data User System | Maintains |
| Archived Data User System Manager | Archived Data User System | Manages |
| Archived Data User System Owner | Archived Data Administrator | Application Usage Agreement |
| Archived Data User System Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Archived Data User System Owner | Archived Data System Owner | Information Provision Agreement |
| Archived Data User System Owner | Archived Data System User | Service Usage Agreement |
| Archived Data User System Owner | Archived Data User System Maintainer | System Maintenance Agreement |
| Archived Data User System Owner | Archived Data User System Manager | Operations Agreement |
| Archived Data User System Supplier | Archived Data User System Owner | Warranty |
| Asset Management System Maintainer | Asset Management System | Maintains |
| Asset Management System Manager | Asset Management System | Manages |
| Asset Management System Owner | Archived Data Administrator | Application Usage Agreement |
| Asset Management System Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Asset Management System Owner | Archived Data System Owner | Information Provision Agreement |
| Asset Management System Owner | Archived Data System User | Service Usage Agreement |
| Asset Management System Owner | Asset Management System Maintainer | System Maintenance Agreement |
| Asset Management System Owner | Asset Management System Manager | Operations Agreement |
| Asset Management System Supplier | Asset Management System Owner | Warranty |
| Border Inspection Administration Center Maintainer | Border Inspection Administration Center | Maintains |
| Border Inspection Administration Center Manager | Border Inspection Administration Center | Manages |
| Border Inspection Administration Center Owner | Archived Data Administrator | Application Usage Agreement |
| Border Inspection Administration Center Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Border Inspection Administration Center Owner | Archived Data System Owner | Information Provision Agreement |
| Border Inspection Administration Center Owner | Archived Data System User | Service Usage Agreement |
| Border Inspection Administration Center Owner | Border Inspection Administration Center Maintainer | System Maintenance Agreement |
| Border Inspection Administration Center Owner | Border Inspection Administration Center Manager | Operations Agreement |
| Border Inspection Administration Center Supplier | Border Inspection Administration Center Owner | Warranty |
| Commercial Vehicle Administration Center Maintainer | Commercial Vehicle Administration Center | Maintains |
| Commercial Vehicle Administration Center Manager | Commercial Vehicle Administration Center | Manages |
| Commercial Vehicle Administration Center Owner | Archived Data Administrator | Application Usage Agreement |
| Commercial Vehicle Administration Center Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Commercial Vehicle Administration Center Owner | Archived Data System Owner | Information Provision Agreement |
| Commercial Vehicle Administration Center Owner | Archived Data System User | Service Usage Agreement |
| Commercial Vehicle Administration Center Owner | Commercial Vehicle Administration Center Maintainer | System Maintenance Agreement |
| Commercial Vehicle Administration Center Owner | Commercial Vehicle Administration Center Manager | Operations Agreement |
| Commercial Vehicle Administration Center Supplier | Commercial Vehicle Administration Center Owner | Warranty |
| Connected Vehicle Roadside Equipment Maintainer | Connected Vehicle Roadside Equipment | Maintains |
| Connected Vehicle Roadside Equipment Manager | Connected Vehicle Roadside Equipment | Manages |
| Connected Vehicle Roadside Equipment Owner | Archived Data Administrator | Application Usage Agreement |
| Connected Vehicle Roadside Equipment Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Connected Vehicle Roadside Equipment Owner | Archived Data System Owner | Information Exchange and Action Agreement |
| Connected Vehicle Roadside Equipment Owner | Archived Data System User | Service Usage Agreement |
| Connected Vehicle Roadside Equipment Owner | Connected Vehicle Roadside Equipment Maintainer | System Maintenance Agreement |
| Connected Vehicle Roadside Equipment Owner | Connected Vehicle Roadside Equipment Manager | Operations Agreement |
| Connected Vehicle Roadside Equipment Supplier | Connected Vehicle Roadside Equipment Owner | Warranty |
| Emergency Management Center Maintainer | Emergency Management Center | Maintains |
| Emergency Management Center Manager | Emergency Management Center | Manages |
| Emergency Management Center Owner | Archived Data Administrator | Application Usage Agreement |
| Emergency Management Center Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Emergency Management Center Owner | Archived Data System Owner | Information Provision Agreement |
| Emergency Management Center Owner | Archived Data System User | Service Usage Agreement |
| Emergency Management Center Owner | Emergency Management Center Maintainer | System Maintenance Agreement |
| Emergency Management Center Owner | Emergency Management Center Manager | Operations Agreement |
| Emergency Management Center Supplier | Emergency Management Center Owner | Warranty |
| Emissions Management Center Maintainer | Emissions Management Center | Maintains |
| Emissions Management Center Manager | Emissions Management Center | Manages |
| Emissions Management Center Owner | Archived Data Administrator | Application Usage Agreement |
| Emissions Management Center Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Emissions Management Center Owner | Archived Data System Owner | Information Provision Agreement |
| Emissions Management Center Owner | Archived Data System User | Service Usage Agreement |
| Emissions Management Center Owner | Emissions Management Center Maintainer | System Maintenance Agreement |
| Emissions Management Center Owner | Emissions Management Center Manager | Operations Agreement |
| Emissions Management Center Supplier | Emissions Management Center Owner | Warranty |
| Intermodal Terminal Maintainer | Intermodal Terminal | Maintains |
| Intermodal Terminal Manager | Intermodal Terminal | Manages |
| Intermodal Terminal Owner | Archived Data Administrator | Application Usage Agreement |
| Intermodal Terminal Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Intermodal Terminal Owner | Archived Data System Owner | Information Exchange and Action Agreement |
| Intermodal Terminal Owner | Archived Data System User | Service Usage Agreement |
| Intermodal Terminal Owner | Intermodal Terminal Maintainer | System Maintenance Agreement |
| Intermodal Terminal Owner | Intermodal Terminal Manager | Operations Agreement |
| Intermodal Terminal Supplier | Intermodal Terminal Owner | Warranty |
| ITS Roadway Equipment Maintainer | ITS Roadway Equipment | Maintains |
| ITS Roadway Equipment Manager | ITS Roadway Equipment | Manages |
| ITS Roadway Equipment Owner | Archived Data Administrator | Application Usage Agreement |
| ITS Roadway Equipment Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| ITS Roadway Equipment Owner | Archived Data System Owner | Information Exchange and Action Agreement |
| ITS Roadway Equipment Owner | Archived Data System User | Service Usage Agreement |
| ITS Roadway Equipment Owner | ITS Roadway Equipment Maintainer | System Maintenance Agreement |
| ITS Roadway Equipment Owner | ITS Roadway Equipment Manager | Operations Agreement |
| ITS Roadway Equipment Supplier | ITS Roadway Equipment Owner | Warranty |
| Maint and Constr Management Center Maintainer | Maint and Constr Management Center | Maintains |
| Maint and Constr Management Center Manager | Maint and Constr Management Center | Manages |
| Maint and Constr Management Center Owner | Archived Data Administrator | Application Usage Agreement |
| Maint and Constr Management Center Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Maint and Constr Management Center Owner | Archived Data System Owner | Information Provision Agreement |
| Maint and Constr Management Center Owner | Archived Data System User | Service Usage Agreement |
| Maint and Constr Management Center Owner | Maint and Constr Management Center Maintainer | System Maintenance Agreement |
| Maint and Constr Management Center Owner | Maint and Constr Management Center Manager | Operations Agreement |
| Maint and Constr Management Center Supplier | Maint and Constr Management Center Owner | Warranty |
| Other Archived Data Systems Maintainer | Other Archived Data Systems | Maintains |
| Other Archived Data Systems Manager | Other Archived Data Systems | Manages |
| Other Archived Data Systems Owner | Archived Data Administrator | Application Usage Agreement |
| Other Archived Data Systems Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Other Archived Data Systems Owner | Archived Data System Owner | Information Exchange Agreement |
| Other Archived Data Systems Owner | Archived Data System User | Service Usage Agreement |
| Other Archived Data Systems Owner | Other Archived Data Systems Maintainer | System Maintenance Agreement |
| Other Archived Data Systems Owner | Other Archived Data Systems Manager | Operations Agreement |
| Other Archived Data Systems Supplier | Other Archived Data Systems Owner | Warranty |
| Other Data Sources Maintainer | Other Data Sources | Maintains |
| Other Data Sources Manager | Other Data Sources | Manages |
| Other Data Sources Owner | Archived Data Administrator | Application Usage Agreement |
| Other Data Sources Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Other Data Sources Owner | Archived Data System Owner | Information Exchange Agreement |
| Other Data Sources Owner | Archived Data System User | Service Usage Agreement |
| Other Data Sources Owner | Other Data Sources Maintainer | System Maintenance Agreement |
| Other Data Sources Owner | Other Data Sources Manager | Operations Agreement |
| Other Data Sources Supplier | Other Data Sources Owner | Warranty |
| Parking Management Center Maintainer | Parking Management Center | Maintains |
| Parking Management Center Manager | Parking Management Center | Manages |
| Parking Management Center Owner | Archived Data Administrator | Application Usage Agreement |
| Parking Management Center Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Parking Management Center Owner | Archived Data System Owner | Information Provision Agreement |
| Parking Management Center Owner | Archived Data System User | Service Usage Agreement |
| Parking Management Center Owner | Parking Management Center Maintainer | System Maintenance Agreement |
| Parking Management Center Owner | Parking Management Center Manager | Operations Agreement |
| Parking Management Center Supplier | Parking Management Center Owner | Warranty |
| Payment Administration Center Maintainer | Payment Administration Center | Maintains |
| Payment Administration Center Manager | Payment Administration Center | Manages |
| Payment Administration Center Owner | Archived Data Administrator | Application Usage Agreement |
| Payment Administration Center Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Payment Administration Center Owner | Archived Data System Owner | Information Provision Agreement |
| Payment Administration Center Owner | Archived Data System User | Service Usage Agreement |
| Payment Administration Center Owner | Payment Administration Center Maintainer | System Maintenance Agreement |
| Payment Administration Center Owner | Payment Administration Center Manager | Operations Agreement |
| Payment Administration Center Supplier | Payment Administration Center Owner | Warranty |
| Surface Transportation Weather Service Maintainer | Surface Transportation Weather Service | Maintains |
| Surface Transportation Weather Service Manager | Surface Transportation Weather Service | Manages |
| Surface Transportation Weather Service Owner | Archived Data Administrator | Application Usage Agreement |
| Surface Transportation Weather Service Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Surface Transportation Weather Service Owner | Archived Data System Owner | Information Provision Agreement |
| Surface Transportation Weather Service Owner | Archived Data System User | Service Usage Agreement |
| Surface Transportation Weather Service Owner | Surface Transportation Weather Service Maintainer | System Maintenance Agreement |
| Surface Transportation Weather Service Owner | Surface Transportation Weather Service Manager | Operations Agreement |
| Surface Transportation Weather Service Supplier | Surface Transportation Weather Service Owner | Warranty |
| Traffic Management Center Maintainer | Traffic Management Center | Maintains |
| Traffic Management Center Manager | Traffic Management Center | Manages |
| Traffic Management Center Owner | Archived Data Administrator | Application Usage Agreement |
| Traffic Management Center Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Traffic Management Center Owner | Archived Data System Owner | Information Provision Agreement |
| Traffic Management Center Owner | Archived Data System User | Service Usage Agreement |
| Traffic Management Center Owner | Traffic Management Center Maintainer | System Maintenance Agreement |
| Traffic Management Center Owner | Traffic Management Center Manager | Operations Agreement |
| Traffic Management Center Supplier | Traffic Management Center Owner | Warranty |
| Transit Management Center Maintainer | Transit Management Center | Maintains |
| Transit Management Center Manager | Transit Management Center | Manages |
| Transit Management Center Owner | Archived Data Administrator | Application Usage Agreement |
| Transit Management Center Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Transit Management Center Owner | Archived Data System Owner | Information Provision Agreement |
| Transit Management Center Owner | Archived Data System User | Service Usage Agreement |
| Transit Management Center Owner | Transit Management Center Maintainer | System Maintenance Agreement |
| Transit Management Center Owner | Transit Management Center Manager | Operations Agreement |
| Transit Management Center Supplier | Transit Management Center Owner | Warranty |
| Transportation Information Center Maintainer | Transportation Information Center | Maintains |
| Transportation Information Center Manager | Transportation Information Center | Manages |
| Transportation Information Center Owner | Archived Data Administrator | Application Usage Agreement |
| Transportation Information Center Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Transportation Information Center Owner | Archived Data System Owner | Information Provision Agreement |
| Transportation Information Center Owner | Archived Data System User | Service Usage Agreement |
| Transportation Information Center Owner | Transportation Information Center Maintainer | System Maintenance Agreement |
| Transportation Information Center Owner | Transportation Information Center Manager | Operations Agreement |
| Transportation Information Center Supplier | Transportation Information Center Owner | Warranty |
| Weather Service System Maintainer | Weather Service System | Maintains |
| Weather Service System Manager | Weather Service System | Manages |
| Weather Service System Owner | Archived Data Administrator | Application Usage Agreement |
| Weather Service System Owner | Archived Data System Maintainer | Maintenance Data Exchange Agreement |
| Weather Service System Owner | Archived Data System Owner | Information Provision Agreement |
| Weather Service System Owner | Archived Data System User | Service Usage Agreement |
| Weather Service System Owner | Weather Service System Maintainer | System Maintenance Agreement |
| Weather Service System Owner | Weather Service System Manager | Operations Agreement |
| Weather Service System Supplier | Weather Service System Owner | Warranty |
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
| Physical Object | Class | Description |
|---|---|---|
| Alternate Mode Transportation Center | Center | The 'Alternate Mode Transportation Center' provides the interface through which non-ITS transportation systems (e.g., airlines, ferry services, passenger-carrying heavy rail) can exchange data with ITS. This two-way interface enables coordination for efficient movement of people across multiple transportation modes. It also enables the traveler to efficiently plan itineraries which include segments using other modes. |
| Archived Data Administrator | Support | 'Archived Data Administrator' represents the human operator who provides overall data management, administration, and monitoring duties for the ITS data archive. Unlike the manager of the operational databases, the archive data administrator's role is focused on the archive and covers areas such as establishing user authentication controls, monitoring data quality, and initiating data import requests. |
| Archived Data System | Support | 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. |
| Archived Data User System | Center | 'Archived Data User System' represents the systems users employ to access archived data. The general interface provided allows a broad range of users (e.g. planners, researchers, analysts, operators) and their systems (e.g. databases, models, analytical tools, user interface devices) to acquire data and analyses results from the archive. |
| Asset Management System | Center | 'Asset Management System' represents the systems that support decision-making for maintenance, upgrade, and operation of physical transportation assets. Asset management integrates and includes the pavement management systems, bridge management systems, and other systems that inventory and manage the highway infrastructure and other transportation-related assets. The types of assets that are inventoried and managed will vary, and may include the maintenance and construction vehicles and equipment as well as "soft" assets such as human resources and software. Asset management systems monitor the condition, performance, and availability of the infrastructure and evaluate and prioritize alternative reconstruction, rehabilitation, and maintenance strategies. |
| Border Inspection Administration Center | Center | 'Border Inspection Administration Center' represents back-office systems and databases run by domestic and foreign governmental agencies responsible for the regulation of trade, and the enforcement of customs and immigration laws. These agencies include U.S. Department of Homeland Security (DHS) and its counterparts in Canada and Mexico. DHS includes components like Customs and Border Protection (CBP), Immigration and Customs Enforcement (ICE), and Transportation Security Administration (TSA). Other agencies include secondary trade agencies (e.g., U.S. Food and Drug Administration, U.S. Department of Agriculture, other USDOT departments, etc.), and agencies from other trading nations. The systems they manage coordinate activities related to the border crossings. These systems support import/export cargo processing and enforcement operations at the border, including programs such as FAST, Automated Commercial Environment (ACE), Nexus (Canada), SENTRI (Mexico), and US-VISIT. |
| Commercial Vehicle Administration Center | Center | The 'Commercial Vehicle Administration Center' performs administrative functions supporting credentials, tax, and safety regulations associated with commercial vehicles. It issues credentials, collects fees and taxes, and supports enforcement of credential requirements. It communicates with motor carriers to process credentials applications and collect fuel taxes, weight/distance taxes, and other taxes and fees associated with commercial vehicle operations. It also receives applications for, and issues special Oversize/Overweight and HAZMAT permits in coordination with cognizant authorities. It coordinates with other Commercial Vehicle Administration Centers (in other states/regions) to support nationwide access to credentials and safety information for administration and enforcement functions. It communicates with field equipment to enable credential checking and safety information collection at the roadside. It makes safety information available to qualified stakeholders to identify carriers and drivers that operate unsafely. |
| Connected Vehicle Roadside Equipment | Field | 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers. |
| Emergency Management Center | Center | The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers. It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system. It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted. It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency. |
| Emissions Management Center | Center | The 'Emissions Management Center' provides the capabilities for air quality managers to monitor and manage air quality. These capabilities include collecting emissions data from distributed emissions sensors (included in ITS Roadway Equipment) and directly from connected vehicles. The sensors monitor general air quality and also monitor the emissions of individual vehicles on the roadway. The measures are collected, processed, and used to support environmental monitoring applications. |
| Intermodal Terminal | Field | The 'Intermodal Terminal' represents the terminal areas corresponding to modal change points. This includes interfaces between roadway freight transportation and air, rail, and/or water shipping modes. The basic unit of cargo handled by the Intermodal Terminal physical object is the container; less-than-container load handling is typically handled at a different facility (i.e., Freight Consolidation Station). The Intermodal Terminal can include electronic gate control for entrance and exit from the facility, automated guidance of vehicles within the facility, alerting appropriate parties of container arrivals and departures, and inventory and location of temporarily stored containers. |
| ITS Roadway Equipment | Field | 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included. |
| Maint and Constr Management Center | Center | The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities. |
| Other Archived Data Systems | Support | 'Other Archived Data Systems' represents distributed archived data systems whose data can be accessed and shared with a local archive. The interface with the Archived Data System allows data from multiple archives to be accessed on demand or imported and consolidated into a single repository. |
| Other Data Sources | Support | 'Other Data Sources' represents the myriad systems and databases containing data not generated by ITS that can provide predefined data sets to the ITS archive. It can provide economic, cost, demographic, land use, law enforcement, and other data that is not collected by ITS systems and would otherwise be unavailable within an ITS data archive. |
| Parking Management Center | Center | The 'Parking Management Center' manages one or more parking lots by providing configuration and control of field infrastructure, user account management and interfaces with financial systems to manage payment. This p-object takes the back office portion of the Parking Management System's functionality as it was defined in ARC-IT 8.3 and prior. |
| Payment Administration Center | Center | The 'Payment Administration Center' provides general payment administration capabilities and supports the electronic transfer of funds from the customer to the transportation system operator or other service provider. Charges can be recorded for tolls, vehicle-mileage charging, congestion charging, or other goods and services. It supports traveler enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the financial infrastructure supporting electronic payment transactions. The system may establish and administer escrow accounts depending on the clearinghouse scheme and the type of payments involved. It may post a transaction to the customer account, generate a bill (for post-payment accounts), debit an escrow account, or interface to a financial infrastructure to debit a customer designated account. It supports communications with the ITS Roadway Payment Equipment to support fee collection operations. As an alternative, a wide-area wireless interface can be used to communicate directly with vehicle equipment. It also sets and administers the pricing structures and may implement road pricing policies in coordination with the Traffic Management Center. |
| Surface Transportation Weather Service | Center | The 'Surface Transportation Weather Service' represents the providers of value-added sector-specific meteorological services. These providers utilize National Weather Service data and predictions, road condition information and local environmental data provided by traffic management or maintenance organizations, and their own models to provide surface transportation related weather observations and forecasts including pavement temperature and conditions. |
| Traffic Management Center | Center | The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters. |
| Transit Management Center | Center | 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. |
| Transportation Information Center | Center | 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. |
| Weather Service System | Center | The 'Weather Service System' provides weather, hydrologic, and climate information and warnings of hazardous weather including thunderstorms, flooding, hurricanes, tornadoes, winter weather, tsunamis, and climate events. It provides atmospheric weather observations and forecasts that are collected and derived by the National Weather Service, private sector providers, and various research organizations. The interface provides formatted weather data products suitable for on-line processing and integration with other ITS data products as well as Doppler radar images, satellite images, severe storm warnings, and other products that are formatted for presentation to various ITS users. |
Includes Functional Objects:
| Functional Object | Description | Physical Object |
|---|---|---|
| Archive Data Repository | 'Archive Data Repository' collects data and data catalogs from one or more data sources and stores the data in a focused repository that is suited to a particular set of ITS data users. It includes capabilities for performing quality checks on the incoming data, error notification, and archive to archive coordination. It includes the capability to define a data registry that allows registration of data identifiers or data definitions for interoperable use throughout a region. It supports a broad range of implementations, ranging from simple data marts that collect a focused set of data and serve a particular user community to large-scale data warehouses that collect, integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region. Repositories may be established to support operations planning, performance monitoring and management, and policy and investment decisions. | Archived Data System |
| Archive Situation Data Archival | 'Archive Situation Data Archival' collects and archives traffic, roadway, and environmental information for use in off-line planning, research, and analysis. It controls and collects information directly from equipment at the roadside, reflecting the deployment of traffic detectors that are used primarily for traffic monitoring and planning purposes, rather than for traffic management. It also collects situation data from connected vehicles. The data collected, quality checks performed, and aggregation strategies are defined to support transportation system performance monitoring and management. | Archived Data System |
| BIAC Data Collection | 'BIAC Data Collection' collects and stores border inspection information that is collected in the course of Border Inspection Administration Center operations. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | Border Inspection Administration Center |
| CVAC Data Collection | 'CVAC Data Collection' collects and stores commercial vehicle information that is collected in the course of Commercial Vehicle Administration Center operations. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | Commercial Vehicle Administration Center |
| Emergency Data Collection | 'Emergency Data Collection' collects and stores emergency information that is collected in the course of operations by the Emergency Management Center. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | Emergency Management Center |
| Emissions Data Collection | 'Emissions Data Collection' collects and stores air quality and emissions management information that is collected in the course of Emissions Management Center operations. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | Emissions Management Center |
| MCM Data Collection | 'MCM Data Collection' collects and stores maintenance and construction information that is collected in the course of operations by the Maintenance and Construction Management Center. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | Maint and Constr Management Center |
| PAC Data Collection | 'PAC Data Collection' collects and stores toll, road use, parking, and other payment information that is collected in the course of operations performed by the Payment Administration Center. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | Payment Administration Center |
| Parking Data Collection | 'Parking Data Collection' collects and stores parking information that is collected in the course of parking system operations. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | Parking Management Center |
| Roadway Data Collection | 'Roadway Data Collection' collects traffic, road, and environmental conditions information for use in transportation planning, research, and other off-line applications where data quality and completeness take precedence over real-time performance. It includes the sensors, supporting roadside infrastructure, and communications equipment that collects and transfers information to a center for archival. | ITS Roadway Equipment |
| RSE Situation Monitoring | 'RSE Situation Monitoring' is a general functional object that supports collection of traffic, environmental, and emissions data from passing vehicles. The data is collected, filtered, and forwarded based on parameters provided by the back office. Parameters are provided to passing vehicles that are equipped to collect and send situation data to the infrastructure in snapshots. In addition, this object collects current status information from local field devices including intersection status, sensor data, and signage data, providing complete, configurable monitoring of the situation for the local transportation system in the vicinity of the RSE. | Connected Vehicle Roadside Equipment |
| Terminal Data Collection | 'Terminal Data Collection' collects and stores information that is collected in the course of intermodal terminal operations. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | Intermodal Terminal |
| TIC Operations Data Collection | 'TIC Operations Data Collection' collects and stores information that is collected about the transportation information service including data on the number of clients serviced and the services that were provided. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | Transportation Information Center |
| TMC Data Collection | 'TMC Data Collection' collects and stores information that is created in the course of traffic operations performed by the Traffic Management Center. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | Traffic Management Center |
| Transit Center Data Collection | 'Transit Center Data Collection' collects and stores transit information that is collected in the course of transit operations performed by the Transit Management Center. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. | Transit Management Center |
Includes Information Flows:
| Information Flow | Description |
|---|---|
| archive coordination | Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and satisfy user data requests. |
| archive management data | Presentation of information to the administrator to support the management of an ITS archive including database reports on the condition and quality of the archived data, status of the import and collection process, reports that monitor archive usage, and any special requests that require direct action by the administrator (e.g., requests for access to new data sources). |
| archive management requests | User input from the administrator including commands, requests, and queries that support data collection, administration, and management of an ITS data archive. |
| archive status | Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified. |
| archived data product requests | A user-specified request for archived data products (i.e., data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any. |
| archived data products | Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information. |
| asset archive data | Information describing transportation assets including pavements, bridges, and all other infrastructure included in the transportation network. In addition, information can cover support assets (support equipment and systems, software, etc.). Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
| border information archive data | Border inspection activities data. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
| commercial vehicle archive data | Information describing commercial vehicle travel and commodity flow characteristics. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
| data collection and monitoring control | Information used to configure and control data collection and monitoring systems. |
| emergency archive data | Logged emergency information including information that characterizes identified incidents (routine highway incidents through disasters), corresponding incident response information, evacuation information, surveillance data, threat data, and resource information. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
| emissions archive data | Air quality and vehicle emissions information that is collected by sensors or derived from models. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
| intermodal freight archive data | Information describing demand at intermodal freight terminals including loading/unloading activities of trailers and containers. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
| local situation data | This general flow represents the traffic, environmental, and emissions situation data that is collected from connected vehicles by an RSE, aggregated, filtered, and provided to a back-office center. It also includes data collected from ITS roadway equipment that provides current intersection and road network status for the area proximate to the RSE. |
| maint and constr archive data | Information describing road construction and maintenance activities identifying the type of activity, the work performed, and work zone information including work zone configuration and safety (e.g., a record of intrusions and vehicle speeds) information. For construction activities, this information also includes a description of the completed infrastructure, including as-built plans as applicable. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
| multimodal archive data | Operational information from alternate passenger transportation modes including air, rail transit, taxis, and ferries. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
| other data source archive data | Data extracted from other data sources. A wide range of ITS and non-ITS data and associated meta data may be provided. |
| parking archive data | Data used to analyze and monitor trends in parking demand, pricing, and operational actions. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
| payment archive data | Data indicating roadway payments including toll facility usage and pricing schedules. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
| roadside archive data | A broad set of data derived from roadside sensors that includes current traffic conditions, environmental conditions, and any other data that can be directly collected by roadside sensors. This data also indicates the status of the sensors and reports of any identified sensor faults. |
| traffic archive data | Information describing the use and vehicle composition on transportation facilities and the traffic control strategies employed. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
| transit archive data | 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. |
| transportation weather information | Current and forecast road conditions and weather information (e.g., surface condition, flooding, wind advisories, visibility, etc.) associated with the transportation network. This information is of a resolution, timeliness, and accuracy to be useful in transportation decision making. |
| traveler archive data | Data associated with traveler information services including service requests, facility usage, rideshare, routing, and traveler payment transaction data. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
| weather archive data | Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.) as well as qualified environmental sensor data. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
Goals and Objectives
Associated Planning Factors and Goals
| Planning Factor | Goal |
|---|---|
| F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; | Enhance integration and connectivity |
Associated Objective Categories 
| Objective Category |
|---|
| Integration: Transportation Data Collection |
Associated Objectives and Performance Measures
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.
Needs and Requirements
| Need | Functional Object | Requirement | ||
|---|---|---|---|---|
| 01 | System operators need to be able to store data for long term access by themselves and other operators. | Archive Data Repository | 01 | The center shall collect data from centers. |
| 03 | The center shall store collected data in an information repository. | |||
| 06 | The center shall include capabilities for archive to archive coordination. | |||
| 08 | The center shall collect data from data distribution systems and other data sources. | |||
| Archive Situation Data Archival | 01 | The center shall collect data from roadside devices. | ||
| 06 | The center shall provide the capability to execute methods on the incoming field data such as aggregation and statistical measures before the data is stored in the archive. | |||
| BIAC Data Collection | 01 | The center shall receive operational data from the border inspection systems as well as administrative and registration data. | ||
| 02 | The border inspection administration 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. 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. | |||
| 03 | The center shall receive and respond to requests from ITS Archives for either a catalog of the border operations data or for the data itself. | |||
| 04 | The border inspection administration center shall produce sample products of the data available. | |||
| CVAC Data Collection | 01 | The center shall receive operational data from the roadside check systems as well as administration and credentials data. | ||
| 02 | The commercial vehicle administration 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. | |||
| 03 | The center shall receive and respond to requests from ITS Archives for either a catalog of the commercial vehicle operations data or for the data itself. | |||
| 04 | The commercial vehicle administration center shall produce sample products of the data available. | |||
| Emergency Data Collection | 01 | The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor and surveillance data, threat data, and incident data. | ||
| 02 | The emergency management 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. | |||
| 03 | The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management data or for the data itself. | |||
| 04 | The emergency management center shall produce sample products of the data available. | |||
| Emissions Data Collection | 01 | The center shall collect air quality and emissions management data from various sources, including emissions sensors distributed along the roadside and wide-area sensors detecting pollution over a larger geographical area. | ||
| 02 | The emissions management 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. | |||
| 03 | The center shall receive and respond to requests from ITS Archives for either a catalog of the emissions management data or for the data itself. | |||
| 04 | The emissions management center shall produce sample products of the data available. | |||
| MCM Data Collection | 01 | The center shall collect maintenance and construction data (such as field equipment status, infrastructure status, maintenance and construction activity data) gathered from roadway, traffic, and other maintenance and construction sources. | ||
| 02 | The maintenance and construction management 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. | |||
| 03 | The center shall receive and respond to requests from ITS Archives for either a catalog of the maintenance and construction data or for the data itself. | |||
| 04 | The maintenance and construction management center shall produce sample products of the data available. | |||
| PAC Data Collection | 01 | The center shall collect toll operational data and roadway pricing data. | ||
| 02 | The payment administration 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. | |||
| 03 | The center shall receive and respond to requests from ITS Archives for either a catalog of the toll data or for the data itself. | |||
| 04 | The payment administration center shall produce sample products of the data available. | |||
| Parking Data Collection | 01 | The parking element shall collect parking management data including lot usage and charging information. | ||
| 02 | The parking element 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. | |||
| 03 | The parking element shall receive and respond to requests from ITS Archives for either a catalog of the parking management data or for the data itself. | |||
| 04 | The parking element shall produce sample products of the data available. | |||
| Roadway Data Collection | 01 | The field element shall collect traffic, road, and environmental conditions information. | ||
| 02 | The field element shall include the sensors and supporting roadside devices that sense, collect, and send traffic, road, and environmental conditions information to a center for archival. | |||
| 03 | The field element shall collect sensor status and sensor faults from roadside equipment and send it along with the recorded data to a center for archival. | |||
| RSE Situation Monitoring | 01 | The field element shall collect traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicles. | ||
| 02 | The field element shall provide vehicle situation data to a center for archival. | |||
| 05 | The field element shall provide collected vehicle situation and local sensor data to data distribution centers. | |||
| Terminal Data Collection | 01 | The intermodal terminal shall collect intermodal shipping data including shipping schedules, container statistics, chassis usage, traffic into and out of the facility. | ||
| 02 | The intermodal terminal 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. | |||
| 03 | The intermodal terminal shall receive and respond to requests from ITS Archives for either a catalog of the parking management data or for the data itself. | |||
| 04 | The intermodal terminal shall produce sample products of the data available. | |||
| TIC Operations Data Collection | 01 | The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations. | ||
| 02 | The center shall collect traveler requests, confirmations, and payment transaction data for traveler services provided. | |||
| 03 | The transportation information 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. | |||
| 04 | The center shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or for the data itself. | |||
| 05 | The transportation information center shall produce sample products of the data available. | |||
| TMC Data Collection | 01 | The center shall collect traffic management data such as operational data, event logs, etc. | ||
| 02 | The traffic management 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. | |||
| 03 | The traffic management center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself. | |||
| 04 | The traffic management center shall produce sample products of the data available. | |||
| Transit Center Data Collection | 01 | The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit operations, transit vehicle maintenance data, etc. | ||
| 02 | The transit management 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. | |||
| 03 | The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data itself. | |||
| 04 | The transit management center shall produce sample products of the data available. | |||
| 02 | System operators need to be able to query for and receive archive data products containing freeway data, tolling data, arterial data, parking data, transit and ridesharing data, incident management data, safety-related data, CVO data, environmental and weather data, vehicle and passenger data and intermodal operations data. | Archive Data Repository | 11 | The center shall respond to requests for archive data from archive data users (centers, field devices). |
| 12 | The center shall provide a mechanism for archive data users to request archive data by meta-data range. | |||
| Archive Situation Data Archival | 07 | The center shall respond to requests from the administrator interface function to select and manage data stored in the archive. | ||
| 03 | System operators need to be able to manage data processing with regard to data archive functions, including data aggregation, data tagging (processed, edited, raw, transformed, etc.), data storage timing and longevity, data quality analysis, data formatting and metadata assignments. | Archive Data Repository | 02 | The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the collection of archived data and may include descriptions of the schema or structure of the data, a description of the contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail). |
| 04 | The center shall perform quality checks on collected data. | |||
| 05 | The center shall notify the system operator of errors related to data collection, analysis and archival. | |||
| 07 | The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive. | |||
| 09 | The center shall respond to requests from the administrator interface function to manage center-sourced data collection. | |||
| 10 | The center shall respond to requests from the administrator interface function to manage the archive data. | |||
| 13 | The center shall associate meta-data with archived data, including catalog data, statistical products determined from method execution and data longevity. | |||
| Archive Situation Data Archival | 02 | The center shall respond to requests from the administrator interface function to manage field-sourced data collection. | ||
| 03 | The center shall provide the capability to adjust the collection of field-sourced data based on the statistical measures. | |||
Security
In order to participate in this service package, each physical object should meet or exceed the following security levels.
In order to participate in this service package, each information flow triple should meet or exceed the following security levels.
| Information Flow Security | |||||
|---|---|---|---|---|---|
| Source | Destination | Information Flow | Confidentiality | Integrity | Availability |
| Basis | Basis | Basis | |||
| Alternate Mode Transportation Center | Archived Data System | multimodal archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Archived Data Administrator | Archived Data System | archive management requests | Moderate | Moderate | Moderate |
| Human readable information intended for the administrator only. No PII, mostly performance data, but observation provides information that should not be viewable outside the operating agency. Compromise allows a third party to potentially manipulate the archive. | System operating characteristics need to be provided in timely and accurate fashion, or inappropriate maintenance activity may take place, costing either system performance or money. | System operating characteristics need to be provided in timely and accurate fashion, or inappropriate maintenance activity may take place, costing either system performance or money. | |||
| Archived Data System | Alternate Mode Transportation Center | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Archived Data Administrator | archive management data | Moderate | Moderate | Moderate |
| Human readable information intended for the administrator only. No PII, mostly performance data, but observation provides information that should not be viewable outside the operating agency. Compromise allows a third party to potentially manipulate the archive. | System operating characteristics need to be provided in timely and accurate fashion, or inappropriate maintenance activity may take place, costing either system performance or money. | System operating characteristics need to be provided in timely and accurate fashion, or inappropriate maintenance activity may take place, costing either system performance or money. | |||
| Archived Data System | Archived Data User System | archived data products | High | High | Low |
| Data may include sensitive information which should not be casually viewable. As many requests could be quite large, the cost of compromise will be corresponding ly high. | Since the whole point of an archived data request is some sort of data analysis, the contents of that data must be intact or the effort is wasted. Such requests can be for very large data sets, the effective cost of which is high. | While the data sets are large, requests should be infrequent, and can be managed with interruptions in service. | |||
| Archived Data System | Asset Management System | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Border Inspection Administration Center | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Commercial Vehicle Administration Center | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Emergency Management Center | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Emissions Management Center | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Intermodal Terminal | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | ITS Roadway Equipment | data collection and monitoring control | Moderate | Moderate | Low |
| Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. | |||
| Archived Data System | Maint and Constr Management Center | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Other Archived Data Systems | archive coordination | Moderate | High | High |
| Archive coordination may involve substantial meta data that indicates how users are using archived data systems, and may include queries that betray intent. Observation of this information provides a third party with intelligence about system users that should not be observable. | Incorrect coordination could lead to substantial performance challenges for the archive systems, degrading overall performance which affects all users. Depending what the archive is used for, this might be reduced to MODERATE | Without this flow, archive usage that spans multiple systems will be impossible, making archive requests unusable. Depending on what the archive is used for, this might be reduced to MODERATE. | |||
| Archived Data System | Other Data Sources | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Parking Management Center | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Payment Administration Center | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Surface Transportation Weather Service | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Traffic Management Center | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Transit Management Center | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Transportation Information Center | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data System | Weather Service System | archive status | High | High | Moderate |
| Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | Tied to the 'archive requests' flow, and rated identically as a result. | |||
| Archived Data User System | Archived Data System | archived data product requests | Moderate | Moderate | Low |
| User login information must be kept confidential. Depending on the sensitivity of the archive data and resulting utiltity of access, this may be HIGH. | An incorrect data request will be incovenient, resulting in error or useless responses, but not catastrophic. | Not a real time service, so intermittent availability should suffice. | |||
| Asset Management System | Archived Data System | asset archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Border Inspection Administration Center | Archived Data System | border information archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Commercial Vehicle Administration Center | Archived Data System | commercial vehicle archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Connected Vehicle Roadside Equipment | Archived Data System | local situation data | Low | Moderate | Low |
| Limited impact if someone sees this data. Typically intended for eventual dissemination to the public. This assumes the RSE does not permit the inclusion of source-unique identifiers to the situation data. If such identifiers are included, may raise this to MODERATE. | Situation data will be used for a variety of decision-making purposes, so it should have some error checking, as any corruption could lead to sub-optimal choices. While any given instance of this flow is not critical, the aggregation of all will be significant. | Outage of this flow will deprive the terminus of the information included, but in the big picture this is a comparitively small amount of data with individually limited decision-driving content. If regional or local traffic management strategies depend on this flow, may raise to MODERATE. | |||
| Emergency Management Center | Archived Data System | emergency archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Emissions Management Center | Archived Data System | emissions archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Intermodal Terminal | Archived Data System | intermodal freight archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| ITS Roadway Equipment | Archived Data System | roadside archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Maint and Constr Management Center | Archived Data System | maint and constr archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Other Archived Data Systems | Archived Data System | archive coordination | Moderate | High | High |
| Archive coordination may involve substantial meta data that indicates how users are using archived data systems, and may include queries that betray intent. Observation of this information provides a third party with intelligence about system users that should not be observable. | Incorrect coordination could lead to substantial performance challenges for the archive systems, degrading overall performance which affects all users. Depending what the archive is used for, this might be reduced to MODERATE | Without this flow, archive usage that spans multiple systems will be impossible, making archive requests unusable. Depending on what the archive is used for, this might be reduced to MODERATE. | |||
| Other Data Sources | Archived Data System | other data source archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Parking Management Center | Archived Data System | parking archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Payment Administration Center | Archived Data System | payment archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Surface Transportation Weather Service | Archived Data System | transportation weather information | Low | Moderate | Moderate |
| Typically intended for public distribution. | There are several mechanisms by which weather information gets to a traveler, though given that the TIC may be performing some data fusion and providing value-added information, this data should be exchanged with some protection on its contents. | There are several mechanisms by which weather information gets to a traveler, though given that the TIC may be performing some data fusion and providing value-added information, this data should be exchanged with some protection on its contents. | |||
| Traffic Management Center | Archived Data System | traffic archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Transit Management Center | Archived Data System | transit archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
| Transportation Information Center | Archived Data System | traveler archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice.Not a real time service, so intermittent availability should suffice. | |||
| Weather Service System | Archived Data System | weather archive data | Moderate | Moderate | Low |
| While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. | May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. | Not a real time service, so intermittent availability should suffice. | |||
Standards
The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.
| Name | Title | Physical Object |
|---|---|---|
| CTI 4001 RSU | Roadside Unit (RSU) Standard | Connected Vehicle Roadside Equipment |
| ITE 5301 ATC ITS Cabinet | Intelligent Transportation System Standard Specification for Roadside Cabinets | ITS Roadway Equipment |
| NEMA TS 8 Cyber and Physical Security | Cyber and Physical Security for Intelligent Transportation Systems | Archived Data System |
| ITS Roadway Equipment |
System Requirements
| System Requirement | Need | ||
|---|---|---|---|
| 001 | The system shall receive operational data from the border inspection systems as well as administrative and registration data. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 002 | The system 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. 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. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 003 | The system shall receive and respond to requests from ITS Archives for either a catalog of the border operations data or for the data itself. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 004 | The system shall receive operational data from the roadside check systems as well as administration and credentials data. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 005 | The system 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. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 006 | The system shall receive and respond to requests from ITS Archives for either a catalog of the commercial vehicle operations data or for the data itself. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 007 | The system shall produce sample products of the data available. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 008 | The system shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor and surveillance data, threat data, and incident data. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 009 | The system shall receive and respond to requests from ITS Archives for either a catalog of the emergency management data or for the data itself. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 010 | The system shall collect air quality and emissions management data from various sources, including emissions sensors distributed along the roadside and wide-area sensors detecting pollution over a larger geographical area. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 011 | The system shall receive and respond to requests from ITS Archives for either a catalog of the emissions management data or for the data itself. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 012 | The system shall collect maintenance and construction data (such as field equipment status, infrastructure status, maintenance and construction activity data) gathered from roadway, traffic, and other maintenance and construction sources. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 013 | The system shall receive and respond to requests from ITS Archives for either a catalog of the maintenance and construction data or for the data itself. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 014 | The system shall collect toll operational data and roadway pricing data. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 015 | The system shall receive and respond to requests from ITS Archives for either a catalog of the toll data or for the data itself. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 016 | The system shall collect parking management data including lot usage and charging information. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 017 | The system shall receive and respond to requests from ITS Archives for either a catalog of the parking management data or for the data itself. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 018 | The system shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 019 | The system shall collect traveler requests, confirmations, and payment transaction data for traveler services provided. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 020 | The system shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or for the data itself. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 021 | The system shall collect traffic management data such as operational data, event logs, etc. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 022 | The system shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 023 | The system shall collect transit management data such as transit fares and passenger use, transit services, paratransit operations, transit vehicle maintenance data, etc. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 024 | The system shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data itself. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 025 | The system shall collect traffic, road, and environmental conditions information. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 026 | The system shall include the sensors and supporting roadside devices that sense, collect, and send traffic, road, and environmental conditions information to a center for archival. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 027 | The system shall collect sensor status and sensor faults from roadside equipment and send it along with the recorded data to a center for archival. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 028 | The system shall collect traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicles. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 029 | The system shall collect provide vehicle situation data to a center for archival. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 030 | The system shall provide collected vehicle situation and local sensor data to data distribution centers. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 031 | The system shall collect intermodal shipping data including shipping schedules, container statistics, chassis usage, traffic into and out of the facility. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 032 | The system shall collect data from centers. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 033 | The system shall collect data catalogs from one or more data sources. A catalog describes the data contained in the collection of archived data and may include descriptions of the schema or structure of the data, a description of the contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail). | 03 | System operators need to be able to manage data processing with regard to data archive functions, including data aggregation, data tagging (processed, edited, raw, transformed, etc.), data storage timing and longevity, data quality analysis, data formatting and metadata assignments. |
| 034 | The system shall store collected data in an information repository. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 035 | The system shall perform quality checks on collected data. | 03 | System operators need to be able to manage data processing with regard to data archive functions, including data aggregation, data tagging (processed, edited, raw, transformed, etc.), data storage timing and longevity, data quality analysis, data formatting and metadata assignments. |
| 036 | The system shall notify the system operator of errors related to data collection, analysis and archival. | 03 | System operators need to be able to manage data processing with regard to data archive functions, including data aggregation, data tagging (processed, edited, raw, transformed, etc.), data storage timing and longevity, data quality analysis, data formatting and metadata assignments. |
| 037 | The system shall include capabilities for archive to archive coordination. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 038 | The system shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive. | 03 | System operators need to be able to manage data processing with regard to data archive functions, including data aggregation, data tagging (processed, edited, raw, transformed, etc.), data storage timing and longevity, data quality analysis, data formatting and metadata assignments. |
| 039 | The system shall collect data from data distribution systems and other data sources. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 040 | The system shall respond to requests from the administrator interface function to manage center-sourced data collection. | 03 | System operators need to be able to manage data processing with regard to data archive functions, including data aggregation, data tagging (processed, edited, raw, transformed, etc.), data storage timing and longevity, data quality analysis, data formatting and metadata assignments. |
| 041 | The system shall respond to requests from the administrator interface function to manage the archive data. | 03 | System operators need to be able to manage data processing with regard to data archive functions, including data aggregation, data tagging (processed, edited, raw, transformed, etc.), data storage timing and longevity, data quality analysis, data formatting and metadata assignments. |
| 042 | The system shall respond to requests for archive data from archive data users (centers, field devices). | 02 | System operators need to be able to query for and receive archive data products containing freeway data, tolling data, arterial data, parking data, transit and ridesharing data, incident management data, safety-related data, CVO data, environmental and weather data, vehicle and passenger data and intermodal operations data. |
| 043 | The system shall provide a mechanism for archive data users to request archive data by meta-data range. | 02 | System operators need to be able to query for and receive archive data products containing freeway data, tolling data, arterial data, parking data, transit and ridesharing data, incident management data, safety-related data, CVO data, environmental and weather data, vehicle and passenger data and intermodal operations data. |
| 044 | The system shall associate meta-data with archived data, including catalog data, statistical products determined from method execution and data longevity. | 03 | System operators need to be able to manage data processing with regard to data archive functions, including data aggregation, data tagging (processed, edited, raw, transformed, etc.), data storage timing and longevity, data quality analysis, data formatting and metadata assignments. |
| 045 | The system shall collect data from roadside devices. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 046 | The system shall respond to requests from the administrator interface function to manage field-sourced data collection. | 03 | System operators need to be able to manage data processing with regard to data archive functions, including data aggregation, data tagging (processed, edited, raw, transformed, etc.), data storage timing and longevity, data quality analysis, data formatting and metadata assignments. |
| 047 | The system shall provide the capability to adjust the collection of field-sourced data based on the statistical measures. | 03 | System operators need to be able to manage data processing with regard to data archive functions, including data aggregation, data tagging (processed, edited, raw, transformed, etc.), data storage timing and longevity, data quality analysis, data formatting and metadata assignments. |
| 048 | The system shall provide the capability to execute methods on the incoming field data such as aggregation and statistical measures before the data is stored in the archive. | 01 | System operators need to be able to store data for long term access by themselves and other operators. |
| 049 | The system shall respond to requests from the administrator interface function to select and manage data stored in the archive. | 02 | System operators need to be able to query for and receive archive data products containing freeway data, tolling data, arterial data, parking data, transit and ridesharing data, incident management data, safety-related data, CVO data, environmental and weather data, vehicle and passenger data and intermodal operations data. |
Implementations
- DM01.1 Traffic Data Mart
- DM01.2 Public Transportation Data Mart
- DM01.3 Comprehensive Transportation Data Warehouse
- DM01.4 Distributed Data Warehouse
Display:
Implementation legend
or
Service Package legend
DM01.1 Traffic Data Mart Implementation
Establish a focused traffic data repository for a jurisdiction or region. This implementation collects traffic data from traffic detectors or connected vehicles. Current traffic control system information (e.g., info on control status, phases and splits, preemptions, ped delays, etc.) can also be included to provide important control context for the traffic data. A focused traffic data repository makes the collected traffic data and traffic control information available to end users and government reporting systems. This implementation represents the traffic data collection capability provided by Automated Traffic Signal Performance Measures (ATSPM) systems. This service package provides only basic reporting. See also DM02 for more advanced query-based performance measure reporting capabilities that can be added.
Traffic Data Mart Implementation Flows
| Information Flow | Description | Inclusion Status |
|---|---|---|
| archive coordination | Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and satisfy user data requests. | Optional |
| archive management data | Presentation of information to the administrator to support the management of an ITS archive including database reports on the condition and quality of the archived data, status of the import and collection process, reports that monitor archive usage, and | Optional |
| archive management requests | User input from the administrator including commands, requests, and queries that support data collection, administration, and management of an ITS data archive. | Optional |
| archive status | Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified. | At Least One |
| archived data product requests | A user-specified request for archived data products (i.e., data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any. | Fundamental |
| archived data products | Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information. | Fundamental |
| data collection and monitoring control | Information used to configure and control data collection and monitoring systems. | At Least One |
| local situation data | This general flow represents the traffic, environmental, and emissions situation data that is collected from connected vehicles by an RSE, aggregated, filtered, and provided to a back-office center. It also includes data collected from ITS roadway equipm | At Least One |
| roadside archive data | A broad set of data derived from roadside sensors that includes current traffic conditions, environmental conditions, and any other data that can be directly collected by roadside sensors. This data also indicates the status of the sensors and reports of | At Least One |
| traffic archive data | Information describing the use and vehicle composition on transportation facilities and the traffic control strategies employed. Content may include a catalog of available information, the actual information to be archived, and associated meta data that d | At Least One |
| traveler archive data | Data associated with traveler information services including service requests, facility usage, rideshare, routing, and traveler payment transaction data. Content may include a catalog of available information, the actual information to be archived, and a | At Least One |
Traffic Data Mart Implementation Functional Objects
| Functional Object |
|---|
| Archive Data Repository |
| Archive Situation Data Archival |
| Roadway Data Collection |
| RSE Situation Monitoring |
| TIC Operations Data Collection |
| TMC Data Collection |
Back to Implementation List
DM01.2 Public Transportation Data Mart Implementation
Establish a public transportation data repository for a jurisdiction or region that collects public transportation system status and performance over time and makes the data available to agency staff and other data users.
Public Transportation Data Mart Implementation Flows
| Information Flow | Description | Inclusion Status |
|---|---|---|
| archive coordination | Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and satisfy user data requests. | Optional |
| archive management data | Presentation of information to the administrator to support the management of an ITS archive including database reports on the condition and quality of the archived data, status of the import and collection process, reports that monitor archive usage, and | Optional |
| archive management requests | User input from the administrator including commands, requests, and queries that support data collection, administration, and management of an ITS data archive. | Optional |
| archive status | Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified. | Optional |
| archive status | Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified. | Fundamental |
| archived data product requests | A user-specified request for archived data products (i.e., data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any. | Fundamental |
| archived data products | Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information. | Fundamental |
| multimodal archive data | Operational information from alternate passenger transportation modes including air, rail transit, taxis, and ferries. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes | Optional |
| payment archive data | Data indicating roadway payments including toll facility usage and pricing schedules. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. | Optional |
| transit archive data | 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. | Fundamental |
Public Transportation Data Mart Implementation Functional Objects
| Functional Object |
|---|
| Archive Data Repository |
| PAC Data Collection |
| Transit Center Data Collection |
Back to Implementation List
DM01.3 Comprehensive Transportation Data Warehouse Implementation
Establish a more comprehensive data repository that collects together transportation data from one or more modes and jurisdictions. (This is essentially the entire SP, since the ARC-IT convention is that implementations, taken together, should cover the entire SP.)
Comprehensive Transportation Data Warehouse Implementation Flows
| Information Flow | Description | Inclusion Status |
|---|---|---|
| archive coordination | Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and satisfy user data requests. | Optional |
| archive management data | Presentation of information to the administrator to support the management of an ITS archive including database reports on the condition and quality of the archived data, status of the import and collection process, reports that monitor archive usage, and | Optional |
| archive management requests | User input from the administrator including commands, requests, and queries that support data collection, administration, and management of an ITS data archive. | Optional |
| archive status | Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified. | Optional |
| archived data product requests | A user-specified request for archived data products (i.e., data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any. | Fundamental |
| archived data products | Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information. | Fundamental |
| asset archive data | Information describing transportation assets including pavements, bridges, and all other infrastructure included in the transportation network. In addition, information can cover support assets (support equipment and systems, software, etc.). Content ma | At Least One |
| border information archive data | Border inspection activities data. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. | At Least One |
| commercial vehicle archive data | Information describing commercial vehicle travel and commodity flow characteristics. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. | At Least One |
| data collection and monitoring control | Information used to configure and control data collection and monitoring systems. | Optional |
| emergency archive data | Logged emergency information including information that characterizes identified incidents (routine highway incidents through disasters), corresponding incident response information, evacuation information, surveillance data, threat data, and resource inf | At Least One |
| emissions archive data | Air quality and vehicle emissions information that is collected by sensors or derived from models. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived informa | At Least One |
| intermodal freight archive data | Information describing demand at intermodal freight terminals including loading/unloading activities of trailers and containers. Content may include a catalog of available information, the actual information to be archived, and associated meta data that | At Least One |
| local situation data | This general flow represents the traffic, environmental, and emissions situation data that is collected from connected vehicles by an RSE, aggregated, filtered, and provided to a back-office center. It also includes data collected from ITS roadway equipm | At Least One |
| maint and constr archive data | Information describing road construction and maintenance activities identifying the type of activity, the work performed, and work zone information including work zone configuration and safety (e.g., a record of intrusions and vehicle speeds) information. | At Least One |
| multimodal archive data | Operational information from alternate passenger transportation modes including air, rail transit, taxis, and ferries. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes | At Least One |
| other data source archive data | Data extracted from other data sources. A wide range of ITS and non-ITS data and associated meta data may be provided. | At Least One |
| parking archive data | Data used to analyze and monitor trends in parking demand, pricing, and operational actions. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. | At Least One |
| payment archive data | Data indicating roadway payments including toll facility usage and pricing schedules. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. | At Least One |
| roadside archive data | A broad set of data derived from roadside sensors that includes current traffic conditions, environmental conditions, and any other data that can be directly collected by roadside sensors. This data also indicates the status of the sensors and reports of | At Least One |
| traffic archive data | Information describing the use and vehicle composition on transportation facilities and the traffic control strategies employed. Content may include a catalog of available information, the actual information to be archived, and associated meta data that d | At Least One |
| transit archive data | 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. | At Least One |
| transportation weather information | Current and forecast road conditions and weather information (e.g., surface condition, flooding, wind advisories, visibility, etc.) associated with the transportation network. This information is of a resolution, timeliness, and accuracy to be useful in | At Least One |
| traveler archive data | Data associated with traveler information services including service requests, facility usage, rideshare, routing, and traveler payment transaction data. Content may include a catalog of available information, the actual information to be archived, and a | At Least One |
| weather archive data | Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.) as well as qualified environmental sensor data. Content may include a catalog of availa | At Least One |
Comprehensive Transportation Data Warehouse Implementation Functional Objects
Back to Implementation List
DM01.4 Distributed Data Warehouse Implementation
Provide virtual access to multiple focused archives to satisfy multimodal requests for transportation data that is physically stored in multiple repositories. (This is the only implementation where the Other Archive triples are mandatory. Not a very interesting implementation, but it does serve to highlight this inter-archive data sharing interface)
Distributed Data Warehouse Implementation Flows
| Information Flow | Description | Inclusion Status |
|---|---|---|
| archive coordination | Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and satisfy user data requests. | Fundamental |
| archive management data | Presentation of information to the administrator to support the management of an ITS archive including database reports on the condition and quality of the archived data, status of the import and collection process, reports that monitor archive usage, and | Optional |
| archive management requests | User input from the administrator including commands, requests, and queries that support data collection, administration, and management of an ITS data archive. | Optional |
| archived data product requests | A user-specified request for archived data products (i.e., data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any. | Fundamental |
| archived data products | Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information. | Fundamental |
Distributed Data Warehouse Implementation Functional Objects
| Functional Object |
|---|
| Archive Data Repository |
Back to Implementation List