OTIC Maintenance Dispatch Offices
Status: Existing
Description
Represents offices along the Ohio Turnpike that provide the dispatch function for turnpike roadway and equipment maintenance vehicles. Provides roadway and equipment maintenance for OTIC assets in the region.
Stakeholders
Physical Objects
Functional Objects
| 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 Map Management | 'Center Map Management' provides the map functionality necessary to support map updates and use within an operational center. It manages map data for the center and provides map data to center applications that use a map. | False |
|---|
| MCM Field Equipment Maintenance | 'MCM Field Equipment Maintenance' provides overall management and support for maintenance of field equipment on a roadway system, right–of–way, parking area, transit stop, or other areas where field equipment exists. Services include repair and maintenance of ITS field equipment in these areas (e.g., detectors and other sensors, cameras, dynamic message signs, electronic toll collection equipment, electronic clearance equipment, weigh–in–motion sensors, etc.). | False |
|---|
| MCM Infrastructure Monitoring | 'MCM Infrastructure Monitoring' monitors the condition of pavement, bridges, tunnels, associated hardware, and other transportation–related infrastructure (e.g., culverts). It monitors the infrastructure, collecting data from both fixed and vehicle–based sensors. In addition to specialized infrastructure monitoring sensors, it also monitors the broader population of equipped vehicles for vertical acceleration data and other situation data that may be used to determine current pavement condition. | False |
|---|
| MCM Reduced Speed Zone Warning | 'MCM Reduced Speed Zone Warning' supports remote control and monitoring of reduced speed zone warning roadside equipment. It provides posted speed limits and associated schedules and information about associated road configuration changes including lane merges and shifts. It monitors field equipment operation and reports current status to the operator. | False |
|---|
Physical Standards
| 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. |
|---|
Interfaces To
(View Context Diagram)