Type: Environmental

Groups:
  • AERIS/ Sustainable Travel
Diagrams are based on the most recently available application concepts that the CVRIA team has access to, and do not necessarily reflect prototypes or other in-development activities.

Eco-Transit Signal Priority

The Eco-Transit Signal Priority application allows a transit vehicle approaching a signalized intersection to request signal priority. The application considers a host of relevant parameters to determine whether signal priority should be granted. These parameters include the vehicle's location, speed, vehicle powertrain type, mass, grade, and associated modal GHG and criteria air pollutant emissions. Information collected from other vehicles approaching the intersection, a transit vehicle's adherence to its schedule, or the number of passengers on the transit vehicle may also be considered in granting priority. If priority is granted, the traffic signal holds the green on the approach until the transit vehicle clears the intersection.

Enterprise

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
The enterprise diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagrams: Installation Operations Maintenance Certification
PNG Diagrams: Installation Operations Maintenance Certification


Display Legend in SVG or PNG

Business Interaction Matrix:

Eco-Transit Signal Priority Operations Stage
Roadway OwnerRSE OwnerRSE OperatorITS Roadway Equipment OwnerITS Roadway OperatorTransit Vehicle OperatorTraffic ManagerRSE Intersection Management ProviderTransit Vehicle Signal Priority ProviderTransit Vehicle Passenger Counting ProviderTransit Vehicle Emissions Monitoring ProviderTransit Fleet Manager
Roadway OwnerService Delivery Agreement
RSE OwnerService Delivery AgreementOperations AgreementInformation Provision AgreementInformation Exchange and Action AgreementApplication Usage AgreementInformation Provision and Action Agreement
RSE OperatorOperations Agreement
ITS Roadway Equipment OwnerInformation Provision AgreementOperations AgreementInformation Exchange Agreement
ITS Roadway OperatorOperations AgreementExpectation of Information Provision
Transit Vehicle OperatorExpectation of Information ProvisionVehicle Operating Agreement
Traffic ManagerInformation Exchange and Action AgreementInformation Exchange AgreementInformation Exchange and Action Agreement
RSE Intersection Management ProviderApplication Usage Agreement
Transit Vehicle Signal Priority ProviderApplication Usage Agreement
Transit Vehicle Passenger Counting ProviderApplication Usage Agreement
Transit Vehicle Emissions Monitoring ProviderApplication Usage Agreement
Transit Fleet ManagerInformation Provision and Action AgreementVehicle Operating AgreementInformation Exchange and Action AgreementApplication Usage AgreementApplication Usage AgreementApplication Usage Agreement

Includes Enterprise Objects:

