Type: Mobility

Groups:
  • Commercial Vehicle Fleet Operations
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.

Container/Chassis Operating Data

The Container/Chassis Operating Data (CCOD) application allows the commercial vehicle driver (and fleet operator) to monitor the operating status of their containers or chassis. The data monitored may include temperature, humidity, battery levels, etc. This application could be implemented through the power unit providing information for the containers or chasses directly to the commercial vehicle (e.g. a variation of a vehicle to vehicle interface), or the information could be transmitted from each container or chassis directly to the infrastructure (e.g. a container to infrastructure interface).

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:

Container/Chassis Operating Data Operations Stage
Fleet-Freight ManagerCommercial Vehicle OwnerFreight Equipment OwnerCommercial Vehicle DriverCV On-Board Cargo Monitoring ProviderFreight Equipment Monitoring Provider
Fleet-Freight ManagerInformation Provision AgreementInformation Provision Agreement
Commercial Vehicle OwnerInformation Provision AgreementExpectation of Information ProvisionVehicle Operating AgreementApplication Usage Agreement
Freight Equipment OwnerInformation Provision AgreementExpectation of Information ProvisionApplication Usage Agreement
Commercial Vehicle DriverVehicle Operating Agreement
CV On-Board Cargo Monitoring ProviderApplication Usage Agreement
Freight Equipment Monitoring ProviderApplication 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.
Commercial Vehicle Driver The 'Commercial Vehicle Driver' represents the people that operate vehicles transporting goods, including both long haul trucks and local pick-up and delivery vans. This physical object is complementary to the Driver physical object in that it represents those interactions which are unique to Commercial Vehicle Operations. Information flowing from the Commercial Vehicle Driver includes those system inputs specific to Commercial Vehicle Operations.
Commercial Vehicle Manufacturer The entity which builds commercial vehicles, including long haul trucks and local pick up and delivery vehicles. This entity is complementary to the Vehicle Manufacturer entity in that it represents those aspects of vehicle manufacture which are unique to commercial vehicles.
Commercial Vehicle OBE Manufacturer The Commercial Vehicle OBE Manufacturer is the provider of the commercial 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.
Commercial Vehicle Owner The entity that owns the commercial vehicle. This entity is complementary to the Vehicle Owner in that it represents those aspects of ownership which are unique to commercial vehicles.
CV On-Board Cargo 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.
CV On-Board Cargo 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.
CV On-Board Cargo 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.
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.
Fleet-Freight Manager The 'Fleet-Freight Manager' represents the people that are responsible for the dispatching and management of Commercial Vehicle fleets (e.g. traditional Fleet Managers) and Freight Equipment assets. It may be many people in a large tracking organization or a single person (owner driver) in the case of single vehicle fleets. The Fleet-Freight Manager provides instructions and coordination for Commercial Vehicles and Freight Equipment and receives the status of the vehicles and freight equipment in the fleet that they manage.
Freight Administration and 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.
Freight Administration and 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.
Freight Administration and Management Provider The developer and distributor of center systems that monitor and track the movement of freight containers, facilitates intermodal transfers and border crossings.
Freight Equipment Manufacturer The entity that builds freight equipment.
Freight Equipment 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.
Freight Equipment 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.
Freight Equipment 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.
Freight Equipment Owner The entity that owns freight equipment such as a freight container, intermodal chassis or trailer.
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.

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.
Commercial Vehicle The commercial vehicle includes the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It includes two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials, and provides HAZMAT response teams with timely and accurate cargo contents information after a vehicle incident. It can collect and process vehicle, cargo information from the attached freight equipment, and driver safety data and status and alert the driver whenever there is a potential safety or security problem. Basic identification, security and safety status data are supplied to inspection facilities at mainline speeds. In addition, it can automatically collect and record mileage, fuel usage, and border crossings.
Commercial Vehicle OBE The Commercial Vehicle On-Board Equipment (OBE) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials. 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 commercial vehicles. The Commercial Vehicle OBE supplements these general capabilities with capabilities that are specific to commercial vehicles.
CV On-Board Cargo Monitoring "CV On-Board Cargo Monitoring" monitors the location and status of the commercial vehicle and its cargo. It sends the collected data to appropriate centers and roadside facilities, including emergency management in the case of HAZMAT incidents. Depending on the nature of the cargo, it may include sensors that measure temperature, pressure, load leveling, acceleration, and other attributes of the cargo.
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.
Fleet and Freight Management Center The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet.
Freight Administration and Management "Freight Administration and Management" manages the movement of freight from source to destination. It interfaces to intermodal customers to setup and schedule transportation and coordinates with intermodal terminals and freight consolidation stations to coordinate the shipment. It coordinates with the appropriate government agencies to expedite the movement of trucks, their drivers, and their cargo across international borders. The application monitors the status of the freight and freight equipment (container, trailer, or chassis) and monitors freight location and compares it against the planned route.
Freight Equipment 'Freight Equipment' represents a freight container, intermodal chassis, or trailer and provides sensory, processing, storage, and communications functions necessary to support safe, secure and efficient freight operations. It provides equipment safety data and status and can alert the appropriate systems of an incident, breach, or tamper event. It also provides accurate position information to support in-transit visibility of freight equipment.
Freight Equipment Monitoring "Freight Equipment Monitoring" includes the on-board devices used to monitor intermodal freight equipment. These devices provide freight equipment location and status of the freight, container, or chassis equipment.
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.

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.
Backoffice Component Maintenance Agreement Agreement An agreement in which one entity maintains the operational status of the backoffice component of an application 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.
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.
Includes Includes Indicates that one component is entirely contained within another component.
Information Provision Agreement Agreement An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
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.
Mobile Component Maintenance Agreement Agreement An agreement in which one entity maintains the operational status of the mobile component of an application 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.
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
2.4 Provide Commercial Vehicle Data Collection Collection
2.4.2 Collect On-board Commercial Vehicle Sensor Data Pspec - CV On-Board Cargo Monitoring
2.4.4 Provide Commercial Vehicle Driver Interface Pspec - CV On-Board Cargo Monitoring
2.4.7 Manage CV On-board Data Pspec - CV On-Board Cargo Monitoring
2.6 Provide Commercial Vehicle On-board Data Collection
2.6.4 Provide Lock Tag Data Interface Pspec - CV On-Board Cargo Monitoring
2.7 Provide Freight Operations Collection
2.7.2 Monitor Freight Equipment Route Pspec - Freight Administration and Management
2.7.3 Manage Freight Equipment Fleet Pspec - Freight Administration and Management
2.7.4 Manage Freight Equipment Maintenance Pspec - Freight Administration and Management
2.7.5 Process Freight Integrity Data Pspec - Freight Administration and Management
2.7.6 Provide Freight Manager Interface Pspec - Freight Administration and Management
2.8 Manage Intermodal Operations Collection
2.8.3.1 Provide Driver Interface for Intermodal Freight Dispatch Pspec - CV On-Board Cargo Monitoring
2.8.3.4 Determine Freight Equipment Status Pspec - Freight Equipment Monitoring

