Parent Service Package: DM01
: DM01.1 : DM01.2 > >

DM01.1: Traffic Data Mart

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.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Archived Data AdministratorArchived Data System Operates
Archived Data System MaintainerArchived Data System Maintains
Archived Data System ManagerArchived Data Administrator System Usage Agreement
Archived Data System ManagerArchived Data System Manages
Archived Data System OwnerArchived Data System Maintainer System Maintenance Agreement
Archived Data System OwnerArchived Data System Manager Operations Agreement
Archived Data System OwnerArchived Data User System Maintainer Maintenance Data Exchange Agreement
Archived Data System OwnerArchived Data User System Operator Application Usage Agreement
Archived Data System OwnerArchived Data User System Owner Information Exchange Agreement
Archived Data System OwnerArchived Data User System User Service Usage Agreement
Archived Data System OwnerITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Archived Data System OwnerITS Roadway Equipment Owner Information Exchange Agreement
Archived Data System OwnerITS Roadway Equipment User Service Usage Agreement
Archived Data System OwnerMaint and Constr Field Personnel Application Usage Agreement
Archived Data System OwnerOther Archived Data Systems Maintainer Maintenance Data Exchange Agreement
Archived Data System OwnerOther Archived Data Systems Operator Application Usage Agreement
Archived Data System OwnerOther Archived Data Systems Owner Information Exchange Agreement
Archived Data System OwnerOther Archived Data Systems User Service Usage Agreement
Archived Data System OwnerTIC Operator Application Usage Agreement
Archived Data System OwnerTraffic Management Center Maintainer Maintenance Data Exchange Agreement
Archived Data System OwnerTraffic Management Center Owner Information Exchange Agreement
Archived Data System OwnerTraffic Management Center User Service Usage Agreement
Archived Data System OwnerTraffic Operations Personnel Application Usage Agreement
Archived Data System OwnerTransportation Information Center Maintainer Maintenance Data Exchange Agreement
Archived Data System OwnerTransportation Information Center Owner Information Exchange Agreement
Archived Data System OwnerTransportation Information Center User Service Usage Agreement
Archived Data System SupplierArchived Data System Owner Warranty
Archived Data User System MaintainerArchived Data User System Maintains
Archived Data User System ManagerArchived Data User System Manages
Archived Data User System ManagerArchived Data User System Operator System Usage Agreement
Archived Data User System OperatorArchived Data User System Operates
Archived Data User System OwnerArchived Data Administrator Application Usage Agreement
Archived Data User System OwnerArchived Data System Maintainer Maintenance Data Exchange Agreement
Archived Data User System OwnerArchived Data System Owner Information Exchange Agreement
Archived Data User System OwnerArchived Data System User Service Usage Agreement
Archived Data User System OwnerArchived Data User System Maintainer System Maintenance Agreement
Archived Data User System OwnerArchived Data User System Manager Operations Agreement
Archived Data User System SupplierArchived Data User System Owner Warranty
Connected Vehicle Roadside Equipment MaintainerConnected Vehicle Roadside Equipment Maintains
Connected Vehicle Roadside Equipment ManagerConnected Vehicle Roadside Equipment Manages
Connected Vehicle Roadside Equipment ManagerConnected Vehicle Roadside Equipment Operator System Usage Agreement
Connected Vehicle Roadside Equipment OperatorConnected Vehicle Roadside Equipment Operates
Connected Vehicle Roadside Equipment OwnerArchived Data Administrator Application Usage Agreement
Connected Vehicle Roadside Equipment OwnerArchived Data System Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment OwnerArchived Data System Owner Information Provision Agreement
Connected Vehicle Roadside Equipment OwnerArchived Data System User Service Usage Agreement
Connected Vehicle Roadside Equipment OwnerConnected Vehicle Roadside Equipment Maintainer System Maintenance Agreement
Connected Vehicle Roadside Equipment OwnerConnected Vehicle Roadside Equipment Manager Operations Agreement
Connected Vehicle Roadside Equipment SupplierConnected Vehicle Roadside Equipment Owner Warranty
ITS Roadway Equipment MaintainerITS Roadway Equipment Maintains
ITS Roadway Equipment ManagerITS Roadway Equipment Manages
ITS Roadway Equipment ManagerMaint and Constr Field Personnel System Usage Agreement
ITS Roadway Equipment OwnerArchived Data Administrator Application Usage Agreement
ITS Roadway Equipment OwnerArchived Data System Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment OwnerArchived Data System Owner Information Provision Agreement
ITS Roadway Equipment OwnerArchived Data System User Service Usage Agreement
ITS Roadway Equipment OwnerITS Roadway Equipment Maintainer System Maintenance Agreement
ITS Roadway Equipment OwnerITS Roadway Equipment Manager Operations Agreement
ITS Roadway Equipment SupplierITS Roadway Equipment Owner Warranty
Maint and Constr Field PersonnelITS Roadway Equipment Operates
Other Archived Data Systems MaintainerOther Archived Data Systems Maintains
Other Archived Data Systems ManagerOther Archived Data Systems Manages
Other Archived Data Systems ManagerOther Archived Data Systems Operator System Usage Agreement
Other Archived Data Systems OperatorOther Archived Data Systems Operates
Other Archived Data Systems OwnerArchived Data Administrator Application Usage Agreement
Other Archived Data Systems OwnerArchived Data System Maintainer Maintenance Data Exchange Agreement
Other Archived Data Systems OwnerArchived Data System Owner Information Exchange Agreement
Other Archived Data Systems OwnerArchived Data System User Service Usage Agreement
Other Archived Data Systems OwnerOther Archived Data Systems Maintainer System Maintenance Agreement
Other Archived Data Systems OwnerOther Archived Data Systems Manager Operations Agreement
Other Archived Data Systems SupplierOther Archived Data Systems Owner Warranty
TIC OperatorTransportation Information Center Operates
Traffic Management Center MaintainerTraffic Management Center Maintains
Traffic Management Center ManagerTraffic Management Center Manages
Traffic Management Center ManagerTraffic Operations Personnel System Usage Agreement
Traffic Management Center OwnerArchived Data Administrator Application Usage Agreement
Traffic Management Center OwnerArchived Data System Maintainer Maintenance Data Exchange Agreement
Traffic Management Center OwnerArchived Data System Owner Information Exchange Agreement
Traffic Management Center OwnerArchived Data System User Service Usage Agreement
Traffic Management Center OwnerTraffic Management Center Maintainer System Maintenance Agreement
Traffic Management Center OwnerTraffic Management Center Manager Operations Agreement
Traffic Management Center SupplierTraffic Management Center Owner Warranty
Traffic Operations PersonnelTraffic Management Center Operates
Transportation Information Center MaintainerTransportation Information Center Maintains
Transportation Information Center ManagerTIC Operator System Usage Agreement
Transportation Information Center ManagerTransportation Information Center Manages
Transportation Information Center OwnerArchived Data Administrator Application Usage Agreement
Transportation Information Center OwnerArchived Data System Maintainer Maintenance Data Exchange Agreement
Transportation Information Center OwnerArchived Data System Owner Information Exchange Agreement
Transportation Information Center OwnerArchived Data System User Service Usage Agreement
Transportation Information Center OwnerTransportation Information Center Maintainer System Maintenance Agreement
Transportation Information Center OwnerTransportation Information Center Manager Operations Agreement
Transportation Information Center SupplierTransportation Information Center Owner Warranty

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
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.
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.
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.
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.
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.
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.

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, anonymization as needed, 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. Repositories may provide visualization outputs (e.g. dashboards) for use by the Archive Data User System. 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
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
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

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.
data collection and monitoring control Information used to configure and control data collection and monitoring systems.
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.
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.
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.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective Performance Measure


 
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

Related Sources

Document Name Version Publication Date
None


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Archived Data System High High High Class 5
Archived Data User System High High Low Class 4
Connected Vehicle Roadside Equipment Low Moderate Low Class 1
ITS Roadway Equipment Moderate Moderate Low Class 2
Other Archived Data Systems Moderate High High Class 5
Traffic Management Center High High Moderate Class 4
Transportation Information Center High High Moderate Class 4



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
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 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 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 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 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 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 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.
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.
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.
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.
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.
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.

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.

NameTitlePhysical 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

No System Requirements