< < SU03 : SU04 : SU05 > >

SU04: Map Management

This service package defines interfaces that can be used download or update all types of map data used to support intelligent transportation systems. This map data will be accessed by centers, field, and vehicle physical objects. The service package can also be used to harness the Connected Vehicle Environment to provide rich source data that can be used to verify, refine, and enhance geographic map data.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Center Maintainer Center Maintains
Center Manager Center Manages
Center Owner Center Maintainer System Maintenance Agreement
Center Owner Center Manager Operations Agreement
Center Owner Map Update System Owner Information Exchange Agreement
Center Supplier Center Owner Warranty
Commercial Vehicle Administration Center Maintainer Commercial Vehicle Administration Center Maintains
Commercial Vehicle Administration Center Manager Commercial Vehicle Administration Center Manages
Commercial Vehicle Administration Center Owner Commercial Vehicle Administration Center Maintainer System Maintenance Agreement
Commercial Vehicle Administration Center Owner Commercial Vehicle Administration Center Manager Operations Agreement
Commercial Vehicle Administration Center Owner Map Update System Owner Information Provision Agreement
Commercial Vehicle Administration Center Supplier Commercial Vehicle Administration Center Owner Warranty
Connected Vehicle Roadside Equipment Maintainer Connected Vehicle Roadside Equipment Maintains
Connected Vehicle Roadside Equipment Manager Connected Vehicle Roadside Equipment Manages
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Maintainer System Maintenance Agreement
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Manager Operations Agreement
Connected Vehicle Roadside Equipment Owner Map Update System Owner Information Provision Agreement
Connected Vehicle Roadside Equipment Owner Personal Information Device Owner Expectation of Information Provision
Connected Vehicle Roadside Equipment Owner Vehicle OBE Owner Expectation of Information Provision
Connected Vehicle Roadside Equipment Supplier Connected Vehicle Roadside Equipment Owner Warranty
Maint and Constr Management Center Maintainer Maint and Constr Management Center Maintains
Maint and Constr Management Center Manager Maint and Constr Management Center Manages
Maint and Constr Management Center Owner Maint and Constr Management Center Maintainer System Maintenance Agreement
Maint and Constr Management Center Owner Maint and Constr Management Center Manager Operations Agreement
Maint and Constr Management Center Owner Map Update System Owner Information Provision Agreement
Maint and Constr Management Center Supplier Maint and Constr Management Center Owner Warranty
MAP GIS Operator Map Update System Operates
Map Update System Maintainer Map Update System Maintains
Map Update System Manager MAP GIS Operator System Usage Agreement
Map Update System Manager Map Update System Manages
Map Update System Owner Center Owner Information Exchange Agreement
Map Update System Owner Connected Vehicle Roadside Equipment Owner Information Exchange Agreement
Map Update System Owner Map Update System Maintainer System Maintenance Agreement
Map Update System Owner Map Update System Manager Operations Agreement
Map Update System Owner Other Map Update Systems Owner Information Exchange Agreement
Map Update System Owner Parking Area Equipment Owner Information Exchange Agreement
Map Update System Owner Personal Information Device Owner Information Provision Agreement
Map Update System Owner Traveler Support Equipment Owner Information Provision Agreement
Map Update System Owner Vehicle OBE Owner Information Exchange Agreement
Map Update System Supplier Map Update System Owner Warranty
Other Map Update Systems Maintainer Other Map Update Systems Maintains
Other Map Update Systems Manager Other Map Update Systems Manages
Other Map Update Systems Owner Map Update System Owner Information Exchange Agreement
Other Map Update Systems Owner Other Map Update Systems Maintainer System Maintenance Agreement
Other Map Update Systems Owner Other Map Update Systems Manager Operations Agreement
Other Map Update Systems Supplier Other Map Update Systems Owner Warranty
Other Vehicle OBEs Maintainer Other Vehicle OBEs Maintains
Other Vehicle OBEs Manager Other Vehicle OBEs Manages
Other Vehicle OBEs Owner Other Vehicle OBEs Maintainer System Maintenance Agreement
Other Vehicle OBEs Owner Other Vehicle OBEs Manager Operations Agreement
Other Vehicle OBEs Owner Vehicle OBE Owner Expectation of Data Provision
Other Vehicle OBEs Supplier Other Vehicle OBEs Owner Warranty
Parking Area Equipment Maintainer Parking Area Equipment Maintains
Parking Area Equipment Manager Parking Area Equipment Manages
Parking Area Equipment Owner Map Update System Owner Information Provision Agreement
Parking Area Equipment Owner Parking Area Equipment Maintainer System Maintenance Agreement
Parking Area Equipment Owner Parking Area Equipment Manager Operations Agreement
Parking Area Equipment Supplier Parking Area Equipment Owner Warranty
Personal Information Device Maintainer Personal Information Device Maintains
Personal Information Device Manager Personal Information Device Manages
Personal Information Device Owner Personal Information Device Maintainer System Maintenance Agreement
Personal Information Device Owner Personal Information Device Manager Operations Agreement
Personal Information Device Supplier Personal Information Device Owner Warranty
Traveler Support Equipment Maintainer Traveler Support Equipment Maintains
Traveler Support Equipment Manager Traveler Support Equipment Manages
Traveler Support Equipment Owner Traveler Support Equipment Maintainer System Maintenance Agreement
Traveler Support Equipment Owner Traveler Support Equipment Manager Operations Agreement
Traveler Support Equipment Supplier Traveler Support Equipment Owner Warranty
Vehicle OBE Maintainer Vehicle OBE Maintains
Vehicle OBE Manager Vehicle OBE Manages
Vehicle OBE Owner Connected Vehicle Roadside Equipment Owner Expectation of Data Provision
Vehicle OBE Owner Map Update System Owner Expectation of Data Provision
Vehicle OBE Owner Other Vehicle OBEs Owner Expectation of Data Provision
Vehicle OBE Owner Vehicle OBE Maintainer System Maintenance Agreement
Vehicle OBE Owner Vehicle OBE Manager Operations Agreement
Vehicle OBE Supplier Vehicle OBE Owner Warranty

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Center Center Map Management 10.3.5 Update Center Display Map Data
10.3.6 Manage Center Map Data
Commercial Vehicle Administration Center CVAC Credentials and Taxes Administration 2.5.1 Manage Commercial Vehicle Trips and Clearances
2.5.2 Obtain Electronic Credential and Tax Filing Payment
2.5.4 Communicate with Other Commercial Vehicle Administration System
2.5.5 Manage Commercial Vehicle and Driver Credentials and Enrollment
2.5.8 Process Data Received from Roadside Facilities
5.4.6 Process CV Violations
7.4.1.1 Process Commercial Vehicle Payments
Connected Vehicle Roadside Equipment RSE Map Management 1.1.2.6 Process Collected Vehicle Safety Data
1.2.5.8 Manage Roadside Parking Facility Communications
1.2.7.7 Process Vehicle Safety and Environmental Data for Output
Maint and Constr Management Center MCM Work Activity Coordination 9.2.1 Schedule M&C Activities
9.2.2 Status Current M&C Activities and Transportation Infrastructure
9.2.4 Manage M&C Map Data
Map Update System Map Management 10.3.1 Collect Geographic Data for Transportation
10.3.2 Maintain Geographic Information System for Transportation
10.3.3 Distribute Map Updates
10.3.4 Coordinate with Other Map Update Systems
Parking Area Equipment Parking Area Management 1.2.5.13 Manage Commercial Vehicle Parking
1.2.5.3 Provide Parking Lot Operator Interface
1.2.5.6 Detect Vehicles in Parking Lot
1.2.5.7 Output Parking Lot Information to Drivers
Personal Information Device Personal Map Management 6.8.1.4 Update Traveler Navigable Map Database
Traveler Support Equipment Traveler Interactive Information 6.3.1 Get Traveler Request
6.3.2 Inform Traveler
6.3.3 Provide Public Traveler Interface
6.3.4 Update Traveler Display Map Data at Kiosk
7.3.4 Provide Remote Terminal Payment Device Interface
7.5.2 Provide Traveler Roadside Payment Device Interface
7.5.4 Provide Traveler Kiosk Payment Device Interface
7.6.6.2 Provide Road Use Charging Services Kiosk Interface
Vehicle OBE Vehicle Map Management 6.7.1.4 Update Vehicle Navigable Map Database

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Center Center This general physical object is used to model core capabilities that are common to any center.
Commercial Vehicle Administration Center Center The 'Commercial Vehicle Administration Center' performs administrative functions supporting credentials, tax, and safety regulations associated with commercial vehicles. It issues credentials, collects fees and taxes, and supports enforcement of credential requirements. It communicates with motor carriers to process credentials applications and collect fuel taxes, weight/distance taxes, and other taxes and fees associated with commercial vehicle operations. It also receives applications for, and issues special Oversize/Overweight and HAZMAT permits in coordination with cognizant authorities. It coordinates with other Commercial Vehicle Administration Centers (in other states/regions) to support nationwide access to credentials and safety information for administration and enforcement functions. It communicates with field equipment to enable credential checking and safety information collection at the roadside. It makes safety information available to qualified stakeholders to identify carriers and drivers that operate unsafely.
Connected Vehicle Roadside Equipment Field 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
Maint and Constr Management Center Center The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems.