Enterprise Object Description
Application Certification Entity The body that determines whether an application may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with application type. For example, applications with human safety component (crash avoidance, movement assistance etc.) may have stringent requirements and extensive testing in a variety of conditions, while applications that provide strictly mobility functionality may have far less testing requirements; possibly as little as just making sure the application doesn't interfere with any other applications.
Device Certification Entity The body that determines whether a device may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device type.
Federal Regulatory Federal regulatory bodies that have legal authority to control and/or provide input to policies regulating transportation infrastructure and operations. This includes entities such as the Federal Communications Commission and US Department of Transportation.
ITS Certification Entity The body that determines whether an ITS device or application may be deployed and operated in the transportation environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device and application type. Typically not a formal body, assigned on a project-by-project basis depending on the type of infrastructure involved. Since ITS projects are locally-focused (typically state or smaller), the entities that are part of this body are typically those with operational jurisdiction where the ITS is installed (e.g., state or local DOTs, state or local maintenance managers etc.)
ITS Roadway Equipment Owner The entity that owns the Roadway ITS equipment.
ITS Roadway Operator The entity that operates the Roadway ITS equipment.
Roadway Owner The owner of the roadway proximate to which roadside equipment will be/is installed.
Roadway Signal Control Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Signal Control Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Signal Control Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
RSE Deployer The entity responsible for the deployment, operations and maintenance of roadside equipment.
RSE Intersection Management Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Intersection Management Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Intersection Management Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
RSE Operator The entity that operates roadside equipment in the transportation environment.
RSE Owner The owner of roadside equipment.
RSE Provider The "RSE Provider" is the entity that develops and (presumably) sells roadside equipment to other entities for deployment and research.
State Regulatory State regulatory bodies that have legal authority to control and/or provide input to policies regulating vehicles, transportation infrastructure and operations. This includes entities like Departments of Motor Vehicles, property tax authorities and tolling agencies.
TMC Multi-Modal Coordination Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Multi-Modal Coordination Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Multi-Modal Coordination Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
TMC Signal Control Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Signal Control Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Signal Control Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Traffic Manager The entity responsible for the management of traffic, both freeway and arterial.
Transit Center Emissions Monitoring Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Transit Center Emissions Monitoring Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Transit Center Emissions Monitoring Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Transit Center Passenger Counting Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Transit Center Passenger Counting Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Transit Center Passenger Counting Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Transit Center Priority Management Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Transit Center Priority Management Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Transit Center Priority Management Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Transit Fleet Manager The agency or organization that operates transit vehicles. This includes administration, routing, driver instruction, maintenance and any other responsibilities associated with the operations and maintenance of a transit system.
Transit Vehicle Emissions Monitoring Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Transit Vehicle Emissions Monitoring Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Transit Vehicle Emissions Monitoring Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Transit Vehicle Manufacturer The entity which builds transit vehicles. This entity is complementary to the Vehicle Manufacturer entity in that it represents those aspects of vehicle manufacture which are unique to transit vehicles.
Transit Vehicle OBE Manufacturer The Transit Vehicle OBE Manufacturer is the provider of the transit vehicle on-board equipment. This entity may design and build the OBE, or may integrate other components to form the OBE, or may use some combination of approaches to provide the on-board equipment. Since the OBE could be aftermarket, retrofit, built-in or nomadic, this entity is the one that builds whatever that-is. In some cases it may be a smart phone manufacturer, or in others a top tier parts supplier, or any other entity in the production chain, depending on the device and commercial vehicle in question.
Transit Vehicle Operator The 'Transit Vehicle Operator' represents the person that receives and provides additional information that is specific to operating the ITS functions in all types of transit vehicles. The information received by the operator would include status of on-board systems. Additional information received depends upon the type of transit vehicle. In the case of fixed route transit vehicles, the Transit Vehicle Operator would receive operator instructions that might include actions to take to correct schedule deviations. In the case of flexible fixed routes and demand response routes the information would also include dynamic routing or passenger pickup information.
Transit Vehicle Passenger Counting Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Transit Vehicle Passenger Counting Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Transit Vehicle Passenger Counting Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Transit Vehicle Signal Priority Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Transit Vehicle Signal Priority Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Transit Vehicle Signal Priority Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.

Includes Resources:

Resource Description
Application Component Certification Requirements The requirements that define the functionality, performance and operational environment of an application component. Certification Requirements must be met in order for an application to be installed in the CVE.
Backoffice Service Development System The systems used to develop backoffice (center) hardware and software components of applications.
Backoffice Service Installation System The systems used to install and configure backoffice (center) hardware and software components.
Backoffice Service Maintenance System The systems used to maintain and upgrade backoffice (center) hardware and software components.
Device Certification Requirements The requirements that define the functionality, performance and operational environment of a connected vehicle device. Certification Requirements must be met in order for the device to be granted the credentials necessary to operate in the Connected Vehicle Environment.
Field Component Development System The system used in a backoffice environment to develop and test the field component of the application.
Field Component Installation System The system used to install a field component of a connected vehicle application.
Field Component Maintenance System The system used to install and configure changes and updates to the field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
ITS Certification Requirements The requirements that define the functionality, performance and operational environment of an ITS device or ITS application. Applicability varies with jurisdictions, but typically devices and applications must meet pre-defined acceptance criteria prior to usage in the transportation environment.
ITS Field Component Development System The system used in a backoffice environment to develop and test the ITS field component of the application.
ITS Field Component Installation System The system used to install a field component of a connected vehicle application.
ITS Field Component Maintenance System The system used to install and configure changes and updates to the ITS field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
ITS Roadway Equipment 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway itself. In CVRIA, this physical object represents all of the other ITS field equipment that interfaces with and supports the Connected Vehicle Roadside Equipment (RSE). This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Mobile Component Development System The system used in a backoffice environment to develop and test the mobile component of the application.
Mobile Component Installation System The system that interacts with the Vehicle OBE other mobile device and installs the mobile component of the application.
Mobile Component Maintenance System The system used to configure changes and updates to the mobile component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
Roadside Equipment 'Roadside Equipment' (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.
Roadway Signal Control "Roadway Signal Control" includes the field elements that monitor and control signalized intersections. It includes the traffic signal controllers, detectors, conflict monitors, signal heads, and other ancillary equipment that supports traffic signal control. It also includes field masters, and equipment that supports communications with a central monitoring and/or control system, as applicable. The communications link supports upload and download of signal timings and other parameters and reporting of current intersection status. It represents the field equipment used in all levels of traffic signal control from basic actuated systems that operate on fixed timing plans through adaptive systems. It also supports all signalized intersection configurations, including those that accommodate pedestrians. In advanced, future implementations, environmental data may be monitored and used to support dilemma zone processing and other aspects of signal control that are sensitive to local environmental conditions.
RSE Development System The system used in a backoffice environment to develop and test the roadside equipment.
RSE Installation System The system used to install and configure the roadside equipment.
RSE Intersection Management "RSE Intersection Management" uses short range communications to support connected vehicle applications that manage signalized intersections. It communicates with approaching vehicles and ITS infrastructure (e.g., the traffic signal controller) to enhance traffic signal operations. Coordination with the ITS infrastructure also supports conflict monitoring to ensure the RSE output and traffic signal control output are consistent and degrade in a fail safe manner.
RSE Maintenance System The system used to configure changes and updates to the roadside equipment. This system is capable of acquiring and reporting diagnostic information about the RSE's configuration and performance.
TMC Multi-Modal Coordination "TMC Multi-Modal Coordination" supports center-to-center coordination between the Traffic Management and Transit Management Centers. It monitors transit operations and provides traffic signal priority for transit vehicles on request from the Transit Management Center.
TMC Signal Control "TMC Signal Control" provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single traffic management center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc.
Traffic Management Center The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Transit Center Emissions Monitoring "Transit Center Emissions Monitoring" collects and/or estimates current transit fleet emissions and forecasts future fleet emissions. The collected, estimated, and forecast emissions is monitored and forwarded to other agencies to more effectively manage transit operations to reduce emissions.
Transit Center Passenger Counting "Transit Center Passenger Counting" receives and processes transit vehicle loading data using two-way communications from equipped transit vehicles.
Transit Center Priority Management "Transit Center Priority Management" monitors transit schedule performance and generates requests for transit priority on routes and at certain intersections. It may coordinate with the Traffic Management Center to provide transit priority along the selected route, including allocation of dynamic lanes and granting signal priority. It also coordinates with the Transit Vehicle OBE to monitor and manage local transit signal priority requests at individual intersections.
Transit Management Center The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces allow for communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
Transit Vehicle The vehicle that provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. This includes buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles.
Transit Vehicle Databus The 'Transit Vehicle Databus' represents the vehicle databus that interfaces with on-board equipment on a transit vehicle. It is a specialized and extended form of the Vehicle Databus that is subject to different vehicle databus standards and hosts a broad range of components that are unique to a transit vehicle including the farebox and associated electronics, passenger counters, and transit security systems. As a specialized form of the Vehicle Databus, it also provides access to the general-purpose sensors (e.g., radars, cameras), GPS, drive train monitoring and control systems, and vehicle safety features that support connected vehicle applications. The Transit Vehicle may represent a bus, paratransit vehicle, light rail vehicle, or other vehicle designed to carry passengers. In CVRIA, the 'Transit Vehicle Databus' is used to represent the onboard interactions between the Transit Vehicle OBE and the other systems included in a host transit vehicle.
Transit Vehicle Emissions Monitoring "Transit Vehicle Emissions Monitoring" directly measures or estimates vehicle emissions and provides current and average emissions measures to the Transit Management Center.
Transit Vehicle OBE The Transit Vehicle On-Board equipment (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.
Transit Vehicle Passenger Counting "Transit Vehicle Passenger Counting" collects transit vehicle loading data and makes it available to the center.
Transit Vehicle Signal Priority "Transit Vehicle Signal Priority" provides the capability for transit vehicles to determine eligibility for priority and request signal priority at signalized intersections, ramps, and interchanges through short range communication with traffic control equipment at the roadside.

Includes Roles:

Role Description
Certifies An Enterprise verifies that a target Resource meets relevant performance, functional, environmental and quality requirements.
Constrains A Resource or Enterprise applies requirements, constraints and associated tests to another Resource.
Installs An Enterprise performs the initial delivery, integration and configuration of the target Resource.
Maintains An Enterprise administers the hardware and software that comprise the target Resource.
Member An Enterprise is part of another larger, target Enterprise.
Operates An Enterprise controls the functionality and state of the target Resource. An Enterprise that Operates a resource is considered Responsible.
Owns An Enterprise has financial ownership and control over the Resource. An Enterprise that Owns a resource is considered Accountable.

Includes Coordination:

Coordination Type Description
Application Installation Data Information Sharing Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow.
Application Interface Specification Agreement The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Application Maintenance Data Information Sharing Data used to facilitate the upgrade, patching and general health maintenance of an application component.
Application Performance Data Information Sharing Data used to characterize application performance, including such measures as availability, known errors and known uses.
Application Procurement Agreement Agreement An agreement whereupon one entity provides a copy of an application component to another entity. This component is capable of being installed and functioning, according to its requirements that passed through the application's certification process.
Application Usage Agreement Agreement An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Backoffice Component Installation Agreement Agreement An agreement that grants one party permission to install a backoffice application component on a center-based device controlled by the other party.
Device Placement and Operations Agreement Agreement An agreement that enables the controller of a physical device to install it (so as to make it operational) at a fixed location controlled by another entity.
Expectation of Information Provision Expectation An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient.
Field Component Installation Agreement Agreement An agreement that grants one party permission to install a field application component on a roadside device controlled by the other party.
Includes Includes Indicates that one component is entirely contained within another component.
Information Exchange Agreement Agreement An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Information Exchange and Action Agreement Agreement An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Information Provision Agreement Agreement An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Information Provision and Action Agreement Agreement An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Installation Agreement Agreement An agreement whereupon one entity installs an application component on a device controlled by another entity.
Maintenance Agreement Agreement An agreement in which one entity maintains the operational status of a system under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Maintenance Data Exchange Agreement Agreement An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Mobile Component Installation Agreement Agreement An agreement whereupon the controller of OBE gives another party permission to install, configure and make operational a component that enables the mobile portion of an application.
Mobile Component License Agreement Agreement An end-user license agreement allowing the operator of the mobile device to use the mobile application component that is part of the application in question.
Operations Agreement Agreement An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
RSE Deployment Agreement Agreement Agreement to install, configure and make operational roadside equipment, between the provider of that equipment and the entity that controls access to the roadside. May define locations, expectation of power provision, backhaul responsibility and installation restrictions.
RSE Installation Data Information Sharing Data necessary to configure and make RSE operational. Uni-directional.
RSE Maintenance Data Information Sharing Data necessary to modify the operational configuration of RSE; assumes RSE is already configured. Uni-directional.
RSE Performance Data Information Sharing Data that includes metrics of RSE performance. Could include fields such as uptime, packets received/transmitted, distance vector from which packets received, as well as application-specific performance measures.
RSE Procurement Agreement Agreement An agreement whereupon one entity provides roadside equipment to another entity. The RSE is capable of being installed and functioning, according to its requirements that passed through the device's certification process.
Service Delivery Agreement Agreement A relationship where one party agrees to provide a service to the other party. This agreement may specify the expected performance of this service in terms of availability and/or actions/time-type performance specifications.
Vehicle Data Access Agreement Agreement An agreement whereby the party that controls access to on-board vehicle data grants another party the right and ability to access that data. Includes the conditions under which data may be accessed, and specifies the mechanisms, including physical and functional access methods, data formats and any other considerations necessary for the accessing party to acquire data. May also include caveats regarding responsibility for data quality and responsibility for use of the data.
Vehicle Operating Agreement Agreement An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle.
Vehicle Procurement Agreement Agreement The exchange of a vehicle for compensation. One entity purchases the vehicle from the other.
Warranty Agreement A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance over time of an application component.

Functional

Includes Processes:

Level Name Type Allocated to Application Object
1.1 Provide Traffic Surveillance Collection
1.1.1 Process Sensor Data Collection
1.1.1.1 Process Traffic Sensor Data Pspec - Roadway Signal Control
1.1.1.6 Collect Vehicle Roadside Safety Data Pspec - RSE Intersection Management
1.1.2 Process and Store Traffic Data Collection
1.1.2.2 Process Traffic Data Pspec - TMC Signal Control
- TMC Multi-Modal Coordination
1.1.2.6 Process Collected Vehicle Safety Data Pspec - RSE Intersection Management
1.2 Provide Device Control Collection
1.2.1 Select Strategy Pspec - TMC Signal Control
1.2.2 Determine Road and Freeway State Collection
1.2.2.2 Determine Indicator State for Road Management Pspec - TMC Signal Control
- TMC Multi-Modal Coordination
1.2.4 Output Control Data Collection
1.2.4.1 Output Control Data for Roads Pspec - TMC Signal Control
1.2.7 Provide Roadside Control Facilities Collection
1.2.7.1 Process Indicator Output Data for Roads Pspec - Roadway Signal Control
1.2.7.2 Monitor Roadside Equipment Operation Pspec - Roadway Signal Control
1.2.7.5 Process Indicator Output Data for Freeways Pspec - Roadway Signal Control
1.2.7.7 Process Vehicle Safety and Environmental Data for Output Pspec - RSE Intersection Management
1.2.7.14 Manage Local Signal Priority Requests Pspec - RSE Intersection Management
1.2.8 Collect Traffic Field Equipment Fault Data Pspec - TMC Signal Control
4.1 Operate Transit Vehicles and Facilities Collection
4.1.1 Process On-Board Systems Data Pspec - Transit Vehicle Signal Priority
- Transit Vehicle Passenger Counting
- Transit Vehicle Emissions Monitoring
4.1.2 Determine Transit Vehicle Service Status Pspec - Transit Vehicle Signal Priority
- Transit Vehicle Passenger Counting
- Transit Vehicle Emissions Monitoring
4.1.3 Provide Transit Vehicle Location Data Pspec - Transit Vehicle Signal Priority
4.1.4 Manage Transit Vehicle Deviations Pspec - Transit Center Priority Management
- Transit Center Emissions Monitoring
- Transit Center Passenger Counting
4.1.5 Provide Transit Vehicle Status and Probe Information Pspec - Transit Center Priority Management
- Transit Center Emissions Monitoring
- Transit Center Passenger Counting
4.1.6 Manage Transit Vehicle Operations Pspec - Transit Center Priority Management
- Transit Center Emissions Monitoring
- Transit Center Passenger Counting

Includes Data Flows:

Source Pspec Data Flow Destination Pspec
Collect Traffic Field Equipment Fault Data indicator_fault_state Select Strategy
Collect Vehicle Roadside Safety Data vehicle_safety_input_data Process Collected Vehicle Safety Data
Determine Indicator State for Road Management transit_road_priority_given Manage Transit Vehicle Deviations
Determine Indicator State for Road Management indicator_road_requested_state Output Control Data for Roads
Determine Transit Vehicle Service Status transit_vehicle_roadway_priorities Manage Local Signal Priority Requests
Determine Transit Vehicle Service Status transit_vehicle_deviations_from_schedule Manage Transit Vehicle Deviations
Determine Transit Vehicle Service Status transit_vehicle_passenger_connection_request Manage Transit Vehicle Deviations
Determine Transit Vehicle Service Status transit_vehicle_connection_request_mode Manage Transit Vehicle Deviations
Determine Transit Vehicle Service Status transit_service_status Manage Transit Vehicle Operations
Determine Transit Vehicle Service Status transit_vehicle_schedule_deviation Manage Transit Vehicle Operations
Determine Transit Vehicle Service Status transit_vehicle_eta Manage Transit Vehicle Operations
Determine Transit Vehicle Service Status transit_vehicle_service_update Manage Transit Vehicle Operations
Manage Local Signal Priority Requests indicator_monitoring_suspend_for_priority Monitor Roadside Equipment Operation
Manage Local Signal Priority Requests indicator_priority_for_highways Process Indicator Output Data for Freeways
Manage Local Signal Priority Requests indicator_priority_for_roads Process Indicator Output Data for Roads
Manage Transit Vehicle Deviations transit_road_overall_priority Determine Indicator State for Road Management
Manage Transit Vehicle Deviations signal_priority_rules Determine Transit Vehicle Service Status
Manage Transit Vehicle Deviations transit_vehicle_connection_response Determine Transit Vehicle Service Status
Manage Transit Vehicle Deviations transit_vehicle_connection_response_constraints Determine Transit Vehicle Service Status
Manage Transit Vehicle Deviations transit_vehicle_connection_instructions Determine Transit Vehicle Service Status
Manage Transit Vehicle Deviations approved_corrective_plan Determine Transit Vehicle Service Status
Manage Transit Vehicle Deviations transit_stop_requests_from_center Determine Transit Vehicle Service Status
Manage Transit Vehicle Deviations transit_vehicle_deviation_update Manage Transit Vehicle Operations
Manage Transit Vehicle Operations schedule_change_for_connection_protection Determine Transit Vehicle Service Status
Manage Transit Vehicle Operations road_network_info_for_transit Determine Transit Vehicle Service Status
Manage Transit Vehicle Operations transit_vehicle_service_enable Determine Transit Vehicle Service Status
Manage Transit Vehicle Operations operations_input_for_deviations Manage Transit Vehicle Deviations
Manage Transit Vehicle Operations transit_vehicle_collected_maintenance_data_request Process On-Board Systems Data
Manage Transit Vehicle Operations transit_vehicle_information Provide Transit Vehicle Status and Probe Information
Monitor Roadside Equipment Operation indicator_status_from_signals Collect Traffic Field Equipment Fault Data
Monitor Roadside Equipment Operation indicator_status_from_traffic_meters Collect Traffic Field Equipment Fault Data
Monitor Roadside Equipment Operation indicator_faults_from_signals Collect Traffic Field Equipment Fault Data
Output Control Data for Roads indicator_status_for_roads_from_center Collect Traffic Field Equipment Fault Data
Output Control Data for Roads indicator_control_configuration_data_for_signal_control Monitor Roadside Equipment Operation
Output Control Data for Roads reversible_lane_control_for_roads Process Indicator Output Data for Roads
Output Control Data for Roads indicator_control_data_for_signal_control Process Indicator Output Data for Roads
Output Control Data for Roads indicator_input_state_for_roads Select Strategy
Process Collected Vehicle Safety Data vehicle_traffic_data_for_freeways Process Indicator Output Data for Freeways
Process Collected Vehicle Safety Data vehicle_traffic_data_for_roads Process Indicator Output Data for Roads
Process Collected Vehicle Safety Data vehicle_safety_data_indication Process Vehicle Safety and Environmental Data for Output
Process Collected Vehicle Safety Data roadway_geometry_location_data Process Vehicle Safety and Environmental Data for Output
Process Collected Vehicle Safety Data roadway_intersection_geometry_data Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Freeways reversible_lane_control_device_status_from_highways Collect Traffic Field Equipment Fault Data
Process Indicator Output Data for Freeways indicator_response_data_for_highways Monitor Roadside Equipment Operation
Process Indicator Output Data for Freeways traffic_metering_data_for_roadside Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads reversible_lane_control_device_status_from_roads Collect Traffic Field Equipment Fault Data
Process Indicator Output Data for Roads indicator_response_data_for_roads Monitor Roadside Equipment Operation
Process Indicator Output Data for Roads indicator_input_data_from_signals Output Control Data for Roads
Process Indicator Output Data for Roads roadside_signal_phase_indication Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads roadside_signal_phase_timing Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads roadside_signal_phase_response_state Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads roadside_signal_priority_preempt Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads signal_preemption_override Select Strategy
Process Indicator Output Data for Roads signal_priority_override Select Strategy
Process On-Board Systems Data transit_vehicle_arrival_times Determine Transit Vehicle Service Status
Process On-Board Systems Data transit_vehicle_collected_maintenance_data Manage Transit Vehicle Operations
Process On-Board Systems Data transit_vehicle_passenger_loading Manage Transit Vehicle Operations
Process On-Board Systems Data transit_vehicle_running_times Manage Transit Vehicle Operations
Process On-Board Systems Data transit_vehicle_on_board_data Provide Transit Vehicle Location Data
Process On-Board Systems Data transit_vehicle_reported_emissions_data Provide Transit Vehicle Status and Probe Information
Process Traffic Data strategy_data_for_roads Determine Indicator State for Road Management
Process Traffic Sensor Data hov_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data multimodal_crossing_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data pedestrian_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data reversible_lane_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data traffic_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data traffic_data_for_vehicle_sensors Collect Vehicle Roadside Safety Data
Process Traffic Sensor Data local_sensor_data_for_highways Process Indicator Output Data for Freeways
Process Traffic Sensor Data local_sensor_data_for_roads Process Indicator Output Data for Roads
Process Traffic Sensor Data traffic_video_image Process Traffic Data
Process Traffic Sensor Data hov_sensor_data Process Traffic Data
Process Traffic Sensor Data multimodal_crossing_sensor_data Process Traffic Data
Process Traffic Sensor Data pedestrian_sensor_data Process Traffic Data
Process Traffic Sensor Data traffic_sensor_data Process Traffic Data
Process Traffic Sensor Data vehicle_characteristics_data Process Traffic Data
Process Vehicle Safety and Environmental Data for Output queue_warning_system_status Collect Traffic Field Equipment Fault Data
Process Vehicle Safety and Environmental Data for Output signal_phase_indication_to_transit_vehicle Determine Transit Vehicle Service Status
Process Vehicle Safety and Environmental Data for Output signal_phase_response_state_to_transit_vehicle Determine Transit Vehicle Service Status
Process Vehicle Safety and Environmental Data for Output signal_phase_timing_to_transit_vehicle Determine Transit Vehicle Service Status
Provide Transit Vehicle Location Data tr_vehicle_roadside_current_status_data Collect Vehicle Roadside Safety Data
Provide Transit Vehicle Location Data tr_vehicle_roadside_location_data Collect Vehicle Roadside Safety Data
Provide Transit Vehicle Location Data tr_vehicle_roadside_size_data Collect Vehicle Roadside Safety Data
Provide Transit Vehicle Location Data tr_vehicle_roadside_speed_data Collect Vehicle Roadside Safety Data
Provide Transit Vehicle Location Data transit_roadside_path_prediction_data Collect Vehicle Roadside Safety Data
Provide Transit Vehicle Location Data transit_vehicle_location_for_eta Determine Transit Vehicle Service Status
Provide Transit Vehicle Location Data transit_vehicle_location_for_deviation Manage Transit Vehicle Deviations
Provide Transit Vehicle Location Data transit_vehicle_location_for_store Manage Transit Vehicle Operations
Provide Transit Vehicle Status and Probe Information transit_information_request Manage Transit Vehicle Operations
Select Strategy selected_hri_control_strategy Determine Indicator State for Road Management
Select Strategy selected_road_control_strategy Determine Indicator State for Road Management
Select Strategy signal_system_timing_plan Process Indicator Output Data for Roads
Select Strategy signal_system_configuration Process Indicator Output Data for Roads
Select Strategy intersection_roadside_sensor_configuration Process Vehicle Safety and Environmental Data for Output

Physical

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
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
ITS Roadway Equipment Field 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway itself. In CVRIA, this physical object represents all of the other ITS field equipment that interfaces with and supports the Connected Vehicle Roadside Equipment (RSE). This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Roadside Equipment Field 'Roadside Equipment' (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.
Traffic Management Center Center The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Transit Management Center Center The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces allow for communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
Transit Vehicle Databus Vehicle The 'Transit Vehicle Databus' represents the vehicle databus that interfaces with on-board equipment on a transit vehicle. It is a specialized and extended form of the Vehicle Databus that is subject to different vehicle databus standards and hosts a broad range of components that are unique to a transit vehicle including the farebox and associated electronics, passenger counters, and transit security systems. As a specialized form of the Vehicle Databus, it also provides access to the general-purpose sensors (e.g., radars, cameras), GPS, drive train monitoring and control systems, and vehicle safety features that support connected vehicle applications. The Transit Vehicle may represent a bus, paratransit vehicle, light rail vehicle, or other vehicle designed to carry passengers. In CVRIA, the 'Transit Vehicle Databus' is used to represent the onboard interactions between the Transit Vehicle OBE and the other systems included in a host transit vehicle.
Transit Vehicle OBE Vehicle The Transit Vehicle On-Board equipment (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.
Transit Vehicle Operator Vehicle The 'Transit Vehicle Operator' represents the person that receives and provides additional information that is specific to operating the ITS functions in all types of transit vehicles. The information received by the operator would include status of on-board systems. Additional information received depends upon the type of transit vehicle. In the case of fixed route transit vehicles, the Transit Vehicle Operator would receive operator instructions that might include actions to take to correct schedule deviations. In the case of flexible fixed routes and demand response routes the information would also include dynamic routing or passenger pickup information.

Includes Application Objects:

Application Object Description Physical Object
Roadway Signal Control "Roadway Signal Control" includes the field elements that monitor and control signalized intersections. It includes the traffic signal controllers, detectors, conflict monitors, signal heads, and other ancillary equipment that supports traffic signal control. It also includes field masters, and equipment that supports communications with a central monitoring and/or control system, as applicable. The communications link supports upload and download of signal timings and other parameters and reporting of current intersection status. It represents the field equipment used in all levels of traffic signal control from basic actuated systems that operate on fixed timing plans through adaptive systems. It also supports all signalized intersection configurations, including those that accommodate pedestrians. In advanced, future implementations, environmental data may be monitored and used to support dilemma zone processing and other aspects of signal control that are sensitive to local environmental conditions. ITS Roadway Equipment
RSE Intersection Management "RSE Intersection Management" uses short range communications to support connected vehicle applications that manage signalized intersections. It communicates with approaching vehicles and ITS infrastructure (e.g., the traffic signal controller) to enhance traffic signal operations. Coordination with the ITS infrastructure also supports conflict monitoring to ensure the RSE output and traffic signal control output are consistent and degrade in a fail safe manner. Roadside Equipment
TMC Multi-Modal Coordination "TMC Multi-Modal Coordination" supports center-to-center coordination between the Traffic Management and Transit Management Centers. It monitors transit operations and provides traffic signal priority for transit vehicles on request from the Transit Management Center. Traffic Management Center
TMC Signal Control "TMC Signal Control" provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single traffic management center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc. Traffic Management Center
Transit Center Emissions Monitoring "Transit Center Emissions Monitoring" collects and/or estimates current transit fleet emissions and forecasts future fleet emissions. The collected, estimated, and forecast emissions is monitored and forwarded to other agencies to more effectively manage transit operations to reduce emissions. Transit Management Center
Transit Center Passenger Counting "Transit Center Passenger Counting" receives and processes transit vehicle loading data using two-way communications from equipped transit vehicles. Transit Management Center
Transit Center Priority Management "Transit Center Priority Management" monitors transit schedule performance and generates requests for transit priority on routes and at certain intersections. It may coordinate with the Traffic Management Center to provide transit priority along the selected route, including allocation of dynamic lanes and granting signal priority. It also coordinates with the Transit Vehicle OBE to monitor and manage local transit signal priority requests at individual intersections. Transit Management Center
Transit Vehicle Emissions Monitoring "Transit Vehicle Emissions Monitoring" directly measures or estimates vehicle emissions and provides current and average emissions measures to the Transit Management Center. Transit Vehicle OBE
Transit Vehicle Passenger Counting "Transit Vehicle Passenger Counting" collects transit vehicle loading data and makes it available to the center. Transit Vehicle OBE
Transit Vehicle Signal Priority "Transit Vehicle Signal Priority" provides the capability for transit vehicles to determine eligibility for priority and request signal priority at signalized intersections, ramps, and interchanges through short range communication with traffic control equipment at the roadside. Transit Vehicle OBE

Includes Information Flows:

Information Flow Description
driver information Regulatory, warning, and guidance information provided to the driver while en route to support safe and efficient vehicle operation.
host transit vehicle status Information provided to the Connected Vehicle on-board equipment from other systems on the Transit Vehicle Platform.
intersection control status Status data provided by the traffic signal controller including phase information, alarm status, and priority/preempt status.
intersection status Current signal phase and timing information for all lanes at a signalized intersection. This flow identifies active lanes and lanes that are being stopped and specifies the length of time that the current state will persist for each lane. It also identifies signal priority and preemption status and pedestrian crossing status information where applicable.
local signal priority request Request from a vehicle to a signalized intersection for priority at that intersection. This flow also allows the vehicle to cancel a priority request (for example, when the vehicle clears the intersection).
right-of-way request notification Notice that a request has occurred for signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other source for right-of-way.
signal control commands Control of traffic signal controllers or field masters including clock synchronization.
signal control status Operational and status data of traffic signal control equipment including operating condition and current indications.
signal priority service request A service request for vehicle priority issued to a traffic signal controller that results in green extension or other accommodation for the priority vehicle, within the current signal timing plan. The request includes the priority level, the desired time and duration of service, and the intended travel path through the intersection. This flow also allows the RSE to cancel a previously issued request for priority.
traffic control priority request Request for signal priority at one or more intersections along a particular route.
traffic control priority status Status of signal priority request functions at the roadside (e.g. enabled or disabled).
transit schedule information Current and projected transit schedule information used to initialize the transit vehicle with a vehicle assignment, monitor schedule performance, and develop corrective actions on-board.
transit vehicle emissions GHG and criteria air pollutant emissions reported by a transit vehicle.
transit vehicle loading data Data collected on board the transit vehicle relating to passenger boarding and alighting.
transit vehicle operator display Visual, audible, and tactile outputs to the transit vehicle operator including vehicle surveillance information, alarm information, vehicle system status, information from the operations center, and information indicating the status of all other on-board ITS services.
transit vehicle operator input Transit vehicle operator inputs to on-board ITS equipment, including tactile and verbal inputs. Includes authentication information, on-board system control, emergency requests, and fare transaction data.
transit vehicle schedule performance Estimated times of arrival and anticipated schedule deviations reported by a transit vehicle.
vehicle location and motion Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.

Application Interconnect Diagram

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
The application interconnect diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram

Requirements

Need Requirement
N1.001 Transportation agencies need to gather data from vehicles or infrastructure to support environmental monitoring. 1.001 All environmental applications shall collect data from mobile devices to support environmental monitoring, including ambient air quality, emissions, temperature, precipitation, and other road weather information.
1.002 All environmental applications shall collect data from infrastructure devices to support environmental monitoring, including ambient air quality, emissions, temperature, precipitation, wind speed, and other road weather information.
N1.038a Eco-Transit Signal Priority needs to collect traffic signal priority requests originating from transit vehicles. 1.118 The Eco-Transit Signal Priority System shall collect traffic signal priority requests originating from transit vehicles equipped with traffic signal priority applications and transponders.
N1.039 The Eco-Transit Signal Priority needs to request traffic signal priority at signalized intersections. 1.136 The Eco-Transit Signal Priority Vehicle System shall request traffic signal priority at a signalized intersection.
N1.042a Eco-Transit Signal Priority needs to process signal priority requests to determine whether a signal priority request should be granted. 1.109 The Eco-Transit Signal Priority System shall include decision support capabilities for determining whether a signal priority request should be granted.
N1.048 The Transit Vehicle System needs to collect transit vehicle operating information such as schedule adherence and passenger loading to support a signal priority request. 1.128 The Eco-Transit Signal Priority Vehicle System shall collect data from onboard systems about the transit vehicle's adherence to a schedule or the number of passengers on the vehicle.

Related Sources

  • Eco-Signal Operations: Operational Concept, Final, 10/1/2013

Security

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

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Security levels have not been defined yet.



In order to participate in this application, 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
Security levels have not been defined yet.