Includes Data Flows:

Source Pspec Data Flow Destination Pspec
Collect On-board Commercial Vehicle Sensor Data cvo_on_board_sensor_data Manage CV On-board Data
Determine Freight Equipment Status fe_cargo_info_for_cv Collect On-board Commercial Vehicle Sensor Data
Determine Freight Equipment Status fe_integrity_data_for_cv Collect On-board Commercial Vehicle Sensor Data
Determine Freight Equipment Status fe_location_data_for_cv Collect On-board Commercial Vehicle Sensor Data
Determine Freight Equipment Status fe_maintenance_data_for_cv Collect On-board Commercial Vehicle Sensor Data
Determine Freight Equipment Status fe_operational_data_for_cv Collect On-board Commercial Vehicle Sensor Data
Determine Freight Equipment Status fe_cargo_information Manage Freight Equipment Fleet
Determine Freight Equipment Status fe_operational_data Manage Freight Equipment Fleet
Determine Freight Equipment Status fe_maintenance_data Manage Freight Equipment Maintenance
Determine Freight Equipment Status fe_location_data Monitor Freight Equipment Route
Determine Freight Equipment Status fe_lock_tag_data Process Freight Integrity Data
Determine Freight Equipment Status fe_integrity_data Process Freight Integrity Data
Determine Freight Equipment Status fe_lock_tag_data_for_cv Provide Lock Tag Data Interface
Manage CV On-board Data cv_cargo_information Manage Freight Equipment Fleet
Manage CV On-board Data cv_freight_operations Manage Freight Equipment Fleet
Manage CV On-board Data cv_freight_maintenance Manage Freight Equipment Maintenance
Manage CV On-board Data cv_freight_location Monitor Freight Equipment Route
Manage CV On-board Data cv_freight_integrity Process Freight Integrity Data
Manage Freight Equipment Fleet operational_monitoring_parameters Determine Freight Equipment Status
Manage Freight Equipment Fleet freight_equipment_maintenance_availability Manage Freight Equipment Maintenance
Manage Freight Equipment Fleet planned_freight_route Monitor Freight Equipment Route
Manage Freight Equipment Fleet intermodal_container_dispatch_assignment Provide Driver Interface for Intermodal Freight Dispatch
Manage Freight Equipment Fleet freight_fleet_status Provide Freight Manager Interface
Manage Freight Equipment Maintenance freight_equipment_maint_status Manage Freight Equipment Fleet
Monitor Freight Equipment Route freight_location_information Manage Freight Equipment Fleet
Process Freight Integrity Data integrity_monitoring_parameters Determine Freight Equipment Status
Provide Freight Manager Interface freight_manager_updates Manage Freight Equipment Fleet
Provide Freight Manager Interface freight_route_monitoring_parameters Monitor Freight Equipment Route
Provide Freight Manager Interface freight_integrity_monitoring_parameters Process Freight Integrity Data

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
Commercial Vehicle Databus Vehicle The 'Commercial Vehicle Databus' represents the interface to the heavy vehicle databus that connects on-board systems included in the commercial vehicle. This vehicle is used to transport goods, is operated by a professional driver and typically administered as part of a larger fleet. Commercial Vehicle classification applies to all goods transport vehicles ranging from small panel vans used in local pick-up and delivery services to large, multi-axle tractor-trailer rigs operating on long haul routes. It is a specialized and extended form of the Vehicle Databus that may be subject to different vehicle databus standards and connect with a broad range of components that are specific to commercial vehicles including the systems that are used to monitor, secure, and maintain freight while enroute. 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.
Commercial Vehicle Driver Vehicle The 'Commercial Vehicle Driver' represents the people that operate vehicles transporting goods, including both long haul trucks and local pick-up and delivery vans. This physical object is complementary to the Driver physical object in that it represents those interactions which are unique to Commercial Vehicle Operations. Information flowing from the Commercial Vehicle Driver includes those system inputs specific to Commercial Vehicle Operations.
Commercial Vehicle OBE Vehicle The Commercial Vehicle On-Board Equipment (OBE) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials. 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 commercial vehicles. The Commercial Vehicle OBE supplements these general capabilities with capabilities that are specific to commercial vehicles.
Fleet and Freight Management Center Center The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet.
Fleet-Freight Manager Center The 'Fleet-Freight Manager' represents the people that are responsible for the dispatching and management of Commercial Vehicle fleets (e.g. traditional Fleet Managers) and Freight Equipment assets. It may be many people in a large tracking organization or a single person (owner driver) in the case of single vehicle fleets. The Fleet-Freight Manager provides instructions and coordination for Commercial Vehicles and Freight Equipment and receives the status of the vehicles and freight equipment in the fleet that they manage.
Freight Equipment Vehicle 'Freight Equipment' represents a freight container, intermodal chassis, or trailer and provides sensory, processing, storage, and communications functions necessary to support safe, secure and efficient freight operations. It provides equipment safety data and status and can alert the appropriate systems of an incident, breach, or tamper event. It also provides accurate position information to support in-transit visibility of freight equipment.