The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.)

Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities.
MAP GIS Operator Support The 'Map GIS Operator' represents the person or people that manage GIS updates, supporting import and translation of source data, preparing the base map and information layers, and providing oversight and management for incremental releases of updated map data.
Map Update System Support The 'Map Update System' represents a provider of map databases used to support ITS services. It supports the provision of the map data that are used directly by vehicles (e.g., roadway and intersection geometry data sets), travelers (e.g., navigable maps used for route guidance and display maps used at traveler information points), system operators (e.g., map data used by Traffic Operators to monitor and manage the road network, and map data used by Fleet Managers to manage a vehicle fleet). It may represent a third-party provider or an internal organization that produces map data for agency use. In the latter case, the 'Map Update System' is typically included as part of the center (e.g., a Traffic Management Center) of the infrastructure owner/operator that manages map data. Products may include simple display maps, map data sets that define detailed road network topology and geometry, or full geographic information system databases that are used to support planning and operations.
Other Map Update Systems Support Representing other distinct Map Update Systems, this object is intended to provide a source and destination for ITS information flows between peer map update providers. It enables cooperative information sharing between base map and specialized map providers and any other exchange of geographic information between map data providers.
Other Vehicle OBEs Vehicle 'Other Vehicle OBEs' represents other connected vehicles that are communicating with the host vehicle. This includes all connected motorized vehicles including passenger cars, trucks, and motorcycles and specialty vehicles (e.g., maintenance vehicles, transit vehicles) that also include the basic 'Vehicle OBE' functionality that supports V2V communications. This object provides a source and destination for information transfers between connected vehicles. The host vehicle on-board equipment, represented by the Vehicle OBE physical object, sends information to, and receives information from the Other Vehicle OBEs to model all connected vehicle V2V communications in ARC-IT.
Parking Area Equipment Field 'Parking Area Equipment' provides electronic monitoring and management of parking facilities. It supports an I2V link to the Vehicle that allows electronic collection of parking fees and monitors and controls parking meters that support conventional parking fee collection. It also includes the instrumentation, signs, and other infrastructure that monitors parking lot usage and provides local information about parking availability and other general parking information. The two primary approaches to monitoring parking area usage are sensing vehicles within parking spots or counting vehicles as they come in and as they leave the area. This portion of the functionality must be located in the parking area where it can monitor, classify, and share information with customers and their vehicles. See also the separate 'Parking Management Center' physical object that may be located in a back office, remote from the parking area, which interfaces with the financial infrastructure and broadly disseminates parking information to other operational centers in the region.
Personal Information Device Personal The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with connected vehicle on-board equipment.
Traveler Support Equipment Field 'Traveler Support Equipment' provides access to traveler information at transit stations, transit stops, other fixed sites along travel routes (e.g., rest stops, merchant locations), and major trip generation locations such as special event centers, hotels, office complexes, amusement parks, and theaters. Traveler information access points include kiosks and informational displays supporting varied levels of interaction and information access. At transit stops this might be simple displays providing schedule information and imminent arrival signals. This may be extended to include multi-modal information including traffic conditions and transit schedules to support mode and route selection at major trip generation sites. Personalized route planning and route guidance information can also be provided based on criteria supplied by the traveler. It also supports service enrollment and electronic payment of transit fares. In addition to the traveler information provision, it also enhances security in public areas by supporting traveler activated silent alarms.
Vehicle OBE Vehicle The Vehicle On-Board Equipment (OBE) provides the vehicle-based sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. The Vehicle OBE includes general capabilities that apply to passenger cars, trucks, and motorcycles. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Route guidance capabilities assist in formulation of an optimal route and step by step guidance along the travel route. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

