Online Services | Commonwealth Sites | Help | Governor


VDOT Roadway Conditions Database

Status:

Planned

Definition:

This statewide database, when completed, will be a clearinghouse for real-time and archived roadway conditions. The database will be used to feed real-time roadway conditions data into the statewide 511 system.

Stakeholder:

VDOT Central Office

Systems Interconnected
with the VDOT Roadway Conditions Database


Architecture Flow Diagrams
which include VDOT Roadway Conditions Database:

Architecture Flows
to/from the VDOT Roadway Conditions Database:

VDOT Roadway Conditions Database flows into icon VDOT Asset Management System VDOT Roadway Conditions Database flows into icon VDOT NRO MPSTOC VDOT Roadway Conditions Database flows into icon VDOT Staunton TOC VDOT Asset Management Systemflows into iconVDOT Roadway Conditions Database VDOT NRO MPSTOCflows into iconVDOT Roadway Conditions Database VDOT Staunton TOCflows into iconVDOT Roadway Conditions Database VDOT VaTrafficflows into iconVDOT Roadway Conditions Database

National ITS Architecture Subsystems
mapped to the VDOT Roadway Conditions Database:

National ITS Architecture Services
associated with VDOT Roadway Conditions Database:

National ITS Architecture Functional Requirements
associated with VDOT Roadway Conditions Database:

ITS Data Repository
  1. The center shall collect data to be archived from one or more data sources.
  2. The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the collection of archived data and may include descriptions of the schema or structure of the data, a description of the contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).
  3. The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.
  4. The center shall include capabilities for performing quality checks on the incoming archived data.
  5. The center shall include capabilities for error notification on the incoming archived data.
  6. The center shall include capabilities for archive to archive coordination.
  7. The center shall support a broad range of archived data management implementations, ranging from simple data marts that collect a focused set of data and serve a particular user community to large-scale data warehouses that collect, integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.
  8. The center shall perform quality checks on received data.
  9. The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive.
  10. The center shall respond to requests from the administrator interface function to maintain the archive data.
  11. When data or a catalog of data is received from the archive, the center shall generate the requested data product for the users systems.
  12. For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a Financial Institution.
Traffic and Roadside Data Archival
  1. The center shall manage the collection of archive data directly from collection equipment located at the roadside.
  2. The center shall collect traffic sensor information from roadside devices.
  3. The center shall collect environmental sensor information that from roadside devices.
  4. The center shall respond to requests from the Archive Data Administer to input the parameters that control the collection process.
  5. The center shall send the request for data and control parameters to the field equipment where the information is collected and returned.
  6. The center shall record the status about the imported traffic and roadside data.
  7. The center shall use the status information to adjust the collection of traffic and roadside data.
Government Reporting Systems Support
  1. The center shall provide data from an ITS archive to federal, state, or local government reporting systems.
  2. The center shall provide the capability to select data from an ITS archive for use in government reports.
  3. The center shall provide the capability to format data from an ITS archive suitable for input into government reports.
  4. The center shall support requests for ITS archived data from Government Reporting Systems.
  5. The center shall provide the applicable meta-data for any ITS archived data to satisfy government reporting system requests. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.
ISP Traveler Data Collection
  1. The center shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.
  2. The center shall collect, process, and store maintenance and construction information, including scheduled maintenance and construction work activities and work zone activities.
  3. The center shall collect, process, and store transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information.
  4. The center shall collect, process, and store parking information, including location, availability, and fees.
  5. The center shall collect, process, and store toll fee information.
  6. The center shall collect, process, and store current and forecast road conditions and surface weather conditions.
  7. The center shall collect, process, and store event information.
  8. The center shall collect, process, and store air quality information.
Interactive Infrastructure Information
  1. The center shall disseminate customized traffic and highway condition information to travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific routes upon request.
  2. The center shall disseminate customized maintenance and construction information to travelers, including scheduled maintenance and construction work activities and work zone activities upon request.
  3. The center shall disseminate customized transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information to travelers upon request.
  4. The center shall disseminate customized parking information to travelers, including location, availability, and fees upon request.
  5. The center shall disseminate customized toll fee information to travelers upon request.
  6. The center shall disseminate customized weather information to travelers upon request.
  7. The center shall disseminate customized multimodal transportation service information (for example, from ferry and airline operators), including transfer points and other information, to travelers upon request.
  8. The center shall disseminate customized event information to travelers upon request.
  9. The center shall disseminate customized air quality information to travelers upon request.
  10. The center shall provide all traveler information based on the traveler's current location or a specific location identified by the traveler, and filter or customize the provided information accordingly.
  11. The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.
  12. The center shall manage payment for services, such as tolls, transit fares, parking lot charges, map updates, and advanced payment for tolls, and provide transaction success or failure details.
  13. The center shall support requests for traveler information and advanced payment for traveler services from commercial fleet operators.
  14. The center shall provide the capability to exchange information with another traveler information service provider current or predicted data for road links that are outside the area served by the local supplier.
  15. The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.
  16. The center shall provide the capability to support requests from the media for traffic and incident data.
  17. The center shall provide the capability for a system operator to control the type and update frequency of traveler information.
Traveler Telephone Information
  1. The center shall provide the capability to process voice-formatted requests for traveler information from a traveler telephone information system, and return the information in the requested format.
  2. The center shall provide the capability to process dual-tone multifrequency (DTMF)-based requests (touch-tone) for traveler information from a traveler telephone information system.
  3. The center shall provide the capability to process traveler information requests from a traveler telephone information system.
  4. The center shall provide information on traffic conditions in the requested voice format and for the requested location.
  5. The center shall provide work zone and roadway maintenance information in the requested voice format and for the requested location.
  6. The center shall provide roadway environment conditions information in the requested voice format and for the requested location.
  7. The center shall provide weather and event information in the requested voice format and for the requested location.
  8. The center shall provide transit service information in the requested voice format and for the requested location.
  9. The center shall provide yellow pages services information in the requested voice format and for the requested location.
  10. The center shall provide current ferry and rail schedule and airport status information in the requested voice format and for the requested location.
  11. The center shall provide the capability to support both specific caller requests as well as bulk upload of regional traveler information.
  12. The center shall receive and forward region-specific wide-area alert and advisory information to the traveler telephone information system, including major emergencies such as a natural or man-made disaster, civil emergency, child abductions, severe weather watches and warnings, military activities, and law enforcement warnings.
ISP Emergency Traveler Information
  1. The center shall disseminate emergency evacuation information to the traveler interface systems, including evacuation zones, shelter information, available transportation modes, road closures and detours, changes to transit services, and traffic and road conditions at the origin, destination, and along the evacuation routes.
  2. The center shall provide evacuation information to shelter providers.
  3. The center shall disseminate wide-area alert information to the traveler interface systems, including major emergencies such as a natural or man-made disaster, civil emergency, child abductions, severe weather watches and warnings, military activities, and law enforcement warnings.
  4. The center shall provide the capability for a system operator to control the type and update frequency of emergency and wide-area alert information distributed to travelers.
ISP Data Collection
  1. The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations.
  2. The center shall collect traveler requests, confirmations, and payment transaction data for traveler services provided.
  3. 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.
  4. The center shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or for the data itself.
  5. The center shall be able to produce sample products of the data available.