---

Route 460 Toll Road

Status:

Existing

Definition:

This element represents the 55-mile (88.5km) section of the US Route 460 toll road from Petersburg to Suffolk.

Stakeholder:

Private Toll Facilities

Architecture Flow Diagrams
which include Route 460 Toll Road:

• Route 460 Toll Road VDOT Richmond TOC
• Route 460 Toll Road VDOT Smart-Tag EZ-Pass Customer Service Center
• Route 460 Toll Road VSP Center

Architecture Flows
to/from the Route 460 Toll Road:

Route 460 Toll Road VDOT Richmond TOC

• evacuation coordination


• incident response coordination


• resource coordination


• toll probe data


• toll service change response

Route 460 Toll Road VDOT Smart-Tag EZ-Pass Customer Service Center

• toll coordination

Route 460 Toll Road VSP Center

• incident information

VDOT Richmond TOCRoute 460 Toll Road

• evacuation coordination


• evacuation information


• incident information


• incident response coordination


• resource coordination


• toll service change request


• transportation system status

VDOT Smart-Tag EZ-Pass Customer Service CenterRoute 460 Toll Road

• toll coordination

National ITS Architecture Subsystems
mapped to the Route 460 Toll Road:

• Emergency Management Subsystem
• Other Toll Administration Terminator
• Other Traffic Management Terminator
• Roadway Subsystem
• Toll Administration Subsystem
• Toll Collection Subsystem
• Traffic Management Subsystem

National ITS Architecture Services
associated with Route 460 Toll Road:

• ATMS10 - Electronic Toll Collection - Private Toll Facilities -- (Graphic)

National ITS Architecture Functional Requirements
associated with Route 460 Toll Road:

Toll Data Collection

1. The center shall collect toll operational data and pricing data.
2. The center shall receive and respond to requests from ITS Archives for either a catalog of the toll data or for the data itself.

Toll Plaza Toll Collection

1. The field element shall read data from passing vehicles to support toll payment transactions.
2. The field element shall calculate the toll due based on the vehicle characteristics (vehicle size, weight, axle count, etc.) and stored toll prices.
3. The field element shall update the stored value after debiting the toll amount and send a record of the transaction to a center.
4. The field element shall read the credit identity from the passing vehicle and send that identity and the amount to be debited to a center.
5. The field element shall support advanced toll payment by checking the vehicle's toll information against a stored list of advanced payments, and debiting the toll from the list in the case of a match.
6. In the case of closed toll systems, the field element shall update the vehicle on-board data with the system entry point, and upon toll system exit, use the stored data in the calculation of the toll.
7. The field element shall control roadside displays indicating success or failure of the toll transaction to the driver.
8. The field element shall control cameras, obtain images, and forward images of toll violators to a center.
9. The field element shall respond to changes in tolls from the Toll Operator.
10. The field element shall forward wide-area alert information to the Toll Operator.

Barrier System Management

1. The center shall remotely control barrier systems for transportation facilities and infrastructure. Barrier systems include automated or remotely controlled gates, barriers and other systems that manage entry to roadways.
2. The center shall collect barrier system operational status.
3. The center shall collect barrier system fault data and send to the maintenance center for repair.
4. The center shall accept requests for barrier system activation from other centers and from center personnel to support emergency response and detours.

Traffic Data Collection

1. The center shall collect traffic management data such as operational data, event logs, etc.
2. The 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.
3. The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data itself.
4. The center shall be able to produce sample products of the data available.