Stakeholder | Role and Responsibility |
---|
ADOT | Use systems polling feature to provide fault data |
Maintain centralized signal systems and software that monitors, analyzes and stores traffic sensor data. |
Establishing and maintaining data processing algorithms, rules and related metadata including all those processes related to validation, integration, sanitization and aggregation (VISA). |
Exchange road network conditions from traffic sensor and surveillance data collection to other systems for distribution. |
Tracking and managing the configuration of the field equipment. |
Detecting, Isolating and correcting CV infrastructure field equipment problems. |
Maintain field equipment. |
Providing, modifying and maintaining software applications on connected vehicle roadside equipment. |
Collecting, filtering, compiling, retrieving and archiving metadata for traveler data, emergency response data, to connected vehicle roadside equipment from vehicles, roadside equipment or other personal devices. |
Arizona Universities | Investigate future connected and automated vehicle systems; Investigation of Impact and Opportunities for Automated Driving Vehicles. |
UofA's provide transportation expertise to perform research-oriented traffic and ITS development studies. Related tasks include the MCDOT SMARTDrive Program and related Deployment Readiness of the Multi-Modal Intelligent Traffic Signal System (MMITSS) and |
Simulation and optimization models in specific applications, studying new transportation hardware and software systems. |
AZTech | Connected Vehicle Roles and Responsibilities for AZTech are defined in the MAG Regional Architecture. |
Federal Highway Administration (FHWA) | Participate in meetings and serve in an advisory capacity for project development. |
Provide funding for Connected Vehicle projects. |
Maricopa County Department of Transportation (MCDOT) | Connected Vehicle Roles and Responsiblities for MCDOT is defined in the MAG Architecture |
Private Commercial Carriers | Provide, modify and maintain software applications inside trucks / vehicles to work with connected vehicle roadside equipment. |
Private Information Service Providers | Coordinate and facilitate sharing of traffic, event, weather, incident and other information on corridors crossing the boundaries between States and/or Districts |
Provide broadcast traveler information. |
Provide support from the media for traffic and incident data. |
Provide customized information on travel times, transit routes, weather conditions and road closures. |
Travelers | Receive traffic and event information from a regional information service provider. |
Utilize information provided by public agencies through DMS, smart phones, 511, etc... To re-route, telecommute or otherwise avoid traffic incidents. |
Allow vehicle settings to be read by local roadway devices for connected vehicles. |
Receiving information without establishing formal relationships with data providers. |
Request permission for use of connected infrastructure data. |