Type: Resource

ITS Field Component Development System

Overview

The system used in a backoffice environment to develop and test the ITS field component of the application.

This resource is included in the following applications:

Coordination

Source Coordination Destination
Border Inspection Provider Operates ITS Field Component Development System
Border Inspection Provider Owns ITS Field Component Development System
CVCE Citation and Accident Electronic Recording Provider Operates ITS Field Component Development System
CVCE Citation and Accident Electronic Recording Provider Owns ITS Field Component Development System
CVCE Electronic Screening Provider Operates ITS Field Component Development System
CVCE Electronic Screening Provider Owns ITS Field Component Development System
CVCE International Border Crossing Provider Operates ITS Field Component Development System
CVCE International Border Crossing Provider Owns ITS Field Component Development System
CVCE Safety and Security Inspection Provider Operates ITS Field Component Development System
CVCE Safety and Security Inspection Provider Owns ITS Field Component Development System
ITS Field Component Development System Application Installation Data ITS Field Component Installation System
ITS Field Component Development System Application Maintenance Data ITS Field Component Maintenance System
ITS Field Component Development System Application Performance Data ITS Field Component Maintenance System
ITS Field Component Maintenance System Application Performance Data ITS Field Component Development System
Parking Electronic Payment Installer Operates ITS Field Component Development System
Parking Electronic Payment Installer Owns ITS Field Component Development System
Parking Electronic Payment Provider Operates ITS Field Component Development System
Parking Electronic Payment Provider Owns ITS Field Component Development System
Parking Management Provider Operates ITS Field Component Development System
Parking Management Provider Owns ITS Field Component Development System
Roadway Advanced Rail Crossing Provider Operates ITS Field Component Development System
Roadway Advanced Rail Crossing Provider Owns ITS Field Component Development System
Roadway Basic Surveillance Provider Operates ITS Field Component Development System
Roadway Basic Surveillance Provider Owns ITS Field Component Development System
Roadway Communications Support Provider Operates ITS Field Component Development System
Roadway Communications Support Provider Owns ITS Field Component Development System
Roadway Dynamic Lane Management and Shoulder Use Provider Operates ITS Field Component Development System
Roadway Dynamic Lane Management and Shoulder Use Provider Owns ITS Field Component Development System
Roadway Emissions Monitoring Provider Operates ITS Field Component Development System
Roadway Emissions Monitoring Provider Owns ITS Field Component Development System
Roadway Environmental Monitoring Provider Operates ITS Field Component Development System
Roadway Environmental Monitoring Provider Owns ITS Field Component Development System
Roadway Lighting System Control Provider Operates ITS Field Component Development System
Roadway Lighting System Control Provider Owns ITS Field Component Development System
Roadway Payment Support Provider Operates ITS Field Component Development System
Roadway Payment Support Provider Owns ITS Field Component Development System
Roadway Pedestrian Crossing Safety Provider Operates ITS Field Component Development System
Roadway Pedestrian Crossing Safety Provider Owns ITS Field Component Development System
Roadway Signal Control Provider Operates ITS Field Component Development System
Roadway Signal Control Provider Owns ITS Field Component Development System
Roadway Speed Monitoring and Warning Provider Operates ITS Field Component Development System
Roadway Speed Monitoring and Warning Provider Owns ITS Field Component Development System
Roadway Toll Collection Support Provider Operates ITS Field Component Development System
Roadway Toll Collection Support Provider Owns ITS Field Component Development System
Roadway Traffic Gap Assist Provider Operates ITS Field Component Development System
Roadway Traffic Gap Assist Provider Owns ITS Field Component Development System
Roadway Traffic Information Dissemination Provider Operates ITS Field Component Development System
Roadway Traffic Information Dissemination Provider Owns ITS Field Component Development System
Roadway Traffic Metering Provider Operates ITS Field Component Development System
Roadway Traffic Metering Provider Owns ITS Field Component Development System
Roadway Variable Speed Limits Maintainer Operates ITS Field Component Development System
Roadway Variable Speed Limits Maintainer Owns ITS Field Component Development System
Roadway Variable Speed Limits Provider Operates ITS Field Component Development System
Roadway Variable Speed Limits Provider Owns ITS Field Component Development System
Roadway Warning Provider Operates ITS Field Component Development System
Roadway Warning Provider Owns ITS Field Component Development System
Roadway Work Zone Safety Provider Operates ITS Field Component Development System
Roadway Work Zone Safety Provider Owns ITS Field Component Development System
Roadway Work Zone Traffic Control Provider Operates ITS Field Component Development System
Roadway Work Zone Traffic Control Provider Owns ITS Field Component Development System
Terminal Management Provider Operates ITS Field Component Development System
Terminal Management Provider Owns ITS Field Component Development System

Security

Interfaces Diagram

Interfaces diagram

Alternative Configurations

Four diagrams below illustrate four different implementations that may be represented by the Vehicle On-Board Equipment: 1) Vehicle Awareness Device, 2) Aftermarket Device, 3) Retrofit Device, or 4) Integrated System. Each diagram shows the subset of interfaces from CVRIA that are relevant to that particular implementation. Note that a V2V safety application is shown, but the four implementation options also provide varied support for other connected vehicle applications. Map provider shown as it is a likely interface for many safety applications, and the different points at which the map hooks in are illustrative of changes in necessary relationships. A fifth diagram covers a scenario where an aftermarket carry-in device is carried in to a vehicle that is already equipped with one of the Vehicle OBE implementations.

1. Vehicle Awareness Device – This is an aftermarket electronic device, installed in a vehicle without connection to vehicle systems, that is only capable of sending the basic safety message over short range communications. Vehicle awareness devices do not issue audible or visual warnings, alerts, or guidance to the driver of the vehicle.

2. Aftermarket Device – This is an aftermarket electronic device, installed in a vehicle, and capable of sending and receiving messages over a wireless communications link. The self-contained device includes GPS, runs connected vehicle applications, and includes an integrated driver interface that issues audible or visual warnings, alerts, and guidance to the driver of the vehicle. The aftermarket device may or may not have access to some vehicle system status.

3. Retrofit Device – This is an OEM authorized electronic device installed in vehicles by an OEM authorized service provider, at a service facility after the vehicle has been built. This type of device provides two-way communications and is connected to a vehicle databus. Depending on implementation, the device may include an integrated driver interface and GPS or integrate with modules on the vehicle databus that provide these services. Depending on implementation, it may only support some of the connected vehicle applications identified in CVRIA and potentially support additional applications that are not identified in CVRIA.

4. Integrated System – This is a system of one or more electronic devices integrated into vehicles during vehicle production. The Integrated System is connected to proprietary data busses to share information with other on-board systems. The Integrated System may be distributed across multiple subsystems and may be configured to support some of the connected vehicle applications identified in CVRIA and potentially support additional applications that are not identified in CVRIA.



In retrofit and integrated implementations, the Vehicle OBE interfaces to other on-board systems through a vehicle databus (e.g., CAN). Represented in CVRIA as the Vehicle Databus, this interface provides access to on-board sensors, monitoring and control systems, and information systems that support connected vehicle applications. The vehicle databus may also be the source for GPS location and time, map data that supports connected vehicle applications, and the access point for the vehicle's driver-vehicle interface.

5. A fifth diagram covers a scenario where an aftermarket carry-in device is carried in to a vehicle that is already equipped with one of the Vehicle OBE implementations. In this scenario, we have two different devices with possibly two different radios and two different user interfaces that must be coordinated to avoid interference or conflicts.