ODOT District 4 Automated Gate Closure Systems
Status: Future
Description
Represents automated road closure gates owned and operated by ODOT used for the remote closure of roads, lanes or ramps. Intended to be for areas where ice or snow or other adverse weather conditions exist on a frequent basis and that cause hazardous conditions for motorists.
Stakeholders
| Stakeholder | Role | Role Status |
|---|
| ODOT | Owns | Planned |
|---|
Physical Objects
Functional Objects
| Functional Object | Description | User Defined |
|---|
| Roadway Barrier System Control | 'Roadway Barrier System Control' includes the field equipment that controls barrier systems used to control access to transportation facilities and infrastructure. Barrier systems include automatic or remotely controlled gates, barriers and other access control systems. | False |
|---|
| 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. | False |
|---|
| Roadway Safeguard System Control | 'Roadway Safeguard System Control' includes field equipment that controls safeguard systems for transportation facilities and infrastructure. Safeguard systems include blast shields, exhaust systems and other automatic or remotely controlled systems intended to mitigate the impact of an incident. | False |
|---|
| Roadway Time Management | 'Roadway Time Management' provides foundational time keeping functionality that supports an accurate, synchronized time reference in ITS field equipment. It receives accurate time information from an external source and maintains a local time reference using an internal clock in between time synchronizations. | False |
|---|
Physical Standards
| Document Number | Title | Description |
|---|
| ITE ATC 5201 | Advanced Transportation Controller | This standard defines the functionality and performance requirements for a modern ITS controller known as an ATC. It is similar to the NEMA TS–2 standard in that it defines basic capabilities but leaves hardware choices up to the manufacturer. |
|---|
| ITE ATC 5202 | Model 2070 Controller Standard | This standard specifies the hardware for a modern, open–architecture controller for ITS applications that can run Linux and is capable of executing advanced signal controller logic, among other things. |
|---|
| ITE ATC 5301 | Intelligent Transportation System Standard Specification for Roadside Cabinets | This standard specifies the characteristics of a modern controller cabinet for the ITS industry. |
|---|
| ITE ATC 5401 | Application Programming Interface Standard for the Advanced Transportation Controller | This standard defines the application programmers' interface (API) that should be supported by an ATC, which is an open–architecture controller that can host multiple ITS applications. |
|---|
| NEMA TS 5 | Portable Traffic Signal Systems (PTSS) Standard | This standard specifies traffic signaling equipment used to enable and expedite the safe movement of vehicle traffic and the performance of work zone activities. |
|---|
| 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. |
|---|
| NEMA TS2 | Traffic Controller Assemblies with NTCIP Requirements | This specification covers traffic signaling equipment used to facilitate and expedite the safe movement of pedestrians and vehicular traffic. |
|---|
| NEMA TS4 | Hardware Standards for Dynamic Message Signs (DMS) With NTCIP Requirements | This standard provides hardware specifications for safe, dependable, functional, and easily maintained Dynamic Message Sign (DMS) equipment. |
|---|
Interfaces To
(View Context Diagram)