CVO08: Smart Roadside and Virtual WIM
This service package includes the delivery of capabilities related to wireless roadside inspections and electronic screening/virtual weigh stations. Wireless roadside inspection is defined by a safety screening capability that employs communications technologies to obtain information from a commercial vehicle that will allow safety screening of the vehicle and its driver. This capability provides for the interrogation at mainline speeds of a commercial vehicle when it has entered a control segment or geofenced area. Vehicle identification and driver information are provided to the roadside unit. The information communicated can be used to verify compliance with safety requirements, allowing a decision to be made regarding whether the vehicle should pull in to a roadside check station. A more advanced version of this service package would download safety information measured on the vehicle including driver related information such as the driver log allowing real time evaluation that the vehicle and driver are meeting safety requirements. The electronic screening/virtual weigh stations capability employs communications technologies to obtain information from a commercial vehicle that will allow verification of permits or credentials for the vehicle. The information communicated is used to verify compliance with safety requirements, allowing a decision to be made regarding whether the vehicle should pull in to a roadside check station. This service package can also be used to verify that the commercial vehicle meets vehicle weight (via weigh in motion capability) or dimension requirements.
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
Source | Destination | Role/Relationship |
---|---|---|
Basic Commercial Vehicle Maintainer | Basic Commercial Vehicle | Maintains |
Basic Commercial Vehicle Manager | Basic Commercial Vehicle | Manages |
Basic Commercial Vehicle Manager | Commercial Vehicle Driver | System Usage Agreement |
Basic Commercial Vehicle Owner | Basic Commercial Vehicle Maintainer | System Maintenance Agreement |
Basic Commercial Vehicle Owner | Basic Commercial Vehicle Manager | Operations Agreement |
Basic Commercial Vehicle Owner | Commercial Vehicle Driver | Application Usage Agreement |
Basic Commercial Vehicle Owner | Commercial Vehicle Driver | Vehicle Operating Agreement |
Basic Commercial Vehicle Owner | Commercial Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
Basic Commercial Vehicle Owner | Commercial Vehicle OBE Owner | Expectation of Data Provision |
Basic Commercial Vehicle Owner | Commercial Vehicle OBE User | Service Usage Agreement |
Basic Commercial Vehicle Supplier | Basic Commercial Vehicle Owner | Warranty |
Commercial Vehicle Administration Center Maintainer | Commercial Vehicle Administration Center | Maintains |
Commercial Vehicle Administration Center Manager | Commercial Vehicle Administration Center | Manages |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Administration Center Maintainer | System Maintenance Agreement |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Administration Center Manager | Operations Agreement |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Check Equipment Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Check Equipment Owner | Information Provision Agreement |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Check Equipment User | Service Usage Agreement |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Driver | Application Usage Agreement |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Inspector | Application Usage Agreement |
Commercial Vehicle Administration Center Owner | Commercial Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle Administration Center Owner | Commercial Vehicle OBE Owner | Information Provision Agreement |
Commercial Vehicle Administration Center Owner | Commercial Vehicle OBE User | Service Usage Agreement |
Commercial Vehicle Administration Center Owner | Enforcement Center Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle Administration Center Owner | Enforcement Center Owner | Information Exchange Agreement |
Commercial Vehicle Administration Center Owner | Enforcement Center User | Service Usage Agreement |
Commercial Vehicle Administration Center Owner | Fleet and Freight Management Center Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle Administration Center Owner | Fleet and Freight Management Center Owner | Information Exchange Agreement |
Commercial Vehicle Administration Center Owner | Fleet and Freight Management Center User | Service Usage Agreement |
Commercial Vehicle Administration Center Owner | Other CV Administration Centers Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle Administration Center Owner | Other CV Administration Centers Owner | Information Exchange Agreement |
Commercial Vehicle Administration Center Owner | Other CV Administration Centers User | Service Usage Agreement |
Commercial Vehicle Administration Center Supplier | Commercial Vehicle Administration Center Owner | Warranty |
Commercial Vehicle Check Equipment Maintainer | Commercial Vehicle Check Equipment | Maintains |
Commercial Vehicle Check Equipment Manager | Commercial Vehicle Check Equipment | Manages |
Commercial Vehicle Check Equipment Manager | Commercial Vehicle Inspector | System Usage Agreement |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle Administration Center Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle Administration Center Owner | Information Exchange and Action Agreement |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle Administration Center User | Service Usage Agreement |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle Check Equipment Maintainer | System Maintenance Agreement |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle Check Equipment Manager | Operations Agreement |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle Driver | Application Usage Agreement |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle OBE Owner | Information Exchange and Action Agreement |
Commercial Vehicle Check Equipment Owner | Commercial Vehicle OBE User | Service Usage Agreement |
Commercial Vehicle Check Equipment Owner | Enforcement Center Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle Check Equipment Owner | Enforcement Center Owner | Information Exchange and Action Agreement |
Commercial Vehicle Check Equipment Owner | Enforcement Center User | Service Usage Agreement |
Commercial Vehicle Check Equipment Supplier | Commercial Vehicle Check Equipment Owner | Warranty |
Commercial Vehicle Driver | Basic Commercial Vehicle | Operates |
Commercial Vehicle Driver | Commercial Vehicle OBE | Operates |
Commercial Vehicle Driver | Driver Identification Card | Operates |
Commercial Vehicle Inspector | Commercial Vehicle Check Equipment | Operates |
Commercial Vehicle OBE Maintainer | Commercial Vehicle OBE | Maintains |
Commercial Vehicle OBE Manager | Commercial Vehicle Driver | System Usage Agreement |
Commercial Vehicle OBE Manager | Commercial Vehicle OBE | Manages |
Commercial Vehicle OBE Owner | Commercial Vehicle Administration Center Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle OBE Owner | Commercial Vehicle Administration Center Owner | Expectation of Data Provision |
Commercial Vehicle OBE Owner | Commercial Vehicle Administration Center User | Service Usage Agreement |
Commercial Vehicle OBE Owner | Commercial Vehicle Check Equipment Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle OBE Owner | Commercial Vehicle Check Equipment Owner | Expectation of Data Provision |
Commercial Vehicle OBE Owner | Commercial Vehicle Check Equipment User | Service Usage Agreement |
Commercial Vehicle OBE Owner | Commercial Vehicle Inspector | Application Usage Agreement |
Commercial Vehicle OBE Owner | Commercial Vehicle Inspector | Vehicle Operating Agreement |
Commercial Vehicle OBE Owner | Commercial Vehicle OBE Maintainer | System Maintenance Agreement |
Commercial Vehicle OBE Owner | Commercial Vehicle OBE Manager | Operations Agreement |
Commercial Vehicle OBE Owner | Fleet and Freight Management Center Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle OBE Owner | Fleet and Freight Management Center Owner | Expectation of Data Provision |
Commercial Vehicle OBE Owner | Fleet and Freight Management Center User | Service Usage Agreement |
Commercial Vehicle OBE Supplier | Commercial Vehicle OBE Owner | Warranty |
Driver Identification Card Maintainer | Driver Identification Card | Maintains |
Driver Identification Card Manager | Commercial Vehicle Driver | System Usage Agreement |
Driver Identification Card Manager | Driver Identification Card | Manages |
Driver Identification Card Owner | Commercial Vehicle Driver | Application Usage Agreement |
Driver Identification Card Owner | Commercial Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
Driver Identification Card Owner | Commercial Vehicle OBE Owner | Information Provision and Action Agreement |
Driver Identification Card Owner | Commercial Vehicle OBE User | Service Usage Agreement |
Driver Identification Card Owner | Driver Identification Card Maintainer | System Maintenance Agreement |
Driver Identification Card Owner | Driver Identification Card Manager | Operations Agreement |
Driver Identification Card Supplier | Driver Identification Card Owner | Warranty |
Enforcement Center Maintainer | Enforcement Center | Maintains |
Enforcement Center Manager | Enforcement Center | Manages |
Enforcement Center Owner | Commercial Vehicle Administration Center Maintainer | Maintenance Data Exchange Agreement |
Enforcement Center Owner | Commercial Vehicle Administration Center Owner | Information Exchange Agreement |
Enforcement Center Owner | Commercial Vehicle Administration Center User | Service Usage Agreement |
Enforcement Center Owner | Commercial Vehicle Check Equipment Maintainer | Maintenance Data Exchange Agreement |
Enforcement Center Owner | Commercial Vehicle Check Equipment Owner | Information Provision Agreement |
Enforcement Center Owner | Commercial Vehicle Check Equipment User | Service Usage Agreement |
Enforcement Center Owner | Commercial Vehicle Inspector | Application Usage Agreement |
Enforcement Center Owner | Enforcement Center Maintainer | System Maintenance Agreement |
Enforcement Center Owner | Enforcement Center Manager | Operations Agreement |
Enforcement Center Supplier | Enforcement Center Owner | Warranty |
Fleet and Freight Management Center Maintainer | Fleet and Freight Management Center | Maintains |
Fleet and Freight Management Center Manager | Fleet and Freight Management Center | Manages |
Fleet and Freight Management Center Owner | Commercial Vehicle Administration Center Maintainer | Maintenance Data Exchange Agreement |
Fleet and Freight Management Center Owner | Commercial Vehicle Administration Center Owner | Information Exchange Agreement |
Fleet and Freight Management Center Owner | Commercial Vehicle Administration Center User | Service Usage Agreement |
Fleet and Freight Management Center Owner | Commercial Vehicle Driver | Application Usage Agreement |
Fleet and Freight Management Center Owner | Commercial Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
Fleet and Freight Management Center Owner | Commercial Vehicle OBE Owner | Information Provision Agreement |
Fleet and Freight Management Center Owner | Commercial Vehicle OBE User | Service Usage Agreement |
Fleet and Freight Management Center Owner | Fleet and Freight Management Center Maintainer | System Maintenance Agreement |
Fleet and Freight Management Center Owner | Fleet and Freight Management Center Manager | Operations Agreement |
Fleet and Freight Management Center Supplier | Fleet and Freight Management Center Owner | Warranty |
Freight Equipment Maintainer | Freight Equipment | Maintains |
Freight Equipment Manager | Freight Equipment | Manages |
Freight Equipment Owner | Commercial Vehicle Check Equipment Maintainer | Maintenance Data Exchange Agreement |
Freight Equipment Owner | Commercial Vehicle Check Equipment Owner | Expectation of Data Provision |
Freight Equipment Owner | Commercial Vehicle Check Equipment User | Service Usage Agreement |
Freight Equipment Owner | Commercial Vehicle Driver | Application Usage Agreement |
Freight Equipment Owner | Commercial Vehicle Driver | Vehicle Operating Agreement |
Freight Equipment Owner | Commercial Vehicle Inspector | Application Usage Agreement |
Freight Equipment Owner | Commercial Vehicle Inspector | Vehicle Operating Agreement |
Freight Equipment Owner | Commercial Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
Freight Equipment Owner | Commercial Vehicle OBE Owner | Expectation of Data Provision |
Freight Equipment Owner | Commercial Vehicle OBE User | Service Usage Agreement |
Freight Equipment Owner | Freight Equipment Maintainer | System Maintenance Agreement |
Freight Equipment Owner | Freight Equipment Manager | Operations Agreement |
Freight Equipment Supplier | Freight Equipment Owner | Warranty |
Other CV Administration Centers Maintainer | Other CV Administration Centers | Maintains |
Other CV Administration Centers Manager | Other CV Administration Centers | Manages |
Other CV Administration Centers Owner | Commercial Vehicle Administration Center Maintainer | Maintenance Data Exchange Agreement |
Other CV Administration Centers Owner | Commercial Vehicle Administration Center Owner | Information Exchange Agreement |
Other CV Administration Centers Owner | Commercial Vehicle Administration Center User | Service Usage Agreement |
Other CV Administration Centers Owner | Other CV Administration Centers Maintainer | System Maintenance Agreement |
Other CV Administration Centers Owner | Other CV Administration Centers Manager | Operations Agreement |
Other CV Administration Centers Supplier | Other CV Administration Centers Owner | Warranty |
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
Physical Object | Class | Description |
---|---|---|
Basic Commercial Vehicle | Vehicle | The 'Basic Commercial Vehicle' represents the commercial vehicle that hosts the on-board equipment that provides ITS capabilities. It includes the heavy vehicle databus and all other interface points between on-board systems and the rest of 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. |
Commercial Vehicle Administration Center | Center | The 'Commercial Vehicle Administration Center' performs administrative functions supporting credentials, tax, and safety regulations associated with commercial vehicles. It issues credentials, collects fees and taxes, and supports enforcement of credential requirements. It communicates with motor carriers to process credentials applications and collect fuel taxes, weight/distance taxes, and other taxes and fees associated with commercial vehicle operations. It also receives applications for, and issues special Oversize/Overweight and HAZMAT permits in coordination with cognizant authorities. It coordinates with other Commercial Vehicle Administration Centers (in other states/regions) to support nationwide access to credentials and safety information for administration and enforcement functions. It communicates with field equipment to enable credential checking and safety information collection at the roadside. It makes safety information available to qualified stakeholders to identify carriers and drivers that operate unsafely. |
Commercial Vehicle Check Equipment | Field | 'Commercial Vehicle Check Equipment' supports automated vehicle identification at mainline speeds for credential checking, roadside safety inspections, and weigh-in-motion using two-way data exchange. These capabilities include providing warnings to the commercial vehicle drivers, their fleet managers, and proper authorities of any safety problems that have been identified, accessing and examining historical safety data, and automatically deciding whether to allow the vehicle to pass or require it to stop with operator manual override. Commercial Vehicle Check Equipment also provides supplemental inspection services such as expedited brake inspections, the use of operator hand-held devices, mobile screening sites, on-board safety database access, and the enrollment of vehicles and carriers in the electronic clearance program. |
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 Inspector | Field | The people who perform regulatory inspection of Commercial Vehicles in the field. CVO Inspectors support roadside inspection, weighing, and checking of credentials either through automated preclearance or manual methods. The Commercial Vehicle Inspector is an inspection and enforcement arm of regulatory agencies with frequent direct interface with Commercial Vehicles and their Drivers. |
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. A separate 'Vehicle OBE' physical object supports vehicle safety and driver information capabilities that apply to all vehicles, including commercial vehicles. The Commercial Vehicle OBE supplements these general ITS capabilities with capabilities that are specific to commercial vehicles. |
Driver Identification Card | Vehicle | 'Driver Identification Card' represents the card or device that enables the transfer of electronic identification information for a driver. This may include license information, biometrics, and other data to identify the driver. Typically the card will be issued by a government agency (e.g. a state driver licensing agency). |
Enforcement Center | Center | The 'Enforcement Center' represents the systems that receive reports of violations detected by various ITS facilities including individual vehicle emissions, lane violations, toll violations, CVO violations, etc. |
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. |
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. |
Other CV Administration Centers | Center | 'Other CV Administration Centers' is intended to provide a source and destination for information flows between peer (e.g. inter-regional) commercial vehicle administration centers. It enables commercial vehicle administration activities to be coordinated across different jurisdictional areas. It encompasses all functions associated with commercial vehicle safety, registration, and operating authority for non-U.S. based commercial motor vehicle carriers. The agencies represented herein may include Federal, state, provincial, and local regulatory entities outside the U.S. |
Includes Functional Objects:
Functional 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 |
CV On-Board Electronic Screening Support | 'CV On-Board Electronic Screening Support' exchanges information with roadside facilities, providing information such as driver, vehicle, and carrier identification to roadside facilities that can be used to support electronic screening. Pass/pull-in messages are received and presented to the commercial vehicle driver and screening events are recorded. Additional information, including trip records (e.g., border clearance information), safety inspection records, cargo information, and driver status information may also be collected, stored, and made available to the roadside facility. | Commercial Vehicle OBE |
CV On-Board Safety and Security | 'CV On-Board Safety and Security' collects and processes vehicle and driver safety and security information and provides safety and security information to the Fleet and Freight Management Center. It also supplies this information to the roadside facilities both at mainline speeds and while stopped for inspections. Safety information may also be provided at predetermined trigger areas using wireless communications. The capability to alert the commercial vehicle driver whenever there is a critical safety or security problem or potential emergency is also provided. It also supports on-board driver safety log maintenance and checking. | Commercial Vehicle OBE |
CVAC Credentials and Taxes Administration | 'CVAC Credentials and Taxes Administration' issues credentials, collects fees and taxes, and supports enforcement of credential requirements. It manages driver licensing and enrolls carriers in additional CVO programs such as wireless roadside inspection programs. It communicates with the Fleet and Freight Management Centers associated with the motor carriers to process applications and collect fuel taxes, weight/distance taxes, and other taxes and fees associated with commercial vehicle operations. It also receives applications for, and issues special Oversize/Overweight and HAZMAT permits in coordination with other cognizant authorities. It supports user account management and receives and processes requests for review of carrier and driver status. It communicates with peer functional objects in other jurisdictions to exchange credentials database information. | Commercial Vehicle Administration Center |
CVAC Information Exchange | 'CVAC Information Exchange' supports the exchange of safety, credentials, permit data, and other data concerning the operation of commercial vehicles among jurisdictions. The object also supports the exchange of safety (e.g., driver logs), credentials, permit, and operations data between systems (for example, an administrative center and the roadside check facilities) within a single jurisdiction. Data are collected from multiple authoritative sources and packaged into snapshots (top-level summary and critical status information) and profiles (detailed and historical data). Data is made available to fleet operators and other information requestors on request or based on subscriptions established by the requestor. | Commercial Vehicle Administration Center |
CVAC Safety and Security Administration | 'CVAC Safety and Security Administration' provides commercial vehicle safety and security criteria to roadside check facilities, collects and reviews safety and security data from the field and distributes safety and security information to other centers, carriers, and enforcement agencies. It also supports wireless roadside inspections, including carrier enrollment, managing and distributing information about trigger areas where wireless inspections may occur, and monitoring the condition of the commercial vehicle and driver using wireless communications at identified trigger areas. It supports the collection and review of carrier and driver safety and security data and supports determination of the carrier and driver safety and security ratings. It clears the out-of-service status when the responsible carrier or driver reports that deficiencies flagged during inspections have been corrected. | Commercial Vehicle Administration Center |
CVCE Citation and Accident Electronic Recording | 'CVCE Citation and Accident Electronic Recording' documents accidents, citations, and violations identified during roadside safety inspections and forwards the information to the Commercial Vehicle Administration Center for processing. It collects data from the vehicle to help characterize the circumstances surrounding the accident. | Commercial Vehicle Check Equipment |
CVCE Electronic Screening | 'CVCE Electronic Screening' supports electronic credentials and safety screening of commercial vehicles at mainline speeds. It processes the data from the commercial vehicles along with accessed database information to determine whether a pull-in message is needed. It may also generate random pull-in messages with provisions for facility operators and enforcement officials to have manual override capabilities. | Commercial Vehicle Check Equipment |
CVCE Safety and Security Inspection | 'CVCE Safety and Security Inspection' supports the roadside safety inspection process, including wireless roadside inspections that are conducted remotely. It reads on-board safety data at mainline speeds to rapidly check the vehicle and driver and accesses historical and current safety data after identifying vehicles at mainline speeds or while stopped at the roadside. The capabilities to process safety data and issue pull-in messages or provide warnings to the driver, carrier, and enforcement agencies are also provided. It includes hand held or automatic devices to rapidly inspect the vehicle and driver, including driver logs. Results of screening and summary safety inspection data are stored and maintained. Since a vehicle may cross jurisdictional boundaries during a trip, it supports the concept of a last clearance event record carried on the vehicle tag. The last clearance event record reflects the results of the roadside verification action. For example, if the vehicle is pulled over in State A and undergoes credential, weight, and safety checks, the results of the clearance process are written to the vehicle s tag. If the vehicle continues the trip and passes a roadside station in State B, the State B station has access to the results of the previous pull-in because it can read the last clearance event record written by the State A roadside station. It associates high-risk cargo with the container/chassis, manifest, carrier, vehicle and driver transporting it. |
Commercial Vehicle Check Equipment |
CVCE Weigh-In-Motion | 'CVCE Weigh-In-Motion' measures and records axle weights and gross vehicle weight without requiring the vehicle to come to a stop. Both permanent and portable installations are supported and may be performed in conjunction with electronic clearance or as a separate application. | Commercial Vehicle Check Equipment |
Fleet Administration | 'Fleet Administration' provides vehicle tracking, dispatch, and reporting capabilities to fleet management personnel. It gathers current road conditions, commercial vehicle-specific traffic and parking information, prepares vehicle routes, and provides a fleet interface for toll collection. It also provides route plan information for network performance evaluation. As part of the tracking function, it monitors commercial vehicle location, compares it against the known route and notifies the Emergency Management Center and Fleet-Freight Manager of any deviations, including HAZMAT route restriction violations. It supports carrier participation in wireless roadside inspection programs, monitoring geographic trigger areas and providing current safety data on behalf of the commercial vehicles it manages. It supports pre-hiring checks for potential drivers and monitors the performance of each driver who is hired. It also supports ongoing monitoring of the company's safety performance. | Fleet and Freight Management Center |
Includes Information Flows:
Information Flow | Description |
---|---|
citation | Report of commercial vehicle citation. The citation includes references to the statute(s) that was (were) violated. It includes information on the violator and the officer issuing the citation. A citation differs from a violation because it is adjudicated by the courts. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown. |
commercial vehicle permit information | Information for commercial vehicle permits for oversize, overweight, or for dangerous goods. The query flow is not explicitly shown. |
commercial vehicle violation notification | Notification of a violation. The violation notification flow describes the statute or regulation that was violated and how it was violated (e. g., overweight on specific axle by xxx pounds or which brake was out of adjustment and how far out of adjustment it was). A violation differs from a citation because it is not adjudicated by the courts. It specifically includes the date/time and location of the violation and identification of the vehicle, driver, and associated equipment/cargo. |
credentials information | Response containing full vehicle fuel tax and registration credentials information. "Response" may be provided in reaction to a real-time query or a standing request for updated information. The query flow is not explicitly shown. |
credentials status information | Credentials information such as registration, licensing, insurance, check flags, and electronic screening enrollment data. A unique identifier is included. Corresponds to the credentials portion of CVISN "snapshots." The status information may be provided as a response to a real-time query or as a result of a standing request for updated information (subscription). This may also include information about non-U.S. fleets for use by U.S. authorities, and information regarding U.S. fleets made available to Mexican and Canadian authorities. The query flow is not explicitly shown. |
cv driver credential | Driver information (e.g., identity, biometrics, address, date of birth, endorsements, restrictions) stored on a driver's license or other official identification card used to identify a driver of commercial vehicles. |
cv driver input | 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. |
cv driver record | Information typically maintained by a state driver licensing agency about a driver of a commercial vehicle including driver identification data, license data, permit data, and driving history details. The query flow is not explicitly shown. |
CVC override mode | This flow represents the tactile or auditory interface with ITS equipment containing the manual override of automated pass/pull-in decisions generated by the Commercial Vehicle Check station. |
CVO inspector information | This flow represents the visual or auditory interface with ITS equipment containing credential, safety, and preclearance information and instructions to the commercial vehicle inspector. |
CVO inspector input | This flow represents the tactile or auditory interface with ITS equipment containing requests from the commercial vehicle inspector to operate the commercial vehicle inspection station. |
CVO pass/pull-in message | This flow represents the visual or auditory interface with ITS equipment containing a message sent to commercial vehicle driver indicating whether to bypass or requesting pull in to inspection/verification stop along with inspection results (e. g., LED indicator on transponder or variable message sign). |
daily site activity data | Record of daily activities at commercial vehicle check stations including summaries of screening events and inspections. |
driver log | A daily log showing hours in service for the current driver. The query flow is not explicitly shown. |
electronic screening request | Request for identification data to support electronic screening. |
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 ITS on-board equipment from other systems on the Commercial Vehicle Platform. |
information on violators | Information on violators provided by a law enforcement agency. May include information about commercial vehicle violations or other kinds of violations associated with the particular entity. The information may be provided as a response to a real-time query or proactively by the source. The query flow is not explicitly shown. |
on-board safety data | Safety data measured by on-board sensors. Includes information about the vehicle, vehicle components, cargo, and driver. The query flow is not explicitly shown. |
pass/pull-in | Command to commercial vehicle to pull into or bypass inspection station. |
roadside data message | Data set collected by roadside sensors to identify and characterize a vehicle, carrier, and (potentially) driver. |
safety inspection record | Record containing results of commercial vehicle safety inspection. |
safety status information | Safety information such as safety ratings, security ratings or flags, inspection summaries, and violation summaries. A unique identifier is included. Corresponds to the safety and security portion of CVISN "snapshots." The status information may be provided as a response to a real-time query or as a result of a standing request for updated information (subscription). This may also include information about non-U.S. fleets for use by U.S. authorities, and information regarding U.S. fleets made available to Mexican and Canadian authorities. The query flow is not explicitly shown. |
screening event record | Results of CVO electronic screening activity. |
targeted list | List of carriers, drivers, and/or vehicles of interest for enforcement purposes. |
trigger area | A geographic area a commercial motor vehicle crosses into, which initiates a request to compile and transmit a safety data message. May be associated with a time period. |
trigger area definition | Information that defines the desired trigger area for wireless roadside inspection safety data message submission. |
trigger area notification | Notification to activate wireless roadside inspection safety data message collection. |
trigger control | Controls to enable or disable a particular trigger. |
unique identifiers | Unique identifiers for the motor carrier, driver, and vehicle. This flow identifies the driver actually operating the vehicle in multi-driver scenarios. |
weigh-in-motion information | Information from commercial vehicle virtual weigh-in-motion systems including vehicle weight, vehicle dimensions, vehicle identification and driver identification. |
Goals and Objectives
Associated Planning Factors and Goals
Planning Factor | Goal |
---|---|
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; | Improve freight network |
B. Increase the safety of the transportation system for motorized and nonmotorized users; | Reduce fatalities and injuries |
Associated Objective Categories
Objective Category |
---|
Freight Management: Customer Satisfaction |
Freight Management: Travel Time Delay |
Freight Management: Travel Time Reliability |
Safety: Vehicle Crashes and Fatalities |
Associated Objectives and Performance Measures
Needs and Requirements
Need | Functional Object | Requirement | ||
---|---|---|---|---|
01 | Commercial Vehicle Administration agencies need to work in conjunction with enforcement agencies to define geographic areas for targeted safety and credentials screening and share that information with commercial fleets and their drivers in order to facilitate smoother and safer operations. | CV On-Board Safety and Security | 04 | The commercial vehicle shall provide information concerning a breach or tamper event on a commercial vehicle or its attached freight equipment to roadside check facilities and to the commercial fleet management center, the information includes identity, type of breach, location, and time. |
CVAC Credentials and Taxes Administration | 13 | The center shall issue special Oversize/Overweight and HAZMAT permits in coordination with other cognizant authorities. | ||
CVAC Information Exchange | 02 | The center shall exchange safety and credentials data among other commercial vehicle administration centers, including border clearance status, credentials information, credentials status information, driver records, accident reports, permit information, and safety status information. | ||
CVAC Safety and Security Administration | 03 | The center shall notify enforcement agencies of commercial vehicle safety violations by individual commercial vehicles, drivers, or carriers. | ||
06 | The center shall manage the citation records and provide the citations to enforcement agencies and the commercial fleet management center. | |||
CVCE Citation and Accident Electronic Recording | 04 | The roadside check facility equipment shall receive driver records from the commercial vehicle administration center to support driver identification and collection of driver credentials and history information. | ||
07 | The roadside check facility equipment shall notify the enforcement agency of a violation describing the statute or regulation that was violated and how it was violated. | |||
CVCE Safety and Security Inspection | 02 | The roadside check facility equipment shall receive the safety and security inspection and status information from the commercial vehicle administration center to include information such as safety ratings, inspection summaries, and violation summaries. | ||
02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. | CV On-Board Cargo Monitoring | 12 | The commercial vehicle shall accepts requests for identification data needed to support electronic screening. |
CV On-Board Safety and Security | 06 | The commercial vehicle shall provide information about previous attempts to disable the commercial vehicle to roadside check facilities. | ||
08 | The commercial vehicle shall record the results of roadside safety inspections. | |||
CVAC Information Exchange | 01 | The center shall exchange information with roadside check facilities, including credentials and credentials status information, safety status information, daily site activity data, driver records, and citations. | ||
CVAC Safety and Security Administration | 01 | The center shall provide commercial vehicle safety and security data to roadside check facilities. | ||
05 | The center shall receive citation records from roadside check facilities. | |||
09 | The center shall manage and distribute information about trigger areas where wireless inspections will occur. | |||
10 | The center shall monitor the condition of the commercial vehicle and driver using wireless communications at identified trigger areas. | |||
CVCE Citation and Accident Electronic Recording | 01 | The roadside check facility equipment shall record the results of roadside inspections carried using an inspector's hand held terminal interface. | ||
03 | The roadside check facility equipment shall forward results of the roadside inspections to the commercial vehicle administration center either as needed or on a periodic basis. These reports include accident reports, violation notifications, citations, and daily site activity logs. | |||
CVCE Safety and Security Inspection | 03 | The roadside check facility equipment shall provide an interface to inspectors in the field to update safety inspection data including overrides to the pull-in decisions made by the system. | ||
06 | The roadside check facility equipment shall receive driver records, accident reports, and citation records from the commercial vehicle administration center to support driver identification and access to driver credentials and history information. | |||
09 | The roadside check facility equipment shall forward results of the roadside safety inspections to the commercial vehicle administration center. | |||
10 | The roadside check facility equipment shall support wireless roadside inspections that are conducted remotely, forwarding data provided by the commercial vehicle via Field-Vehicle communications to the center that performs the safety assessment. | |||
Fleet Administration | 07 | The center shall monitor geographic trigger areas for wireless roadside inspection programs and distribute the trigger areas to their commercial vehicles. | ||
08 | The center shall provide fleet status information including safety status, routing information, current vehicle information, and emergency information to commercial vehicle operators. | |||
03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. | CV On-Board Cargo Monitoring | 01 | The commercial vehicle shall compute the location of the commercial vehicle and its freight equipment. |
04 | The commercial vehicle shall forward information concerning the freight equipment on to its fleet and freight management center as well as the roadside check facility. | |||
CV On-Board Electronic Screening Support | 01 | The commercial vehicle shall receive electronic screening (pass/pull-in) messages from the roadside check facilities and present them to the driver in either audible or visual forms. | ||
02 | The commercial vehicle shall respond to requests to provide data accumulated on-board the vehicle to roadside check facilities for inspection including driver logs, electronic identifiers, credentials, border clearance data, and other screening data such as cargo status, hazmat identifiers, out of service status, vehicle axle weight, vehicle weight, and time. | |||
03 | The commercial vehicle shall respond to requests to provide the identity, status and other information from the electronic cargo lock tag, if so equipped, to roadside check facilities, including border crossings. | |||
CV On-Board Safety and Security | 01 | The commercial vehicle shall receive safety and security messages from the roadside check facilities and present them to the driver in either audible or visual forms. | ||
02 | The commercial vehicle shall respond to requests to provide on-board safety inspection data to roadside check facilities including vehicle identification, driver logs, and characteristics data for initiating safety and security checking. Results of the inspection are read back into the on-board equipment. | |||
03 | The commercial vehicle shall monitor on-board systems pertaining to the safety and security of the vehicle, its driver, and its cargo/freight equipment; and provide the information to the driver, roadside check facilities, and commercial fleet management centers. | |||
07 | The commercial vehicle shall provide safety information at predetermined trigger areas using wireless communications. | |||
CVAC Credentials and Taxes Administration | 08 | The center shall provide credentials information about commercial vehicle operators and carriers to authorized requestors, including roadside check stations that determine when a vehicle should be pulled-in based on their credentials and their actual load/freight contents. | ||
CVAC Safety and Security Administration | 02 | The center shall collect and review safety inspection reports and violations from the roadside check facilities and pass on appropriate portions to other commercial vehicle administrative centers and commercial vehicle fleet operators. | ||
CVCE Citation and Accident Electronic Recording | 06 | The roadside check facility equipment shall read the driver identification card provided by the commercial vehicle driver and support cross-check of the identification data with driver records. | ||
04 | Commercial Vehicle Administration needs to measure the weight or dimensions of commercial vehicles while moving at mainline speeds in order to monitor and enforce weight or dimension restrictions. | CVCE Electronic Screening | 02 | The roadside check facility equipment shall differentiate between different types of vehicles and determine the number of axles, gross vehicle weight, and the identification of the vehicle and its cargo. |
CVCE Safety and Security Inspection | 01 | The roadside check facility equipment shall receive information concerning commercial vehicles and freight equipment approaching a facility that are being pulled in for safety and security inspections. | ||
04 | The roadside check facility equipment shall request and input electronic safety data from the commercial vehicle's electronic tag data. This includes identities, driver logs, on-board safety data, safety inspection records, commercial vehicle breach information, as well as freight equipment information. | |||
05 | The roadside check facility equipment shall send a pass/pull-in notification to the commercial vehicle and its driver based on the information received from the vehicle, the administration center, and the inspector. The message may be sent to the on-board equipment in the commercial vehicle or transmitted to the driver using equipment such as dynamic message signs, red-green lights, flashing signs, etc. | |||
08 | The roadside safety and security equipment shall read the driver identification card provided by the commercial vehicle driver and support cross-check of the identification data with driver records. | |||
CVCE Weigh-In-Motion | 01 | The roadside check facility equipment shall detect the presence of commercial vehicles and freight equipment approaching a facility. | ||
05 | Commercial Vehicle Management needs to know when a certain area has been identified as an area of focus or trigger areas by enforcement in order to inform the appropriate systems and stakeholders. | CVAC Information Exchange | 07 | The center shall inform fleet and freight management when certain geographic areas and time periods have been identified for screening and commercial vehicle enforcement. These trigger areas may be shared with the centers or with the field. |
Fleet Administration | 09 | The center shall send data to its commercial vehicles including dispatch, routing, trigger areas, and special instructions, including alerts and other advisories. |
Related Sources
Document Name | Version | Publication Date |
---|---|---|
ITS User Services Document | 1/1/2005 | |
Smart Roadside Initiative ConOps | 5/21/2012 |
Security
In order to participate in this service package, each physical object should meet or exceed the following security levels.
Physical Object Security | ||||
---|---|---|---|---|
Physical Object | Confidentiality | Integrity | Availability | Security Class |
Basic Commercial Vehicle | ||||
Commercial Vehicle Administration Center | High | High | Moderate | Class 4 |
Commercial Vehicle Check Equipment | High | High | Moderate | Class 4 |
Commercial Vehicle OBE | High | High | Moderate | Class 4 |
Driver Identification Card | High | Moderate | Moderate | Class 4 |
Enforcement Center | High | High | Moderate | Class 4 |
Fleet and Freight Management Center | High | High | Moderate | Class 4 |
Freight Equipment | Moderate | Moderate | Moderate | Class 2 |
Other CV Administration Centers | High | High | Moderate | Class 4 |
In order to participate in this service package, each information flow triple should meet or exceed the following security levels.
Information Flow Security | |||||
---|---|---|---|---|---|
Source | Destination | Information Flow | Confidentiality | Integrity | Availability |
Basis | Basis | Basis | |||
Basic Commercial Vehicle | Commercial Vehicle OBE | host commercial vehicle status | Moderate | Moderate | Moderate |
This can include some sensitive data. However, other data, such as vehicle location and motion will then be broadcast. There also may be proprietary information included in this. | This is used later on to determine whether a vehicle should request priority at an intersection. If this information is incorrect the vehicle may make false requests. All other flows that use the data from this flow have a MODERATE integrity requirement, therefore, this must also have a MODERATE integrity requirement. | This information would need to be available immediately for the application to work. | |||
Commercial Vehicle Administration Center | Commercial Vehicle Check Equipment | commercial vehicle permit information | Moderate | Moderate | Moderate |
Indicates company and individual vehicle permitting information, which is competitive commercial data. Observation of this information could provide leverage or business advantage over a particular carrier. | If incorrect a vehicle or carrier may be misled about what permits it has or needs, resulting in a potential for being improperly permitted and penalized. MODERATE and not HIGH because the impact is likely to be limited and can likely be easily addressed. | If this flow is inconsistently available there is probably little harm. It may be required for real-time CVO checking action, but the effect will apply to only one or at most, a limited number of drivers at a given location. | |||
Commercial Vehicle Administration Center | Commercial Vehicle Check Equipment | credentials information | High | Moderate | Moderate |
Credentials contain PII and proprietary information including trip data. This is private and competitive. If revealed, could provide leverage over carrier and/or vehicle. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. MODERATE and not HIGH because the impact should be limited. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. MODERATE and not HIGH because the impact should be limited. | |||
Commercial Vehicle Administration Center | Commercial Vehicle Check Equipment | credentials status information | High | Moderate | Moderate |
Credentials contain PII and proprietary information including trip data. This is private and competitive. If revealed, could provide leverage over carrier and/or vehicle. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. MODERATE and not HIGH because the impact should be limited. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. MODERATE and not HIGH because the impact should be limited. | |||
Commercial Vehicle Administration Center | Commercial Vehicle Check Equipment | cv driver record | High | High | Moderate |
Contains PII including driver identity, license and citations. If this were revealed then leverage could be had over the driver. | Incorrect or unavailable information could lead to a cited driver proceeding when he should not, or a clear driver improperly cited. In either case, this could be used to manipulate the driver's clearance. | Incorrect or unavailable information could lead to a cited driver proceeding when he should not, or a clear driver improperly cited. In either case, this could be used to manipulate the driver's clearance. Availability set to MODERATE because without this data, the CVCE operator will fall back on other processes. | |||
Commercial Vehicle Administration Center | Commercial Vehicle Check Equipment | safety status information | Moderate | Moderate | Moderate |
Credentials data are vehicle-specific even if they don't include PII, and thus between the inspection agency and the vehicle owner. Divulging this information could provide leverage or business advantage. | Incorrect or corrupted credentials data will affect the individual commercial vehicle and should be correct, but the scope of such corruption or errors should be limited. | If this information is not available it may slow processing of vehicles through the CVCE. | |||
Commercial Vehicle Administration Center | Commercial Vehicle Check Equipment | targeted list | Moderate | Moderate | Low |
Contains sensitive information about enforcement procedures and targets that if disclosed, could be used for business or other leverage over those affected carriers or entities. | Identification of enfocement targets and procedures should be correct or the point of this list is lost. | Without this flow inspections and enforcement will still happen. This flow also does not need constant updates to be effective. | |||
Commercial Vehicle Administration Center | Commercial Vehicle Check Equipment | trigger area notification | Low | High | Moderate |
Broadcast intended for all commercial vehicles in fleet; no harm if non-commercial vehicles receive this. | Trigger area messages indicate particular behaviors expected of commercial vehicles in the area; if corrupted, unavailable or forged commercial vehicles could be suspect to additional procedures or penalties which signficiantly affect their operations. | Trigger area messages indicate particular behaviors expected of commercial vehicles in the area; if corrupted, unavailable or forged commercial vehicles could be suspect to additional procedures or penalties which signficiantly affect their operations. There should be other mechanisms for learning this information, which is why availability is MODERATE and not HIGH. | |||
Commercial Vehicle Administration Center | Commercial Vehicle Check Equipment | trigger control | Moderate | Moderate | Low |
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. | ontrol flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. | |||
Commercial Vehicle Administration Center | Commercial Vehicle OBE | safety inspection record | Moderate | Moderate | Moderate |
Inspection results are vehicle-specific even if they don't include PII, and thus between the inspection agency and the vehicle owner. Divulging this information could provide leverage or business advantage. | Incorrect or corrupted inspection records will affect the individual commercial vehicle and should be correct, but the scope of such corruption or errors should be limited. | If this information is not available the commercial vehicle operator may be inconvenienced, though the armount of time lost may vary depending on the inspection regime. Could be LOW. | |||
Commercial Vehicle Administration Center | Commercial Vehicle OBE | trigger area notification | Low | High | Moderate |
Broadcast intended for all commercial vehicles in fleet; no harm if non-commercial vehicles receive this. | Trigger area messages indicate particular behaviors expected of commercial vehicles in the area; if corrupted, unavailable or forged commercial vehicles could be suspect to additional procedures or penalties which signficiantly affect their operations. | Trigger area messages indicate particular behaviors expected of commercial vehicles in the area; if corrupted, unavailable or forged commercial vehicles could be suspect to additional procedures or penalties which signficiantly affect their operations. There should be other mechanisms for learning this information, which is why availability is MODERATE and not HIGH. | |||
Commercial Vehicle Administration Center | Enforcement Center | citation | Moderate | Moderate | Moderate |
May contain PII, depending on the citation and type of information included could be HIGH. | Citation information should be correct and timely or the destination may be improperly informed of citation information, jeopardizing the operations of affected vehicles. | Citation information should be correct and timely or the destination may be improperly informed of citation information, jeopardizing the operations of affected vehicles. | |||
Commercial Vehicle Administration Center | Enforcement Center | commercial vehicle violation notification | High | Moderate | Low |
Contains PII and violation information, that if disclosed to parties other than the destination could provide leverage (business or personal) over the commercial vehicle. | Violation information needs to be correct or the commercial vehicle may be improperly penalized, or not when it should be. This is probably not a severe consequence however, so MODERATE. | This flow does not need to be real-time as there will be a backup (manual) mechanism, and buffering or batch uploads would also suffice. | |||
Commercial Vehicle Administration Center | Fleet and Freight Management Center | citation | Moderate | Moderate | Moderate |
May contain PII, depending on the citation and type of information included could be HIGH. | Citation information should be correct and timely or the destination may be improperly informed of citation information, jeopardizing the operations of affected vehicles. | Citation information should be correct and timely or the destination may be improperly informed of citation information, jeopardizing the operations of affected vehicles. | |||
Commercial Vehicle Administration Center | Fleet and Freight Management Center | trigger area | Moderate | Moderate | Low |
Not really sensitive, but provided intentionally only to carriers that register with the CVAC. MODERATE considering that only those that register are intended to receive this information. | Information associated with inspection areas, cargos and vehicle types should be correct so the FFMC and its associated vehicles undestand the inspection regime in which they operate. | This flow should not need to be updated often. Even if not functioning when an update should occur, the effect should be limited to those vehicles operating under the trigger conditions in between updates. Could possibly be MODERATE if trigger areas are very dynamic in a given area. | |||
Commercial Vehicle Administration Center | Fleet and Freight Management Center | trigger area notification | Low | High | Moderate |
This data is eventually broadcast to all commercial vehicles in fleet; no harm if non-commercial vehicles receive this. | Trigger area messages indicate particular behaviors expected of commercial vehicles in the area; if corrupted, unavailable or forged commercial vehicles could be suspect to additional procedures or penalties which signficiantly affect their operations. | Trigger area messages indicate particular behaviors expected of commercial vehicles in the area; if corrupted, unavailable or forged commercial vehicles could be suspect to additional procedures or penalties which signficiantly affect their operations. There should be other mechanisms for learning this information, which is why availability is MODERATE and not HIGH. | |||
Commercial Vehicle Administration Center | Other CV Administration Centers | commercial vehicle permit information | Moderate | Moderate | Moderate |
Indicates company and individual vehicle permitting information, which is competitive commercial data. Observation of this information could provide leverage or business advantage over a particular carrier. | If incorrect a vehicle or carrier may be misled about what permits it has or needs, resulting in a potential for being improperly permitted and penalized. MODERATE and not HIGH because the impact is likely to be limited and can likely be easily addressed. | If this flow is inconsistently available there is probably little harm. It may be required for real-time CVO checking action, but the effect will apply to only one or at most, a limited number of drivers at a given location. | |||
Commercial Vehicle Administration Center | Other CV Administration Centers | credentials information | High | High | Moderate |
Credentials contain PII and proprietary information including trip data. This is private and competitive. If revealed, could provide leverage over carrier and/or vehicle. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. HIGH because the impact should be extensive as this flow could include credentials information for large numbers of carriers and vehicles. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. MODERATE because while the impact could be extensive due to the number of vehicles involved, the flow can be reestablished and any issues fixed relatively quickly. | |||
Commercial Vehicle Administration Center | Other CV Administration Centers | credentials status information | High | High | Moderate |
Credentials contain PII and proprietary information including trip data. This is private and competitive. If revealed, could provide leverage over carrier and/or vehicle. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. HIGH because the impact should be extensive as this flow could include credentials information for large numbers of carriers and vehicles. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. MODERATE because while the impact could be extensive due to the number of vehicles involved, the flow can be reestablished and any issues fixed relatively quickly. | |||
Commercial Vehicle Administration Center | Other CV Administration Centers | safety status information | Moderate | Moderate | Moderate |
Credentials data are vehicle-specific even if they don't include PII, and thus between the inspection agency and the vehicle owner. Divulging this information could provide leverage or business advantage. | Incorrect or corrupted credentials data will affect the individual commercial vehicle and should be correct, but the scope of such corruption or errors should be limited. | If this information is not available it may slow processing of vehicles administered through equipment managed by other CVAC. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle Administration Center | citation | Moderate | Moderate | Moderate |
May contain PII, depending on the citation and type of information included could be HIGH. | Citation information should be correct and timely or the destination may be improperly informed of citation information, jeopardizing the operations of affected vehicles. | Citation information should be correct and timely or the destination may be improperly informed of citation information, jeopardizing the operations of affected vehicles. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle Administration Center | commercial vehicle violation notification | High | Moderate | Low |
Contains PII and violation information, that if disclosed to parties other than the destination could provide leverage (business or personal) over the commercial vehicle. | Violation information needs to be correct or the commercial vehicle may be improperly penalized, or not when it should be. This is probably not a severe consequence however, so MODERATE. | This flow does not need to be real-time as there will be a backup (manual) mechanism, and buffering or batch uploads would also suffice. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle Administration Center | daily site activity data | High | Moderate | Low |
Contains IDs and screening results. Given that this represents a large volume of IDs and results, capture of this information could provide leverage or advantage over a large number of vehicles and carriers. Also has vehicle IDs that could be used to track vehicle movements, not in real-time but in the long term, which could betray business practices. | This data is intended to be used to identify "problem vehicles." Any errors could lead to the wrong vehicles being targeted, which will have some operational impacts. | Not a real time report, only a batch upload. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle Administration Center | driver log | High | High | Moderate |
Driver log contains PII, personal identification and work conditions and by definition, log of hours worked. This is personal and competitive with regulatory use. It should be available only to the intended recipient. | Driver log data is covered under commercial regulatory schemes in most jurisdictions. Forgery of driver log data would have significant competitive implications, not to mention being a regulatory violation. | There are alternative mechanisms for exchanging the driver log, though all have a negative impact on the driver's time, which is why MODERATE and not LOW. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle Administration Center | on-board safety data | High | High | Moderate |
Contains PII of commercial vehicle operator, vehicle cargo as well as characteristics related to regulation and the vehicle's past history related to regulatory compliance. Interception, of this information would compromise the owner and/or operator of the commercial vehicle. | Contains PII of commercial vehicle operator as well as cargo, vehicle characteristics related to regulation and the vehicle's past history related to regulatory compliance. Corruption or falsification of this information would enable illegal operations of the commercial vehicle in question. | Alternative mechanisms exist to collect this data, though they require more manpower and negatively affect all parties involved with regard to time spent. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle Administration Center | roadside data message | Moderate | High | Moderate |
dicates company and individual vehicle identity. Observation of this information could provide leverage or business advantage over a particular carrier. | If incorrect the CVAC and its user may be misled about the identity of a vehicle or carrier, and consquently either penalize or fail to penalize the vehicle or carrier depending on his load, location and credentialing status. MODERATE and not HIGH because the impact is likely to be limited and can likely be easily addressed. | If this flow drops out the CVAC operator will be negatively affected. Could be LOW, depending on the perceived importance of these actions. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle Administration Center | weigh-in-motion information | Moderate | Moderate | Moderate |
Contains PII, including vehicle ID and driver ID. | Since this is used for regulation, must be correct to ensure compliance. | Real-time response may be needed depending on the regulatory scheme. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle Driver | CVO pass/pull-in message | Not Applicable | High | High |
This interface is also directly observable. | Data should be correct as it relates to CVO, however there is generally another mechanism to double-check this data, which is why it is MODERATE and not HIGH. If roadside mechanisms are not existant, then this would be HIGH. | Data should be available as it relates to CVO, however there is generally another mechanism to double-check this data, which is why it is MODERATE and not HIGH. If roadside mechanisms are not existant, then this would be HIGH. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle Inspector | CVO inspector information | Not Applicable | High | High |
Commercial Vehicle Operations human interfaces should not be casually viewable for competitive reasons. | Data should be correct as it relates to CVO, and given that this is the primary interface between inspector and inspection results, must be HIGH for both integrity and availability or the inspection regime breaks down. | Data should be correct as it relates to CVO, and given that this is the primary interface between inspector and inspection results, must be HIGH for both integrity and availability or the inspection regime breaks down. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle OBE | electronic screening request | Moderate | High | Moderate |
Request for screening does not contain PII, but implies a response that may contain PII. | In order to be acted upon the request must be correct, and if not acted upon manual processes may intervene. Additionally, MaM-type attacks may be used to mislead, confuse or otherwise harm the commercial vehicle or check equipment. | Without this flow manual processes may take over, but those have a time cost to the commercial vehicle. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle OBE | pass/pull-in | Low | High | Moderate |
This is directly observable data. | This message is directly acted upon. It should not be possible to spoof a border inspection station bypass. | Provision of the pull-in request will have other backup mechanisms in most instances, but should be correct to avoid confusion or incorrect action by the receiving vehicle. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle OBE | screening event record | Moderate | High | Moderate |
Screening results contain PII and details of the screening event, disclosure of which could harm the commercial vehicle or operator in question. | In order to be acted upon the request must be correct, and if not acted upon manual processes may intervene. Additionally, MaM-type attacks may be used to mislead, confuse or otherwise harm the commercial vehicle or check equipment. | Without this flow manual processes may take over, but those have a time cost to the commercial vehicle. | |||
Commercial Vehicle Check Equipment | Commercial Vehicle OBE | trigger area notification | Low | High | Moderate |
Broadcast intended for all commercial vehicles in fleet; no harm if non-commercial vehicles receive this. | Trigger area messages indicate particular behaviors expected of commercial vehicles in the area; if corrupted, unavailable or forged commercial vehicles could be suspect to additional procedures or penalties which signficiantly affect their operations. | Trigger area messages indicate particular behaviors expected of commercial vehicles in the area; if corrupted, unavailable or forged commercial vehicles could be suspect to additional procedures or penalties which signficiantly affect their operations. There should be other mechanisms for learning this information, which is why availability is MODERATE and not HIGH. | |||
Commercial Vehicle Check Equipment | Enforcement Center | commercial vehicle violation notification | High | Moderate | Low |
Contains PII and violation information, that if disclosed to parties other than the destination could provide leverage (business or personal) over the commercial vehicle. | Violation information needs to be correct or the commercial vehicle may be improperly penalized, or not when it should be. This is probably not a severe consequence however, so MODERATE. | This flow does not need to be real-time as there will be a backup (manual) mechanism, and buffering or batch uploads would also suffice. | |||
Commercial Vehicle Driver | Commercial Vehicle OBE | cv driver input | Moderate | Moderate | Moderate |
Commercial Vehicle Operations human interfaces should not be casually viewable for competitive and physical security reasons. | Data should be correct as it relates to CVO, however there is generally another mechanism to double-check this data, which is why it is MODERATE and not HIGH. | Flow should be available as it relates to CVO, however there is generally another mechanism through which this data might be received, which is why it is MODERATE and not HIGH. | |||
Commercial Vehicle Inspector | Commercial Vehicle Check Equipment | CVC override mode | Not Applicable | High | High |
Commercial Vehicle Operations human interfaces should not be casually viewable for competitive reasons. | Overrides must be correct and available or it would be possible for a vehicle that the inspector wants to see to pass through uninspected, which could have a safety impact. | Overrides must be correct and available or it would be possible for a vehicle that the inspector wants to see to pass through uninspected, which could have a safety impact. | |||
Commercial Vehicle Inspector | Commercial Vehicle Check Equipment | CVO inspector input | Not Applicable | High | High |
Commercial Vehicle Operations human interfaces should not be casually viewable for competitive reasons. | Data should be correct as it relates to CVO, and given that this is the primary interface between inspector and inspection results, must be HIGH for both integrity and availability or the inspection regime breaks down. | Data should be correct as it relates to CVO, and given that this is the primary interface between inspector and inspection results, must be HIGH for both integrity and availability or the inspection regime breaks down. | |||
Commercial Vehicle OBE | Commercial Vehicle Administration Center | driver log | High | High | Moderate |
Driver log contains PII, personal identification and work conditions and by definition, log of hours worked. This is personal and competitive with regulatory use. It should be available only to the intended recipient. | Driver log data is covered under commercial regulatory schemes in most jurisdictions. Forgery of driver log data would have significant competitive implications, not to mention being a regulatory violation. | There are alternative mechanisms for exchanging the driver log, though all have a negative impact on the driver's time, which is why MODERATE and not LOW. | |||
Commercial Vehicle OBE | Commercial Vehicle Administration Center | on-board safety data | High | High | Moderate |
Contains PII of commercial vehicle operator, vehicle cargo as well as characteristics related to regulation and the vehicle's past history related to regulatory compliance. Interception, of this information would compromise the owner and/or operator of the commercial vehicle. | Contains PII of commercial vehicle operator as well as cargo, vehicle characteristics related to regulation and the vehicle's past history related to regulatory compliance. Corruption or falsification of this information would enable illegal operations of the commercial vehicle in question. | Alternative mechanisms exist to collect this data, though they require more manpower and negatively affect all parties involved with regard to time spent. | |||
Commercial Vehicle OBE | Commercial Vehicle Administration Center | unique identifiers | High | High | Moderate |
Contains the identity of the commercial vehicle as well as particulars of its trip. Both competetive and regulatory, so deserving a high level of protection. | Incorrect or fraudelent data may be used to pursue criminal activity. | If this flow does not exist alternative mechanisms will have to be used, which exist but will be slower, negatively impacting the commercial vehicle. | |||
Commercial Vehicle OBE | Commercial Vehicle Check Equipment | driver log | High | High | Moderate |
Driver log contains PII, personal identification and work conditions and by definition, log of hours worked. This is personal and competitive with regulatory use. It should be available only to the intended recipient. | Driver log data is covered under commercial regulatory schemes in most jurisdictions. Forgery of driver log data would have significant competitive implications, not to mention being a regulatory violation. | There are alternative mechanisms for exchanging the driver log, though all have a negative impact on the driver's time, which is why MODERATE and not LOW. | |||
Commercial Vehicle OBE | Commercial Vehicle Check Equipment | freight equipment information | Moderate | Moderate | Moderate |
Will include proprietary and/or competitive information that should be disclosed only when necessary and to those with a need for the information. | Information must be accurate in order to be properly acted upon in support of screening or commercial vehicle safety processes. | Information must be timely in order to be properly acted upon in support of screening or commercial vehicle safety processes, though some of the information contained has alternative delivery mechanisms. | |||
Commercial Vehicle OBE | Commercial Vehicle Check Equipment | on-board safety data | High | High | Moderate |
Contains PII of commercial vehicle operator, vehicle cargo as well as characteristics related to regulation and the vehicle's past history related to regulatory compliance. Interception, of this information would compromise the owner and/or operator of the commercial vehicle. | Contains PII of commercial vehicle operator as well as cargo, vehicle characteristics related to regulation and the vehicle's past history related to regulatory compliance. Corruption or falsification of this information would enable illegal operations of the commercial vehicle in question. | Alternative mechanisms exist to collect this data, though they require more manpower and negatively affect all parties involved with regard to time spent. | |||
Commercial Vehicle OBE | Commercial Vehicle Check Equipment | screening event record | Moderate | High | Moderate |
Screening results contain PII and details of the screening event, disclosure of which could harm the commercial vehicle or operator in question. | In order to be acted upon the request must be correct, and if not acted upon manual processes may intervene. Additionally, MaM-type attacks may be used to mislead, confuse or otherwise harm the commercial vehicle or check equipment. | Without this flow manual processes may take over, but those have a time cost to the commercial vehicle. | |||
Commercial Vehicle OBE | Commercial Vehicle Check Equipment | unique identifiers | High | High | Moderate |
Contains the identity of the commercial vehicle as well as particulars of its trip. Both competetive and regulatory, so deserving a high level of protection. | Incorrect or fraudelent data may be used to pursue criminal activity. | If this flow does not exist alternative mechanisms will have to be used, which exist but will be slower, negatively impacting the commercial vehicle. | |||
Commercial Vehicle OBE | Commercial Vehicle Driver | CVO pass/pull-in message | Not Applicable | Moderate | Moderate |
This interface is also directly observable. | Data should be correct as it relates to CVO, however there is generally another mechanism to double-check this data, which is why it is MODERATE and not HIGH. | Flow should be available as it relates to CVO, however there is generally another mechanism through which this data might be received, which is why it is MODERATE and not HIGH. | |||
Commercial Vehicle OBE | Fleet and Freight Management Center | driver log | High | High | Moderate |
Driver log contains PII, personal identification and work conditions and by definition, log of hours worked. This is personal and competitive with regulatory use. It should be available only to the intended recipient. | Driver log data is covered under commercial regulatory schemes in most jurisdictions. Forgery of driver log data would have significant competitive implications, not to mention being a regulatory violation. | There are alternative mechanisms for exchanging the driver log, though all have a negative impact on the driver's time, which is why MODERATE and not LOW. | |||
Commercial Vehicle OBE | Fleet and Freight Management Center | on-board safety data | High | High | Moderate |
Contains PII of commercial vehicle operator, vehicle cargo as well as characteristics related to regulation and the vehicle's past history related to regulatory compliance. Interception, of this information would compromise the owner and/or operator of the commercial vehicle. | Contains PII of commercial vehicle operator as well as cargo, vehicle characteristics related to regulation and the vehicle's past history related to regulatory compliance. Corruption or falsification of this information would enable illegal operations of the commercial vehicle in question. | Alternative mechanisms exist to collect this data, though they require more manpower and negatively affect all parties involved with regard to time spent. | |||
Driver Identification Card | Commercial Vehicle OBE | cv driver credential | High | Moderate | Moderate |
Credentials contain PII and proprietary information. This is private and competitive. If revealed, could provide leverage over carrier and/or vehicle. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. MODERATE because the impact should be limited to a single vehicle per instance. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. MODERATE because the impact should be limited to a single vehicle per instance. | |||
Enforcement Center | Commercial Vehicle Administration Center | targeted list | Moderate | Moderate | Low |
Contains sensitive information about enforcement procedures and targets that if disclosed, could be used for business or other leverage over those affected carriers or entities. | Identification of enfocement targets and procedures should be correct or the point of this list is lost. | Without this flow inspections and enforcement will still happen. This flow also does not need constant updates to be effective. | |||
Enforcement Center | Commercial Vehicle Administration Center | trigger area definition | Low | High | Moderate |
This data is eventually broadcast to all commercial vehicles in fleet; no harm if non-commercial vehicles receive this. | Trigger area messages indicate particular behaviors expected of commercial vehicles in the area; if corrupted, unavailable or forged commercial vehicles could be suspect to additional procedures or penalties which signficiantly affect their operations. | Trigger area messages indicate particular behaviors expected of commercial vehicles in the area; if corrupted, unavailable or forged commercial vehicles could be suspect to additional procedures or penalties which signficiantly affect their operations. There should be other mechanisms for learning this information, which is why availability is MODERATE and not HIGH. | |||
Enforcement Center | Commercial Vehicle Administration Center | trigger control | Moderate | Moderate | Low |
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. | ontrol flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. | |||
Enforcement Center | Commercial Vehicle Check Equipment | information on violators | High | Moderate | Low |
Contains PII and violation information, that if disclosed to parties other than the destination could provide leverage (business or personal) over the commercial vehicle. | Violation information needs to be correct or the commercial vehicle may be improperly penalized, or not when it should be. This is probably not a severe consequence however, so MODERATE. | This flow does not need to be real-time as there will be a backup (manual) mechanism, and buffering or batch uploads would also suffice. | |||
Fleet and Freight Management Center | Commercial Vehicle Administration Center | driver log | High | High | Moderate |
Driver log contains PII, personal identification and work conditions and by definition, log of hours worked. This is personal and competitive with regulatory use. It should be available only to the intended recipient. | Driver log data is covered under commercial regulatory schemes in most jurisdictions. Forgery of driver log data would have significant competitive implications, not to mention being a regulatory violation. | There are alternative mechanisms for exchanging the driver log, though all have a negative impact on the driver's time, which is why MODERATE and not LOW. | |||
Fleet and Freight Management Center | Commercial Vehicle Administration Center | on-board safety data | High | High | Moderate |
Contains PII of commercial vehicle operator, vehicle cargo as well as characteristics related to regulation and the vehicle's past history related to regulatory compliance. Interception, of this information would compromise the owner and/or operator of the commercial vehicle. | Contains PII of commercial vehicle operator as well as cargo, vehicle characteristics related to regulation and the vehicle's past history related to regulatory compliance. Corruption or falsification of this information would enable illegal operations of the commercial vehicle in question. | Alternative mechanisms exist to collect this data, though they require more manpower and negatively affect all parties involved with regard to time spent. | |||
Fleet and Freight Management Center | Commercial Vehicle Administration Center | unique identifiers | High | High | Moderate |
Contains the identity of the commercial vehicle as well as particulars of its trip. Both competetive and regulatory, so deserving a high level of protection. | Incorrect or fraudelent data may be used to pursue criminal activity. | If this flow does not exist alternative mechanisms will have to be used, which exist but will be slower, negatively impacting the commercial vehicle. | |||
Fleet and Freight Management Center | Commercial Vehicle OBE | driver log | High | High | Moderate |
Driver log contains PII, personal identification and work conditions and by definition, log of hours worked. This is personal and competitive with regulatory use. It should be available only to the intended recipient. | Driver log data is covered under commercial regulatory schemes in most jurisdictions. Forgery of driver log data would have significant competitive implications, not to mention being a regulatory violation. | There are alternative mechanisms for exchanging the driver log, though all have a negative impact on the driver's time, which is why MODERATE and not LOW. | |||
Fleet and Freight Management Center | Commercial Vehicle OBE | safety inspection record | Moderate | Moderate | Moderate |
Inspection results are vehicle-specific even if they don't include PII, and thus between the inspection agency and the vehicle owner. Divulging this information could provide leverage or business advantage. | Incorrect or corrupted inspection records will affect the individual commercial vehicle and should be correct, but the scope of such corruption or errors should be limited. | If this information is not available the commercial vehicle operator may be inconvenienced, though the armount of time lost may vary depending on the inspection regime. Could be LOW. | |||
Fleet and Freight Management Center | Commercial Vehicle OBE | trigger area | Moderate | Moderate | Low |
Not really sensitive, but provided intentionally only to carriers that register with the CVAC. MODERATE considering that only those that register are intended to receive this information. | Information associated with inspection areas, cargos and vehicle types should be correct so the FFMC and its associated vehicles undestand the inspection regime in which they operate. | This flow should not need to be updated often. Even if not functioning when an update should occur, the effect should be limited to those vehicles operating under the trigger conditions in between updates. Could possibly be MODERATE if trigger areas are very dynamic in a given area. | |||
Fleet and Freight Management Center | Commercial Vehicle OBE | trigger area notification | Low | High | Moderate |
Broadcast intended for all commercial vehicles in fleet; no harm if non-commercial vehicles receive this. | Trigger area messages indicate particular behaviors expected of commercial vehicles in the area; if corrupted, unavailable or forged commercial vehicles could be suspect to additional procedures or penalties which signficiantly affect their operations. | Trigger area messages indicate particular behaviors expected of commercial vehicles in the area; if corrupted, unavailable or forged commercial vehicles could be suspect to additional procedures or penalties which signficiantly affect their operations. There should be other mechanisms for learning this information, which is why availability is MODERATE and not HIGH. | |||
Freight Equipment | Commercial Vehicle Check Equipment | freight equipment information | Moderate | Moderate | Moderate |
Will include proprietary and/or competitive information that should be disclosed only when necessary and to those with a need for the information. | Information must be accurate in order to be properly acted upon in support of screening or commercial vehicle safety processes. | Information must be timely in order to be properly acted upon in support of screening or commercial vehicle safety processes, though some of the information contained has alternative delivery mechanisms. | |||
Freight Equipment | Commercial Vehicle OBE | freight equipment information | Moderate | Moderate | Moderate |
Cargo status information, though internal to the vehicle, should probably be protected as part of a sound defense-in-depth strategy against malicious hacking. Freight Vehicle to CV OBE is considered on-board when the vehicle and freight are mated, so the same logic holds. | Cargo status information, though internal to the vehicle, should probably be protected as part of a sound defense-in-depth strategy against malicious hacking. Freight Vehicle to CV OBE is considered on-board when the vehicle and freight are mated, so the same logic holds. | On-board data exchanges, should be at least MODERATE so that on-board systems can fulfill their functions. Freight Vehicle to CV OBE is considered on-board when the vehicle and freight are mated, so the same logic holds. | |||
Other CV Administration Centers | Commercial Vehicle Administration Center | commercial vehicle permit information | Moderate | Moderate | Moderate |
Indicates company and individual vehicle permitting information, which is competitive commercial data. Observation of this information could provide leverage or business advantage over a particular carrier. | If incorrect a vehicle or carrier may be misled about what permits it has or needs, resulting in a potential for being improperly permitted and penalized. MODERATE and not HIGH because the impact is likely to be limited and can likely be easily addressed. | If this flow is inconsistently available there is probably little harm. It may be required for real-time CVO checking action, but the effect will apply to only one or at most, a limited number of drivers at a given location. | |||
Other CV Administration Centers | Commercial Vehicle Administration Center | credentials information | High | High | Moderate |
Credentials contain PII and proprietary information including trip data. This is private and competitive. If revealed, could provide leverage over carrier and/or vehicle. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. HIGH because the impact should be extensive as this flow could include credentials information for large numbers of carriers and vehicles. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. MODERATE because while the impact could be extensive due to the number of vehicles involved, the flow can be reestablished and any issues fixed relatively quickly. | |||
Other CV Administration Centers | Commercial Vehicle Administration Center | credentials status information | High | High | Moderate |
Credentials contain PII and proprietary information including trip data. This is private and competitive. If revealed, could provide leverage over carrier and/or vehicle. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. HIGH because the impact should be extensive as this flow could include credentials information for large numbers of carriers and vehicles.. | Incorrect or unavailable credentials information could delay clearance, could result in incorrect assessment of penalties. MODERATE because while the impact could be extensive due to the number of vehicles involved, the flow can be reestablished and any issues fixed relatively quickly. | |||
Other CV Administration Centers | Commercial Vehicle Administration Center | safety status information | Moderate | Moderate | Moderate |
Credentials data are vehicle-specific even if they don't include PII, and thus between the inspection agency and the vehicle owner. Divulging this information could provide leverage or business advantage. | Incorrect or corrupted credentials data will affect the individual commercial vehicle and should be correct, but the scope of such corruption or errors should be limited. | If this information is not available it may slow processing of vehicles through the CVCE. |
Standards
Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.
System Requirements
System Requirement | Need | ||
---|---|---|---|
001 | The system shall provide credentials information about commercial vehicle operators and carriers to authorized requestors, including roadside check stations that determine when a vehicle should be pulled-in based on their credentials and their actual load | 03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. |
002 | The system shall issue special Oversize/Overweight and HAZMAT permits in coordination with other cognizant authorities. | 01 | Commercial Vehicle Administration agencies need to work in conjunction with enforcement agencies to define geographic areas for targeted safety and credentials screening and share that information with commercial fleets and their drivers in order to facilitate smoother and safer operations. |
003 | The system shall exchange information with roadside check facilities, including credentials and credentials status information, safety status information, daily site activity data, driver records, and citations. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
004 | The system shall exchange safety and credentials data among other commercial vehicle administration centers, including border clearance status, credentials information, credentials status information, driver records, accident reports, permit information, | 01 | Commercial Vehicle Administration agencies need to work in conjunction with enforcement agencies to define geographic areas for targeted safety and credentials screening and share that information with commercial fleets and their drivers in order to facilitate smoother and safer operations. |
005 | The system shall inform fleet and freight management when certain geographic areas and time periods have been identified for screening and commercial vehicle enforcement. These trigger areas may be shared with the centers or with the field. | 05 | Commercial Vehicle Management needs to know when a certain area has been identified as an area of focus or trigger areas by enforcement in order to inform the appropriate systems and stakeholders. |
006 | The system shall provide commercial vehicle safety and security data to roadside check facilities. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
007 | The system shall collect and review safety inspection reports and violations from the roadside check facilities and pass on appropriate portions to other commercial vehicle administrative centers and commercial vehicle fleet operators. | 03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. |
008 | The system shall notify enforcement agencies of commercial vehicle safety violations by individual commercial vehicles, drivers, or carriers. | 01 | Commercial Vehicle Administration agencies need to work in conjunction with enforcement agencies to define geographic areas for targeted safety and credentials screening and share that information with commercial fleets and their drivers in order to facilitate smoother and safer operations. |
009 | The system shall receive citation records from roadside check facilities. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
010 | The system shall manage the citation records and provide the citations to enforcement agencies and the commercial fleet management center. | 01 | Commercial Vehicle Administration agencies need to work in conjunction with enforcement agencies to define geographic areas for targeted safety and credentials screening and share that information with commercial fleets and their drivers in order to facilitate smoother and safer operations. |
011 | The system shall manage and distribute information about trigger areas where wireless inspections will occur. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
012 | The system shall monitor the condition of the commercial vehicle and driver using wireless communications at identified trigger areas. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
013 | The system shall monitor geographic trigger areas for wireless roadside inspection programs and distribute the trigger areas to their commercial vehicles. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
014 | The system shall provide fleet status information including safety status, routing information, current vehicle information, and emergency information to commercial vehicle operators. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
015 | The system shall send data to its commercial vehicles including dispatch, routing, trigger areas, and special instructions, including alerts and other advisories. | 05 | Commercial Vehicle Management needs to know when a certain area has been identified as an area of focus or trigger areas by enforcement in order to inform the appropriate systems and stakeholders. |
016 | The system shall record the results of roadside inspections carried using an inspector's hand held terminal interface. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
017 | The system shall forward results of the roadside inspections to the commercial vehicle administration center either as needed or on a periodic basis. These reports include accident reports, violation notifications, citations, and daily site activity logs | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
018 | The system shall receive driver records from the commercial vehicle administration center to support driver identification and collection of driver credentials and history information. | 01 | Commercial Vehicle Administration agencies need to work in conjunction with enforcement agencies to define geographic areas for targeted safety and credentials screening and share that information with commercial fleets and their drivers in order to facilitate smoother and safer operations. |
019 | The system shall read the driver identification card provided by the commercial vehicle driver and support cross-check of the identification data with driver records. | 03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. |
04 | Commercial Vehicle Administration needs to measure the weight or dimensions of commercial vehicles while moving at mainline speeds in order to monitor and enforce weight or dimension restrictions. | ||
020 | The system shall notify the enforcement agency of a violation describing the statute or regulation that was violated and how it was violated. | 01 | Commercial Vehicle Administration agencies need to work in conjunction with enforcement agencies to define geographic areas for targeted safety and credentials screening and share that information with commercial fleets and their drivers in order to facilitate smoother and safer operations. |
021 | The system shall differentiate between different types of vehicles and determine the number of axles, gross vehicle weight, and the identification of the vehicle and its cargo. | 04 | Commercial Vehicle Administration needs to measure the weight or dimensions of commercial vehicles while moving at mainline speeds in order to monitor and enforce weight or dimension restrictions. |
022 | The system shall receive information concerning commercial vehicles and freight equipment approaching a facility that are being pulled in for safety and security inspections. | 04 | Commercial Vehicle Administration needs to measure the weight or dimensions of commercial vehicles while moving at mainline speeds in order to monitor and enforce weight or dimension restrictions. |
023 | The system shall receive the safety and security inspection and status information from the commercial vehicle administration center to include information such as safety ratings, inspection summaries, and violation summaries. | 01 | Commercial Vehicle Administration agencies need to work in conjunction with enforcement agencies to define geographic areas for targeted safety and credentials screening and share that information with commercial fleets and their drivers in order to facilitate smoother and safer operations. |
024 | The system shall provide an interface to inspectors in the field to update safety inspection data including overrides to the pull-in decisions made by the system. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
025 | The system shall request and input electronic safety data from the commercial vehicle's electronic tag data. This includes identities, driver logs, on-board safety data, safety inspection records, commercial vehicle breach information, as well as freight | 04 | Commercial Vehicle Administration needs to measure the weight or dimensions of commercial vehicles while moving at mainline speeds in order to monitor and enforce weight or dimension restrictions. |
026 | The system shall send a pass/pull-in notification to the commercial vehicle and its driver based on the information received from the vehicle, the administration center, and the inspector. The message may be sent to the on-board equipment in the commerci | 04 | Commercial Vehicle Administration needs to measure the weight or dimensions of commercial vehicles while moving at mainline speeds in order to monitor and enforce weight or dimension restrictions. |
027 | The system shall receive driver records, accident reports, and citation records from the commercial vehicle administration center to support driver identification and access to driver credentials and history information. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
028 | The system shall forward results of the roadside safety inspections to the commercial vehicle administration center. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
029 | The system shall support wireless roadside inspections that are conducted remotely, forwarding data provided by the commercial vehicle via Field-Vehicle communications to the center that performs the safety assessment. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
030 | The system shall detect the presence of commercial vehicles and freight equipment approaching a facility. | 04 | Commercial Vehicle Administration needs to measure the weight or dimensions of commercial vehicles while moving at mainline speeds in order to monitor and enforce weight or dimension restrictions. |
031 | The system shall compute the location of the commercial vehicle and its freight equipment. | 03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. |
032 | The system shall accepts requests for identification data needed to support electronic screening. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
033 | The system shall forward information concerning the freight equipment on to its fleet and freight management center as well as the roadside check facility. | 03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. |
034 | The system shall receive electronic screening (pass/pull-in) messages from the roadside check facilities and present them to the driver in either audible or visual forms. | 03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. |
035 | The system shall respond to requests to provide data accumulated on-board the vehicle to roadside check facilities for inspection including driver logs, electronic identifiers, credentials, border clearance data, and other screening data such as cargo sta | 03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. |
036 | The system shall respond to requests to provide the identity, status and other information from the electronic cargo lock tag, if so equipped, to roadside check facilities, including border crossings. | 03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. |
037 | The system shall receive safety and security messages from the roadside check facilities and present them to the driver in either audible or visual forms. | 03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. |
038 | The system shall respond to requests to provide on-board safety inspection data to roadside check facilities including vehicle identification, driver logs, and characteristics data for initiating safety and security checking. Results of the inspection ar | 03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. |
039 | The system shall monitor on-board systems pertaining to the safety and security of the vehicle, its driver, and its cargo/freight equipment; and provide the information to the driver, roadside check facilities, and commercial fleet management centers. | 03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. |
040 | The system shall provide information concerning a breach or tamper event on a commercial vehicle or its attached freight equipment to roadside check facilities and to the commercial fleet management center, the information includes identity, type of breac | 01 | Commercial Vehicle Administration agencies need to work in conjunction with enforcement agencies to define geographic areas for targeted safety and credentials screening and share that information with commercial fleets and their drivers in order to facilitate smoother and safer operations. |
041 | The system shall provide information about previous attempts to disable the commercial vehicle to roadside check facilities. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |
042 | The system shall provide safety information at predetermined trigger areas using wireless communications. | 03 | Commercial Vehicle Administration needs to have a vehicle credentialing capability that acquires electronic clearance information (including the commercial vehicle and clearance status) from vehicle as it passes the inspection site and allows exchange of relevant information with center systems. |
043 | The system shall record the results of roadside safety inspections. | 02 | Commercial Vehicle Administration needs to have a safety screening capability that acquires safety inspection data from commercial vehicles using electronic communications with fleets and with vehicles along the roadside. |