Includes Functional Objects:

Functional Object Description Physical Object
Center Map Management 'Center Map Management' provides the map functionality necessary to support map updates and use within an operational center. It manages map data for the center and provides map data to center applications that use a map. Center
CVAC Credentials and Taxes Administration 'CVAC Credentials and Taxes Administration' issues credentials, collects fees and taxes, and supports enforcement of credential requirements. It manages driver licensing and enrolls carriers in additional CVO programs such as wireless roadside inspection programs. It communicates with the Fleet and Freight Management Centers associated with the motor carriers to process applications and collect fuel taxes, weight/distance taxes, and other taxes and fees associated with commercial vehicle operations. It also receives applications for, and issues special Oversize/Overweight and HAZMAT permits in coordination with other cognizant authorities. It supports user account management and receives and processes requests for review of carrier and driver status. It communicates with peer functional objects in other jurisdictions to exchange credentials database information. Commercial Vehicle Administration Center
Map Management 'Map Management' provides the GIS functionality necessary to support map data creation and management. It provides an operator interface that supports management of the map data and rendering of the maps under operator control and interfaces to external data sources, including the connected vehicle environment. Map Update System
MCM Work Activity Coordination 'MCM Work Activity Coordination' disseminates work activity schedules and current asset restrictions to other agencies. Work schedules are coordinated with operating agencies, factoring in the needs and activities of other agencies and adjacent jurisdictions. Work schedules are also distributed to Transportation Information Centers for dissemination to the traveling public. Maint and Constr Management Center
Parking Area Management 'Parking Area Management' detects and classifies vehicles at parking facility entrances, exits, and other designated locations within the facility. Current parking availability is monitored and used to inform drivers through dynamic message signs/displays so that vehicles are efficiently routed to available spaces. Parking facility information, including current parking rates and directions to entrances and available exits, is also provided to drivers. Parking Area Equipment
Personal Map Management 'Personal Map Management' supports map updates and makes current map and geometry data available to other applications. It manages map data for the device and provides map data to end-user applications that provide location-based services. Personal Information Device
RSE Map Management 'RSE Map Management' provides the map functionality necessary to support map data updates to passing vehicles. It collects current map and geometry data and provides current map and geometry data to connected vehicles. Connected Vehicle Roadside Equipment
Traveler Interactive Information 'Traveler Interactive Information' provides traffic information, road conditions, transit information, yellow pages (traveler services) information, special event information, and other traveler information that is specifically tailored based on the traveler's request and/or previously submitted traveler profile information. It also supports interactive services that support enrollment, account management, and payments for transportation services. The interactive traveler information capability is provided by a public traveler interface, such as a kiosk. Traveler Support Equipment
Vehicle Map Management 'Vehicle Map Management' supports map updates and makes current map and geometry data available to other applications. It manages map data on-board and provides map data to end-user applications that provide location-based services. Vehicle OBE