Includes Application Objects:

Application Object Description Physical Object
CV On-Board Cargo Monitoring "CV On-Board Cargo Monitoring" monitors the location and status of the commercial vehicle and its cargo. It sends the collected data to appropriate centers and roadside facilities, including emergency management in the case of HAZMAT incidents. Depending on the nature of the cargo, it may include sensors that measure temperature, pressure, load leveling, acceleration, and other attributes of the cargo. Commercial Vehicle OBE
Freight Administration and Management "Freight Administration and Management" manages the movement of freight from source to destination. It interfaces to intermodal customers to setup and schedule transportation and coordinates with intermodal terminals and freight consolidation stations to coordinate the shipment. It coordinates with the appropriate government agencies to expedite the movement of trucks, their drivers, and their cargo across international borders. The application monitors the status of the freight and freight equipment (container, trailer, or chassis) and monitors freight location and compares it against the planned route. Fleet and Freight Management Center
Freight Equipment Monitoring "Freight Equipment Monitoring" includes the on-board devices used to monitor intermodal freight equipment. These devices provide freight equipment location and status of the freight, container, or chassis equipment. Freight Equipment

Includes Information Flows:

Information Flow Description
commercial vehicle status Current status of the commercial vehicle and associated freight equipment. This includes temperature, humidity, power, battery levels, brake wear data, door open/closed status, chassis bare/covered status)
CVO driver initialization This flow represents the tactile or auditory interface with ITS equipment containing the commercial vehicle driver and vehicle information. This flow contains inquiries to the commercial vehicle managing system, interaction with on-board equipment including setup, configuration, and initiation of self tests, and entry of carrier, driver, vehicle, and route information.
fleet manager inquiry This flow represents the tactile or auditory interface with ITS equipment containing an inquiry from fleet manager requesting data from commercial vehicle management system.
fleet status This flow represents the visual or auditory interface with ITS equipment containing fleet status information including enrollment status, safety status including inspection summaries, detailed inspection reports, and safety ratings, routing information, current vehicle information, and emergency information.
freight equipment information Container, trailer, or chassis information regarding identity, type, location, brake wear data, mileage, seal #, seal type, door open/close status, chassis bare/covered status, tethered / untethered status, temperature, humidity, power, battery levels, brake wear data, and bill of lading/information regarding the cargo/content.
host commercial vehicle status Information provided to the Connected Vehicle on-board equipment from other systems on the Commercial Vehicle Platform.

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
N2.049 Container/Chassis Operating Data (CCOD) needs to determine the operating status of containers and chassis. 2.115 Container/Chassis Operating Data (CCOD) shall monitor the operating status of containers, including the internal temperature, humidity, power and battery levels.
2.116 CCOD shall monitor the operating status of chassis, including brake wear data, door open/closed status, chassis bare/covered status.
N2.050 CCOD needs to provide the operating status of containers and chassis to commercial vehicle operator. 2.117 CCOD shall provide the operating status (temperature, humidity, power, battery levels, brake wear data, door open/closed status, chassis bare/covered status) of containers/chassis to the commercial vehicle operator.
N2.210 CCOD needs to provide the operating status of containers and chassis to the fleet operator. 2.117a CCOD shall provide the operating status (temperature, humidity, power, battery levels, brake wear data, door open/closed status, chassis bare/covered status) of containers/chassis to the commercial fleet operator.

Related Sources

  • SAE J3067- Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary (SAE J2735)Using Systems Engineering Methods, 8/15/2014

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.