Operational Concepts: DDOT Transportation Operations Administration
The following are the roles and responsibilities, by functional area or by project, for the DDOT Transportation Operations Administration.| Functional Area or Project | Roles and Responsibilities | Status |
|---|---|---|
|
Archived Data Systems for District of Columbia ITS Architecture |
Collect and archive traffic information from traffic sensors, including traffic volumes, speeds and occupancy. | Existing |
|
District Public Traveler Information System |
Provide traffic information to travelers via traffic information devices on District-owned roadways (e.g., DMS and HAR equipment), and through local ISPs and web sites. | Existing |
| Provide traffic information to travelers via website, 511 system, information service providers, and the media. | Not Planned | |
|
District Video Exchange Network |
Share video images with other centers. | Planned |
|
Emergency Management for District of Columbia ITS Architecture |
Coordinate emergency plans and emergency responses with District EOC. Includes managing highways and arterials in response to and under the direction of the District EOC. | Existing |
| Coordinate evacuation and re-entry plans with the District EOC. | Existing | |
| Dispatch roadway service patrol vehicles that monitor roads that aid motorists, offering rapid response to minor incidents (flat tire, accidents, out of gas) to minimize disruption to the traffic stream. | Existing | |
| Monitor its transportation infrastructure (e.g., bridges, tunnels and operations centers) for potential threats using sensors and surveillance equipment and inform the appropriate emergency management agencies. | Planned | |
| Provide signal preemption for emergency vehicles. | Existing | |
|
Emergency Vehicle Preemption |
Provide signal preemption for emergency vehicles. | Existing |
|
Freeway Management for District of Columbia ITS Architecture |
Collect traffic data from highway system sensors. | Existing |
| Collect traffic probe information (e.g., highway travel times) from field sensors. | Existing | |
| Monitor and control highway traffic with traffic sensors, ramp meters and lane control signals. | Existing | |
| Monitor highway surveillance cameras. | Existing | |
| Provide traffic information reports to other traffic management agencies. | Existing | |
|
Generic |
Not Planned | |
| Provide traffic information reports to other traffic management agencies. | Not Planned | |
|
Incident Management for District of Columbia ITS Architecture |
Not Planned | |
| Control high occupancy vehicle (HOV) lanes. | Planned | |
| Coordinate incident response for incidents on or adjacent to highways and arterials with public safety agencies, and EOCs in surrounding counties and municipalities, including response for scheduled events. | Existing | |
| Coordinate maintenance resources for incidents with other regional maintenance and construction operations. | Existing | |
| Perform network surveillance for incident detection and verification, and send traffic/incident information and traffic images to local public safety agencies and EOCs. | Existing | |
| Provide incident information to other traffic management and public safety agencies. | Existing | |
| Provide maintenance resources in response to incidents on highways and arterials. | Existing | |
| Receive maintenance resource requests for incident response from District police/fire/EMS and 911 emergency call centers. | Existing | |
| Share video images with other centers. | Not Planned | |
|
Maintenance and Construction for District of Columbia ITS Architecture |
Collect environmental information from District field equipment, and from public and private weather service providers. | Existing |
| Collect road weather information from field sensors. | Existing | |
| Coordinate maintenance activities with DPW and with maintenance organizations in adjoining jurisdictions. | Existing | |
| Distribute environmental data to private weather providers, regional TOCs, regional emergency management agencies, regional transit agencies, and District and other municipal maintenance sections. | Existing | |
| Distribute work zone information to local transit agencies, local emergency management agencies, private rail operations, the media, and multimodal service providers. | Existing | |
| Manage work zones for all District maintenance and construction activities, and monitor work zone safety with District field devices and vehicles. | Existing | |
| Perform maintenance for ITS field equipment owned by the District DOT. | Existing | |
| Provide automated maintenance status information on maintenance vehicles to the District maintenance dispatch and equipment repair facility. | Planned | |
| Provide environmental data to public and private weather service providers. | Existing | |
| Provide maintenance and construction information to District maintenance and construction operations; regional maintenance and construction operations; and the traveling public through portable DMS devices. | Existing | |
| Receive automatic vehicle location (AVL) information from District maintenance vehicles. | Existing | |
|
Parking Management for District of Columbia ITS Architecture |
Provide parking information to local area transit systems. | Planned |
| Provide parking information to the regional traveler information system. | Planned | |
| Receive parking lot input from transportation management centers for traffic coordination at parking facilities. | Planned | |
|
Regional Coordination |
Provide traffic information reports to other traffic management agencies. | Existing |
|
Surface Street Management for District of Columbia ITS Architecture |
Coordinate with WMATA, Circulator and Streetcar Rail Operations | Planned |
| Manage drawbridges via control devices (e.g., gates, warning lights, dynamic message signs) at the drawbridge as well as the traveler information systems. | Existing | |
| Monitor and control reversible lanes on highways and District-owned arterials with lane control signals. | Existing | |
| Monitor and control traffic information devices of other traffic management agencies, such as dynamic message signs, during certain agreed upon conditions, such as specific hours or during specific emergencies. | Existing | |
| Monitor the speeds of vehicles traveling on the highway or arterials. | Planned | |
| Operate traffic information devices, such as dynamic message signs and highway advisory radios. | Existing | |
| Provide traffic information in a coordinated effort to the District traveler information system, websites and other traffic management agencies. | Existing | |
| Provide traffic information to travelers via traffic information devices on District-owned roadways (e.g., DMS and HAR equipment), and through local ISPs and web sites. | Existing | |
| Provide traffic information, such as road network conditions, information to transit agencies. | Existing | |
| Provide traffic information, such as road network conditions, to information service providers. | Existing | |
| Provide traffic information, such as road network conditions, to maintenance and construction agencies. | Existing | |
| Provide traffic information, such as road network conditions, to public safety agencies. | Existing | |
| Suggest a safe driving speed for vehicles traveling on the highway or arterials. | Existing | |
| Use decision support systems to improve traffic management. | Planned | |
|
Transit Services for District of Columbia ITS Architecture |
Provide signal priority for transit vehicles. | Planned |
|
Transit Signal Priority |
Provide signal priority for transit vehicles. | Planned |