Includes Information Flows:

Information Flow Description
current infrastructure restrictions Restrictions levied on transportation asset usage based on infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed during maintenance and construction.
intersection geometry The physical geometry of an intersection covering the location and width of each approaching lane, egress lane, and valid paths between approaches and egresses. This flow also defines the location of stop lines, cross walks, specific traffic law restrictions for the intersection (e.g., turning movement restrictions), and other elements that support calculation of a safe and legal vehicle path through the intersection.
map operator input The range of GIS operator inputs that support creation and update of navigable maps and management and distribution of the map data to end users.
map operator updates Interactive display of base map and information layers and associated information that supports map development, management, and dissemination.
map update coordination Exchange of geographic information between map update systems.
map update notification Notification of maintenance, construction, and other activities that will result in medium to long term changes to road location and configuration that may impact navigable maps. This flow includes the timing of the changes and precise enumeration of the location and configuration changes. It also includes updated static speed limits (perhaps other regulatory rules/signage - no U turns, etc.) and default travel times.
map update sharing Peer to peer sharing of map updates. Map updates could include a new underlying static or real-time map or map layer(s) update. Map layers can include highways, major roads, streets, public transport routes, pedestrian routes, topography, points of interest, and regulatory information including turn restrictions and speed limits.
map updates Map update that could include a new underlying static or real-time map or map layer(s) update. Map layers can include highways, major roads, streets, public transport routes, pedestrian routes, topography, points of interest, and regulatory information including turn restrictions and speed limits.
parking facility geometry Precise spatial description of a parking facility that locates each parking space and the ingress and egress routes that are used to travel to and from the spaces.
roadway geometry The physical geometry of a road segment that specifies the location and width of each lane, including normal lanes as well as special lanes for pedestrians and bicycles, transit vehicles, and trains. This flow also may include the curvature, grade, and superelevation or banking of the road segment.
route restrictions Information about routes, road segments, and areas that do not allow the transport of security sensitive hazmat cargoes or include other restrictions (such as height or weight limits).
vehicle location and motion for mapping Vehicles may provide location and motion data independently using wide-area wireless communications to application/service providers who use the provided data to update their maps and maintain real-time traffic and road conditions information sourced from their client-base.
vehicle location and motion for surveillance Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications.
vehicle location data for mapping Aggregate vehicle location data collected to support map data creation and refinement.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
B. Increase the safety of the transportation system for motorized and nonmotorized users; Reduce fatalities and injuries
D. Increase the accessibility and mobility of people and for freight; Reduce congestion
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; Enhance integration and connectivity
G. Promote efficient system management and operation; Improve efficiency
J. Enhance travel and tourism. Support travel and tourism

Associated Objective Categories

Objective Category
Safety: Vehicle Crashes and Fatalities
Travel Weather Management: Disseminating Information
Traveler Information: Trip Planning Tools

Associated Objectives and Performance Measures

