Stakeholder | Role and Responsibility |
---|
ADOT | Detect, Isolate and correct CV infrastructure field equipment problems. |
---|
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 sensors and surveillance data collection systems to other systems for distribution. |
Track and manage the configuration of the field equipment. |
Provide, modify and maintain software applications on connected vehicle roadside equipment. |
Cooperate as appropriate, and coordinate with public agency connected vehicle test bed activities and connected vehicle pilot projects. |
Work with local, regional, and federal agencies, as well as academia and the private sector, to ensure connected vehicle infrastructure and systems are fully interoperable throughout the state. |
Install, operate, and maintain Connected Vehicle Roadside Equipment. |
Collect, filter, compile, and archive metadata for traveler data, emergency response data, to connected vehicle roadside equipment from vehicles, roadside equipment or other personal devices. |
Arizona Universities | Perform research–oriented activities on connected vehicle deployments to advance the deployment of connected vehicle infrastructure and applications; similar to the MCDOT SMARTDrive Program and the related Deployment Readiness of the Multi–Modal Intelligent Traffic Signal System (MMITSS) deployments. |
---|
Simulation and optimization models in specific applications, studying new connected vehilce hardware and software systems. |
Investigate future connected and automated vehicle systems; Investigation of Impact and Opportunities for Automated Driving Vehicles. |
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. |
Oversee and coordinate public agency connected vehicle test bed activities and connected vehicle pilot projects, as appropriate. |
Work with local, regional, and state agencies, as well as academia and the private sector, to ensure connected vehicle infrastructure and systems are fully interoperable throughout the state. |
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 | Provide customized information on travel times, transit routes, weather conditions and road closures, based on connected vehicle infrastructure and systems. |
---|
Coordinate and facilitate, as appropriate, sharing of traffic, event, weather, incident and other information generated from conected vehicle infrastructure and systems. |
Provide support from the media for traffic and incident data. |
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. |
Receive information, as apprpriate, without establishing formal relationships with data providers. |
Request permission for use of connected infrastructure data. |
Receive traffic and event information from connected vehicle infrastructure and systems. |