Represent ODOT traffic signal control software. ODOT traffic signal systems range from fixed–schedule control systems to fully traffic responsive systems that dynamically adjust control plans and strategies based on current traffic conditions and priority requests.
| Functional Object | Description | User Defined |
|---|
| Center Connected Vehicle Infrastructure Management | 'Center Connected Vehicle Infrastructure Management' is the back office application that supports monitoring and maintenance of the Connected Vehicle infrastructure (RSEs, support systems, and associated communications links). It monitors the performance and configuration of the infrastructure portion of the Connected Vehicle Environment. This includes tracking and management of the infrastructure configuration as well as detection, isolation, and correction of infrastructure service problems. The application also includes monitoring of performance of the infrastructure equipment, including RSEs and communications links. | False |
|---|
| Center Data Collection | 'Center Data Collection' collects and stores information that is created in the course of 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. | False |
|---|
| Center Data Subscription Management | 'Center Data Subscription Management' manages data subscriptions for an end user. It provides access to a catalog of available data, manages the necessary user information and rules that govern the data subscriptions, supports communications with data providers to collect data per the subscription rules, and makes the data available to the end user. It provides the local user interface through which a user can specify and manage subscriptions. It supports different mechanisms for collecting subscribed data for the end–user including one–time query–response as well as publish–subscribe services. | False |
|---|
| Center Permission Management | 'Center Permission Management' enables Connected Vehicle system users to request permission to access connected vehicle services. A center may request permission for the center or the infrastructure devices and vehicles associated with the center. | False |
|---|
| Center Support Services | 'Center Support Services' provides foundational functions that support data collection, management, location reference, timing, and data distribution. It maintains precise location and time information to support other services. | False |
|---|
| ITS Communications Support | 'ITS Communications Support' provides means to send and receive messages to and from other ITS Objects. It provides mechanisms for scheduling and prioritizing communications traffic. It may also provide relay functions. | False |
|---|
| ITS Management Support | 'ITS Management Support' provides management of the ITS Object. This includes management of regulatory information and policies, management of application processes, management of communication system configuration and update management, communications interfaces, protocol–specific techniques to ensure interoperability such as service advertisements, communications congestion management and interference management, local device states and communications information, billing management, fault management, service level and performance monitoring. | False |
|---|
| ITS Security Support | 'ITS Security Support' provides communications and system security functions to the ITS Object, including privacy protection functions. It may include firewall, intrusion management, authentication, authorization, profile management, identity management, cryptographic key management. It may include a hardware security module and security management information base. | False |
|---|
| TMC Advanced Rail Crossing Management | 'TMC Advanced Rail Crossing Management' monitors and controls rail crossing traffic control equipment at advanced crossings that provide additional information on approaching trains, detect and report obstructions on the grade crossing, and communicate directly with equipped vehicles approaching the crossing. It remotely monitors and reports the status of the rail crossing equipment and sends control plan updates to the equipment. It also provides enhanced coordination between rail operations and traffic management centers that supports forecast of closure times and durations that may be applied to advanced traffic control strategies or delivered as enhanced traveler information. | False |
|---|
| TMC Basic Surveillance | 'TMC Basic Surveillance' remotely monitors and controls traffic sensor systems and surveillance (e.g., CCTV) equipment, and collects, processes and stores the collected traffic data. Current traffic information and other real–time transportation information is also collected from other centers. The collected information is provided to traffic operations personnel and made available to other centers. | False |
|---|
| 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. | False |
|---|
| TMC Roadway Equipment Monitoring | 'TMC Roadway Equipment Monitoring' monitors the operational status of field equipment and detects failures. It presents field equipment status to Traffic Operations Personnel and reports failures to the Maintenance and Construction Management Center. It tracks the repair or replacement of the failed equipment. The entire range of ITS field equipment may be monitored including sensors (traffic, infrastructure, environmental, security, speed, etc.) and devices (highway advisory radio, dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security surveillance equipment, etc.). | False |
|---|
| TMC Signal Control | 'TMC Signal Control' provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single Traffic Management Center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc. | False |
|---|
| TMC Standard Rail Crossing Management | 'TMC Standard Rail Crossing Management' monitors and controls rail crossing traffic control equipment. This version provides basic support for standard active warning systems at grade crossings. It remotely monitors and reports the status of the rail crossing equipment and sends control plan updates to the equipment. | False |
|---|
| Document Number | Title | Description |
|---|
| ISO 21217 | Intelligent transport systems –– Communications access for land mobiles (CALM) –– Architecture | ISO 21217 describes the communications reference architecture of nodes called "ITS station units" designed for deployment in ITS communication networks. While it describes a number of ITS station elements, whether or not a particular element is implemented in an ITS station unit depends on the specific communication requirements of the implementation. It also describes the various communication modes for peer–to–peer communications over various networks between ITS communication nodes. These nodes may be ITS station units as described in the document or any other reachable nodes. ISO 21217 specifies the minimum set of normative requirements for a physical instantiation of the ITS station based on the principles of a bounded secured managed domain. |
|---|
| NEMA TS 8 | Cyber and Physical Security for Intelligent Transportation Systems | This specification describes how agencies and other transportation infrastructure owner/operators should implement cyber– and physical–security for ITS. |
|---|
| NIST FIPS PUB 140–2 | Security Requirements for Cryptographic Modules | This Federal Information Processing Standard (140–2) specifies the security requirements that will be satisfied by a cryptographic module, providing four increasing, qualitative levels intended to cover a wide range of potential applications and environments. The areas covered, related to the secure design and implementation of a cryptographic module, include specification; ports and interfaces; roles, services, and authentication; finite state model; physical security; operational environment; cryptographic key management; electromagnetic interference/electromagnetic compatibility (EMI/EMC); self–tests; design assurance; and mitigation of other attacks. |
|---|