Objective Performance Measure
Enhance regional multimodal trip planning tools to X data sources by year Y. The number of data sources providing information for multi-modal trip planning tools.
Increase the ease of use of trip planning tools by X percent by year Y. Trip planning tools ease of use rating.
Increase the number of uses of multimodal trip planning tools by X percent by year Y. Number of uses of trip planning tools.
Reduce crashes at intersections Number of crashes and fatalities at signalized intersections
Reduce crashes at intersections Number of crashes and fatalities at unsignalized intersections
Reduce crashes at intersections Number of crashes and fatalities related to red-light running
Reduce crashes at railroad crossings Number of crashes and fatalities at railroad crossings
Reduce crashes due to red-light running Number of crashes and fatalities related to red-light running
Reduce crashes due to road weather conditions Number of crashes and fatalities related to weather conditions
Reduce crashes due to unexpected congestion Number of crashes and fatalities related to unexpected congestion
Reduce lane departure crashes Number of crashes and fatalities related to inappropriate lane departure, crossing or merging
Reduce secondary crashes Number of secondary crashes
Reduce the number of motorcyclist fatalities by X percent by year Y. Number of motorcyclist fatalities
Reduce the number of pedestrian fatalities by X percent by year Y. Number of pedestrian fatalities
Reduce the number of speeding-related fatalities by X percent by year Y. Number of speeding-related fatalities
Reduce the rate fatalities in the region by X percent by year Y. Rate of fatalities (rate per vehicle miles travelled (VMT))
Reduce the rate of severe injuries in the region by X percent by year Y. Rate of serious injuries (rate per VMT)
Reduce the total number of crashes in the region by X percent by year Y. Total crashes per X VMT.
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y. Total crashes involving bicycles.
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y. Total crashes involving pedestrians.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y. Total fatalities per X VMT.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y. Total severe injuries per X VMT.
Reduce the total number of fatalities in the region by X percent by year Y. Number of fatalities
Reduce the total number of severe injuries in the region by X percent by year Y. Number of serious injuries
Reduce time to alert travelers of travel weather impacts (using variable message signs, 511, road weather information systems, public information broadcasts, the agency's website, Web 2.0 technologies, etc.) by X (time period or percent) in Y years. Time from beginning of weather event to posting of traveler information on (variable message signs, 511, Road Weather Information Systems, public information broadcasts etc.).
Reduce time to alert travelers of travel weather impacts (using variable message signs, 511, road weather information systems, public information broadcasts, the agency's website, Web 2.0 technologies, etc.) by X (time period or percent) in Y years. Time from beginning of weather event to posting of traveler information on agency website.

 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement
01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry. CVAC Credentials and Taxes Administration 05 The center shall provide route restrictions information, including hazmat restrictions, to other centers and agencies for distribution to commercial vehicle operators. These centers and agencies may include commercial fleet and freight management operators, traveler information centers, digital map update providers, and other commercial vehicle administration centers.
Map Management 06 The Center shall collect parking space location information from field parking management systems.
09 The Center shall collect parking space egress/ingress location information from field parking management systems.
14 The Center shall provide the operator with functions necessary to support map rendering.
15 The Center shall provide the operator with functions to support the management of map data.
16 The Center shall provide the operator with mechanisms to control the acquisition of external map data.
17 The Center shall provide the operator with mechanisms to monitor the distribution of map data.
18 The Center shall provide intersection geometry updates to Connected Vehicle Roadside Equipment.
19 The Center shall provide roadway geometry updates to Connected Vehicle Roadside Equipment.
20 The Center shall provide basemap updates to Personal devices.
21 The Center shall provide intersection geometry updates to Vehicles.
22 The Center shall provide basemap updates to Vehicles.
23 The Center shall provide parking facility geometry information to Vehicles.
24 The Center shall provide intersection geometry updates to Personal Devices.
25 The Center shall provide roadway geometry updates to Vehicles.
26 The Center shall provide parking facility geometry information to Connected Vehicle Roadside Equipment.
27 The Center shall provide basemap updates to Connected Vehicle Roadside Equipment.
Parking Area Management 07 The parking element shall provide precise parking egress/ingress location information to Centers.
08 The parking element shall provide precise parking space location information to Centers.
Personal Map Management 01 The Personal Device shall obtain basemap updates from Centers.
02 The Personal Device shall obtain intersection geometry information from Centers.
03 The Personal Device shall make basemap, roadway geometry, intersection geometry and parking facility geometry information available to other personal device applications.
04 Personal devices shall obtain intersection geometry update information from proximate Connected Vehicle Roadside Equipment.
RSE Map Management 03 The field element shall provide roadway geometry update information to proximate Vehicles.
04 The field element shall provide parking facility geometry information to proximate Vehicles.
05 The field element shall provide intersection geometry update information to proximate Vehicles.
06 The field element shall provide basemap update information to proximate Vehicles.
07 The field element shall provide intersection geometry update information to proximate Personal devices.
09 The field element shall provide basemap updates to proximate Vehicles.
10 The field element shall provide intersection geometry updates to proximate Vehicles.
11 The field element shall provide parking facility geometry information to proximate Personal devices.
12 The field element shall provide roadway geometry updates to proximate Vehicles.
Traveler Interactive Information 01 The public interface for travelers shall receive traffic information from a center and present it to the traveler upon request.
09 The public interface for travelers shall base requests from the traveler on the traveler's current location or a specific location identified by the traveler, and filter the provided information accordingly.
Vehicle Map Management 01 The Vehicle shall make basemap, roadway geometry, intersection geometry and parking facility geometry information available to other onboard vehicle applications.
02 The Vehicle shall obtain parking facility geometry information from proximate Connected Vehicle Roadside Equipment.
03 The Vehicle shall obtain roadway geometry update information from proximate Connected Vehicle Roadside Equipment.
04 The Vehicle shall obtain intersection geometry update information from proximate Connected Vehicle Roadside Equipment.
06 The Vehicle shall obtain basemap updates from Centers.
07 The Vehicle shall obtain basemap update information from proximate Connected Vehicle Roadside Equipment.
08 The Vehicle shall obtain roadway geometry information from Centers.
09 The Vehicle shall obtain parking facility geometry information from Centers.
10 The Vehicle shall obtain intersection geometry information from Centers.
02 Mapping operators need real-world observations of roadway geometry, intersection geometry and parking geometry to feed their map update processes. Map Management 01 The Center shall collect Vehicle location information from Vehicles.
07 The Center shall collect vehicle location information from the Connected Vehicle Roadside Equipment.
10 The Center shall use vehicle location information to refine roadway geometry.
11 The Center shall use vehicle location information to refine basemaps.
12 The Center shall use vehicle location information to refine intersection geometry.
RSE Map Management 01 The field element shall collect broadcasted vehicle location and motion information.
02 The field element shall aggregate vehicle location data.
08 The field element shall provide vehicle location data to Centers.
Vehicle Map Management 05 The Vehicle shall provide its location to Centers.
03 Mapping operators need to be able to exchange mapping information (map data and update coordination) with other mapping operators. Center Map Management 01 The Center shall collect updates to basemaps from Map Update Systems .
02 The Center shall collect updates to intersection geometry from Map Update Systems.
03 The Center shall provide roadway geometry updates to Map Update Systems.
04 The Center shall provide intersection geometry updates to Map Update Systems.
Map Management 02 The Center shall collect updates to roadway geometry from other Centers.
03 The Center shall collect road infrastructure restriction information from other Centers.
04 The Center shall collect updates to intersection geometry from other Centers.
05 The Center shall provide basemap updates to other Centers.
08 The Center shall coordinate the contents of map data for distribution with other Centers.
13 The Center shall provide intersection geometry updates to other Centers.
MCM Work Activity Coordination 05 The Center shall provide road infrastructure restriction information to other Centers.

Related Sources

Document Name Version Publication Date
Core System Concept of Operations (ConOps) Final revE 10/24/2011
ITS User Services Document 1/1/2005
Signal Phase & Timing (SPaT) ConOps Draft revD 8/8/2011


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Center Low High Moderate Class 3
Commercial Vehicle Administration Center Low Moderate Low Class 1
Connected Vehicle Roadside Equipment Moderate High Moderate Class 3
Maint and Constr Management Center Low High Moderate Class 3
Map Update System Moderate High Moderate Class 3
Other Map Update Systems Low High Moderate Class 3
Other Vehicle OBEs Not Applicable High Low Class 3
Parking Area Equipment Low High Moderate Class 3
Personal Information Device Low Low Moderate Class 1
Traveler Support Equipment Not Applicable Low Moderate Class 1
Vehicle OBE Moderate High Moderate Class 3



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Center Map Update System map update notification Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Commercial Vehicle Administration Center Map Update System route restrictions Low Moderate Low
Should be public data, so no need for obfuscation. Incorrect route restrictions data will not affect the TIC but will affect the eventual user, and may result in a commercial vehicle being in a place the vehicle is not permitted. This information should not need to be updated often.
Connected Vehicle Roadside Equipment Map Update System vehicle location data for mapping Moderate Moderate Low
Similar to other vehicle location and motion flows. Individual instances of this flow may betray vehicle behavior however, especially if the vehicle ID is included (as the data flow indicates). False information here could lead to incorrect or at least suboptimal map information, which negatively effects much of C-ITS. Individual instances are probably not of tremendous value. More ubiquitous coverage is valuable. So this is LOW for any given instance, but over the broad swath of all vehicles, should provide complete geographic coverage.
Connected Vehicle Roadside Equipment Personal Information Device intersection geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Connected Vehicle Roadside Equipment Vehicle OBE intersection geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Connected Vehicle Roadside Equipment Vehicle OBE map updates Not Applicable High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Connected Vehicle Roadside Equipment Vehicle OBE parking facility geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of parking-related application processes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications.
Connected Vehicle Roadside Equipment Vehicle OBE roadway geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Maint and Constr Management Center Map Update System current infrastructure restrictions Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
MAP GIS Operator Map Update System map operator input Not Applicable High High
System core flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over core equipment Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Map Update System Center intersection geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Map Update System Center map updates Not Applicable High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Map Update System Connected Vehicle Roadside Equipment intersection geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Map Update System Connected Vehicle Roadside Equipment map updates Not Applicable High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Map Update System Connected Vehicle Roadside Equipment parking facility geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of parking-related application processes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications.
Map Update System Connected Vehicle Roadside Equipment roadway geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Map Update System MAP GIS Operator map operator updates Not Applicable Moderate Moderate
System core flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over core equipment Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation. The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take.
Map Update System Other Map Update Systems map update coordination Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Map Update System Parking Area Equipment parking facility geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of parking-related application processes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications.
Map Update System Personal Information Device intersection geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Map Update System Personal Information Device map updates Not Applicable High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Map Update System Traveler Support Equipment map updates Not Applicable High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Map Update System Vehicle OBE intersection geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Map Update System Vehicle OBE map updates Not Applicable High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Map Update System Vehicle OBE parking facility geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of parking-related application processes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications.
Map Update System Vehicle OBE roadway geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Other Map Update Systems Map Update System map update coordination Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Other Vehicle OBEs Vehicle OBE map update sharing Not Applicable High Low
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Map data sharing between vehicles is considered a secondary source of map data, and no applications should rely on it.
Parking Area Equipment Map Update System parking facility geometry Low High Moderate
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Occasional outages of this flow will delay updates and lead to a loss of accurate function of some applications. Depending on the application this could be HIGH.
Vehicle OBE Connected Vehicle Roadside Equipment vehicle location and motion for surveillance Not Applicable Moderate Moderate
This is directly observable data; DISC: WYO believes this to be MODERATE Incorrect information here could lead to the system not functioning properly. If they are unable to properly detect all vehicles crossing the border, it would lead to confusion. There are other factors, such as visual indicators, of vehicles crossing the border, which can be used to help mitigate contradicting information. DISC: THEA believes this should be HIGH: "BSM info needs to be accurate and should not be tampered with" WYO believes this to be HIGH This information must be available in a timely manner for the system to act upon it. The system can operate correctly if some messages are missed, but overall a majority of them should be received.; WYO believes this to be LOW
Vehicle OBE Map Update System vehicle location and motion for mapping Moderate Moderate Low
Similar to other vehicle location and motion flows. Individual instances of this flow may betray vehicle behavior however, especially if the vehicle ID is included (as the data flow indicates). False information here could lead to incorrect or at least suboptimal map information, which negatively effects much of C-ITS. Individual instances are probably not of tremendous value. More ubiquitous coverage is valuable. So this is LOW for any given instance, but over the broad swath of all vehicles, should provide complete geographic coverage.
Vehicle OBE Other Vehicle OBEs map update sharing Not Applicable High Low
Map data intended for general use by any C-ITS component than needs it. No information here includes PII or anything else that, if viewed by someone other than the participant, would lead to harm. Map data is used for a host of application purposes. This widespread use means that any corruption in the data has a widespread and far reaching effect. Map data sharing between vehicles is considered a secondary source of map data, and no applications should rely on it.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name Title Physical Object
CTI 4001 RSU Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589) Connected Vehicle Roadside Equipment




System Requirements

System Requirement Need
001 The system shall collect updates to basemaps from Map Update Systems . 03 Mapping operators need to be able to exchange mapping information (map data and update coordination) with other mapping operators.
002 The system shall collect updates to intersection geometry from Map Update Systems. 03 Mapping operators need to be able to exchange mapping information (map data and update coordination) with other mapping operators.
003 The system shall provide roadway geometry updates to Map Update Systems. 03 Mapping operators need to be able to exchange mapping information (map data and update coordination) with other mapping operators.
004 The system shall provide intersection geometry updates to Map Update Systems. 03 Mapping operators need to be able to exchange mapping information (map data and update coordination) with other mapping operators.
005 The system shall provide route restrictions information, including hazmat restrictions, to other centers and agencies for distribution to commercial vehicle operators. These centers and agencies may include commercial fleet and freight management operato 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
006 The system shall provide road infrastructure restriction information to other Centers. 03 Mapping operators need to be able to exchange mapping information (map data and update coordination) with other mapping operators.
007 The system shall provide precise parking egress/ingress location information to Centers. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
008 The system shall provide precise parking space location information to Centers. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
009 The system shall collect broadcasted vehicle location and motion information. 02 Mapping operators need real-world observations of roadway geometry, intersection geometry and parking geometry to feed their map update processes.
010 The system shall aggregate vehicle location data. 02 Mapping operators need real-world observations of roadway geometry, intersection geometry and parking geometry to feed their map update processes.
011 The system shall provide roadway geometry update information to proximate Vehicles. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
012 The system shall provide parking facility geometry information to proximate Vehicles. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
013 The system shall provide intersection geometry update information to proximate Vehicles. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
014 The system shall provide basemap update information to proximate Vehicles. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
015 The system shall provide intersection geometry update information to proximate Personal devices. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
016 The system shall provide vehicle location data to Centers. 02 Mapping operators need real-world observations of roadway geometry, intersection geometry and parking geometry to feed their map update processes.
017 The system shall provide basemap updates to proximate Vehicles. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
018 The system shall provide intersection geometry updates to proximate Vehicles. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
019 The system shall provide parking facility geometry information to proximate Personal devices. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
020 The system shall provide roadway geometry updates to proximate Vehicles. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
021 The system shall collect Vehicle location information from Vehicles. 02 Mapping operators need real-world observations of roadway geometry, intersection geometry and parking geometry to feed their map update processes.
022 The system shall collect updates to roadway geometry from other Centers. 03 Mapping operators need to be able to exchange mapping information (map data and update coordination) with other mapping operators.
023 The system shall collect road infrastructure restriction information from other Centers. 03 Mapping operators need to be able to exchange mapping information (map data and update coordination) with other mapping operators.
024 The system shall collect updates to intersection geometry from other Centers. 03 Mapping operators need to be able to exchange mapping information (map data and update coordination) with other mapping operators.
025 The system shall provide basemap updates to other Centers. 03 Mapping operators need to be able to exchange mapping information (map data and update coordination) with other mapping operators.
026 The system shall collect parking space location information from field parking management systems. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
027 The system shall collect vehicle location information from the Connected Vehicle Roadside Equipment. 02 Mapping operators need real-world observations of roadway geometry, intersection geometry and parking geometry to feed their map update processes.
028 The system shall coordinate the contents of map data for distribution with other Centers. 03 Mapping operators need to be able to exchange mapping information (map data and update coordination) with other mapping operators.
029 The system shall collect parking space egress/ingress location information from field parking management systems. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
030 The system shall use vehicle location information to refine roadway geometry. 02 Mapping operators need real-world observations of roadway geometry, intersection geometry and parking geometry to feed their map update processes.
031 The system shall use vehicle location information to refine basemaps. 02 Mapping operators need real-world observations of roadway geometry, intersection geometry and parking geometry to feed their map update processes.
032 The system shall use vehicle location information to refine intersection geometry. 02 Mapping operators need real-world observations of roadway geometry, intersection geometry and parking geometry to feed their map update processes.
033 The system shall provide intersection geometry updates to other Centers. 03 Mapping operators need to be able to exchange mapping information (map data and update coordination) with other mapping operators.
034 The system shall provide the operator with functions necessary to support map rendering. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
035 The system shall provide the operator with functions to support the management of map data. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
036 The system shall provide the operator with mechanisms to control the acquisition of external map data. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
037 The system shall provide the operator with mechanisms to monitor the distribution of map data. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
038 The system shall provide intersection geometry updates to Connected Vehicle Roadside Equipment. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
039 The system shall provide roadway geometry updates to Connected Vehicle Roadside Equipment. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
040 The system shall provide basemap updates to Personal devices. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
041 The system shall provide intersection geometry updates to Vehicles. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
042 The system shall provide basemap updates to Vehicles. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
043 The system shall provide parking facility geometry information to Vehicles. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
044 The system shall provide intersection geometry updates to Personal Devices. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
045 The system shall provide roadway geometry updates to Vehicles. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
046 The system shall provide parking facility geometry information to Connected Vehicle Roadside Equipment. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
047 The system shall provide basemap updates to Connected Vehicle Roadside Equipment. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
048 The system shall obtain basemap updates from Centers. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
049 The system shall obtain intersection geometry information from Centers. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
050 The system shall make basemap, roadway geometry, intersection geometry and parking facility geometry information available to other personal device applications. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
051 The system shall obtain intersection geometry update information from proximate Connected Vehicle Roadside Equipment. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
052 The system shall make basemap, roadway geometry, intersection geometry and parking facility geometry information available to other onboard vehicle applications. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
053 The system shall obtain parking facility geometry information from proximate Connected Vehicle Roadside Equipment. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
054 The system shall obtain roadway geometry update information from proximate Connected Vehicle Roadside Equipment. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
055 The system shall provide its location to Centers. 02 Mapping operators need real-world observations of roadway geometry, intersection geometry and parking geometry to feed their map update processes.
056 The system shall obtain basemap update information from proximate Connected Vehicle Roadside Equipment. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
057 The system shall obtain roadway geometry information from Centers. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.
058 The system shall obtain parking facility geometry information from Centers. 01 System operators, vehicle operators and PID users need map data that is accurate and consistent between one another. This includes roadway maps and geometry, intersection maps and geometry and parking facility maps and geometry.