CVO01: Carrier Operations and Fleet Management
This service package manages a fleet of commercial vehicles. The Fleet and Freight Management Center monitors the vehicle fleet and can provide routes using either an in-house capability or an external provider. Routes generated by either approach are constrained by hazardous materials and other restrictions (such as height or weight). A route is electronically sent to the Commercial Vehicle with any appropriate dispatch instructions. The location of the Commercial Vehicle can be monitored by the Fleet and Freight Management Center and routing changes can be made depending on current road network conditions. This service package also supports maintenance of fleet vehicles with on-board monitoring equipment. Records of vehicle mileage, preventative maintenance and repairs are maintained.
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 OBE Owner | Expectation of Data Provision |
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 | Fleet and Freight Management Center Owner | Information Exchange Agreement |
Commercial Vehicle Administration Center Supplier | Commercial Vehicle Administration Center Owner | Warranty |
Commercial Vehicle Driver | Basic Commercial Vehicle | Operates |
Commercial Vehicle Driver | Commercial Vehicle OBE | Operates |
Commercial Vehicle Driver | Location and Time Data Source | 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 OBE Maintainer | System Maintenance Agreement |
Commercial Vehicle OBE Owner | Commercial Vehicle OBE Manager | Operations Agreement |
Commercial Vehicle OBE Owner | Fleet and Freight Management Center Owner | Information Exchange Agreement |
Commercial Vehicle OBE Supplier | Commercial Vehicle OBE 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 Manager | Fleet-Freight Manager | System Usage Agreement |
Fleet and Freight Management Center Owner | Commercial Vehicle Administration Center Owner | Information Exchange Agreement |
Fleet and Freight Management Center Owner | Commercial Vehicle OBE Owner | Information Exchange 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 |
Fleet-Freight Manager | Fleet and Freight Management Center | Operates |
Location and Time Data Source Maintainer | Location and Time Data Source | Maintains |
Location and Time Data Source Manager | Commercial Vehicle Driver | System Usage Agreement |
Location and Time Data Source Manager | Location and Time Data Source | Manages |
Location and Time Data Source Owner | Location and Time Data Source Maintainer | System Maintenance Agreement |
Location and Time Data Source Owner | Location and Time Data Source Manager | Operations Agreement |
Location and Time Data Source Supplier | Location and Time Data Source Owner | Warranty |
Transportation Information Center Maintainer | Transportation Information Center | Maintains |
Transportation Information Center Manager | Transportation Information Center | Manages |
Transportation Information Center Owner | Fleet and Freight Management Center Owner | Information Provision Agreement |
Transportation Information Center Owner | Transportation Information Center Maintainer | System Maintenance Agreement |
Transportation Information Center Owner | Transportation Information Center Manager | Operations Agreement |
Transportation Information Center Supplier | Transportation Information Center 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 Driver | Vehicle | The 'Commercial Vehicle Driver' represents the people that operate vehicles transporting goods, including both long haul trucks and local pick-up and delivery vans. This physical object is complementary to the Driver physical object in that it represents those interactions which are unique to Commercial Vehicle Operations. Information flowing from the Commercial Vehicle Driver includes those system inputs specific to Commercial Vehicle Operations. |
Commercial Vehicle OBE | Vehicle | The Commercial Vehicle On-Board Equipment (OBE) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials. 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. |
Fleet and Freight Management Center | Center | The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet. |
Fleet-Freight Manager | Center | The 'Fleet-Freight Manager' represents the people that are responsible for the dispatching and management of Commercial Vehicle fleets (e.g. traditional Fleet Managers) and Freight Equipment assets. It may be many people in a large tracking organization or a single person (owner driver) in the case of single vehicle fleets. The Fleet-Freight Manager provides instructions and coordination for Commercial Vehicles and Freight Equipment and receives the status of the vehicles and freight equipment in the fleet that they manage. |
Location and Time Data Source | ITS | The 'Location and Time Data Source' provides accurate position information. While a Global Positioning System (GPS) Receiver is the most common implementation, this physical object represents any technology that provides a position fix in three dimensions and time with sufficient accuracy. |
Transportation Information Center | Center | The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service. |
Includes Functional Objects:
Functional Object | Description | Physical Object |
---|---|---|
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 |
CV On-Board Trip Monitoring | 'CV On-Board Trip Monitoring' provides the capabilities to support fleet management with automatic vehicle location and automated mileage and fuel reporting and auditing. In addition, this equipment is used to monitor the planned route and notify the Fleet and Freight Management Center of any deviations. | Commercial Vehicle OBE |
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 |
Fleet Maintenance Management | 'Fleet Maintenance Management' tracks and monitors diagnostic results, vehicle mileage, inspection records, driver logs, and repair and service records collected from a commercial vehicle fleet equipped with on-board monitoring equipment. The data is used to develop preventative maintenance and repair schedules and repair and service records are maintained. | Fleet and Freight Management Center |
Includes Information Flows:
Information Flow | Description |
---|---|
commercial vehicle location data | Current vehicle location and related operational conditions data provided by a commercial vehicle. |
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 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. |
cv driver safety alert | Driver alerts based on operator safety sensors, including driver alertness. |
cv driver safety status | Information from on-board sensors regarding the commercial vehicle driver's ability to operate the vehicle safely, including information on driver alertness. |
cv repair status | Information about the completion of a repair to a commercial vehicle. |
driver to fleet request | Requests from the driver and vehicle for routing, payment, and enrollment information. |
fleet manager inquiry | This flow represents the tactile or auditory interface with ITS equipment containing an inquiry from fleet manager requesting data from commercial vehicle management system. |
fleet status | This flow represents the visual or auditory interface with ITS equipment containing fleet status information including enrollment status, safety status including inspection summaries, detailed inspection reports, and safety ratings, routing information, current vehicle information, and emergency information. |
fleet to driver update | Updated instructions to the driver including dispatch, routing, travel and parking information, and special instructions. Special instructions include incident management instruction, operational tasks, impacted transport orders in case of an incident, task descriptions with trip/route/load plan, transport order status information, driver information, vehicle information, cargo information and trip information. |
host commercial vehicle status | Information provided to the ITS on-board equipment from other systems on the Commercial Vehicle Platform. |
incident information for public | Report of current desensitized incident information prepared for public dissemination. |
location and time | The current geographic location in three dimensions (latitude, longitude, elevation) and the current time. |
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. |
on-board vehicle data | Information about the commercial vehicle stored on-board (for maintenance purposes, gate access, cargo status, lock status, etc.). The request flow is not explicitly shown. |
road network conditions | Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included. |
route restrictions | Information about routes, road segments, and areas that do not allow the transport of security sensitive hazmat cargoes or include other restrictions (such as height or weight limits). |
trip log | Driver's daily log, vehicle location, mileage, and trip activity (includes screening, inspection and border clearance event data as well as fare payments). The request flow is not explicitly shown. |
trip log information | This flow represents the tactile or auditory interface with ITS equipment containing the information entered into the trip log, or request for update. |
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 |
Associated Objective Categories 
Objective Category |
---|
Freight Management: Customer Satisfaction |
Freight Management: Travel Time Delay |
Associated Objectives and Performance Measures 

Needs and Requirements
Need | Functional Object | Requirement | ||
---|---|---|---|---|
01 | Fleet and Freight Management needs to know the location and status of its vehicles, drivers, and loads in order to efficiently manage and maintain its fleet. | CV On-Board Safety and Security | 10 | The commercial vehicle shall provide safety data to the commercial fleet management center upon request. |
CV On-Board Trip Monitoring | 01 | The commercial vehicle shall compute the location of the commercial vehicle and its freight equipment based on inputs from commercial vehicle measures (e.g. identity, distance traveled, etc.) and a positioning system. | ||
03 | The commercial vehicle shall provide warnings to the driver when the vehicle's location has deviated from its planned route. | |||
04 | The commercial vehicle shall warn the commercial vehicle fleet management center when the vehicle's location has deviated from its planned route. | |||
05 | The commercial vehicle shall maintain the driver's daily log, vehicle location, mileage, and trip activity (includes screening, inspection and border clearance event data as well as fare payments) and distribute it to the driver and to the commercial vehicle fleet management center upon request. | |||
06 | The commercial vehicle shall provide on-board vehicle data to the commercial vehicle fleet management center upon request - includes location, credentials, driver license citations, fuel purchase data, identity details, inspection data, log data, service records, safety systems diagnostics, and freight equipment data. | |||
07 | The commercial vehicle shall maintain the interface between the vehicle, its driver, and the commercial vehicle fleet management center for dispatch, routing, and special instructions as well as payment, and enrollment information. | |||
Fleet Administration | 01 | The center shall send data concerning enrollment of commercial vehicles for electronic clearance and tax filing to the appropriate commercial vehicle administration center. The data may include driver and vehicle identification, safety inspections/status, carrier credentials, related citations, and accident information. | ||
03 | The center shall support an interface with a map update provider, or other appropriate data sources, through which updates of digitized map data can be obtained and used as the background for commercial vehicle fleet administration - includes commercial vehicle specific data such as route or HAZMAT restrictions. | |||
04 | The center shall monitor the locations and progress of commercial vehicles against their planned routes and raise appropriate warnings based on route monitoring parameters. | |||
02 | Fleet and Freight Management needs access to accurate and current information about traffic road conditions in order to make informed decisions regarding its fleet. | Fleet Administration | 02 | The center shall obtain and manage commercial vehicle routes for its fleet of vehicles, taking into account route restrictions, advance payment of tolls, HAZMAT restrictions, current traffic and road conditions, loading zone conditions, and incident information provided by traveler information systems. |
14 | The center shall provide routes to its fleet of vehicles, taking into account route restrictions, advance payment of tolls, HAZMAT restrictions, current traffic and road conditions, and incident information. | |||
03 | Fleet and Freight Management needs to provide accurate and appropriate routes for its drivers and vehicles that include such factors as size and weight restrictions, times of day, and type of load, e.g. Hazmat loads. | CV On-Board Trip Monitoring | 02 | The commercial vehicle shall provide details of the route to the driver as received from the commercial vehicle fleet management center. |
Fleet Administration | 02 | The center shall obtain and manage commercial vehicle routes for its fleet of vehicles, taking into account route restrictions, advance payment of tolls, HAZMAT restrictions, current traffic and road conditions, loading zone conditions, and incident information provided by traveler information systems. | ||
04 | Fleet and Freight Management needs to monitor and record the mileage, repairs, and safety violations of its vehicles in order to efficiently manage its fleet. | CV On-Board Safety and Security | 10 | The commercial vehicle shall provide safety data to the commercial fleet management center upon request. |
Fleet Administration | 17 | The center shall maintain records of the mileage and time in service of its fleet of vehicles and freight equipment. | ||
18 | The center shall monitor the status of its fleet, including vehicles and freight equipment, for maintenance issues or repairs that may be needed. | |||
Fleet Maintenance Management | 01 | The fleet maintenance center shall collect and process operational and safety data from its fleet of commercial vehicles - data includes mileage data, repairs, diagnostic data, driver logs, and on-board safety system data. | ||
02 | The fleet maintenance center shall use data from its fleet of commercial vehicles to schedule maintenance and repair activities. | |||
05 | Fleet and Freight Management needs to make its fleet vehicle repair status available to the appropriate commercial vehicle administration agencies in order to update their credentials. | Fleet Administration | 19 | The center shall report required commercial vehicle repairs and other corrections of identified deficiencies to the appropriate commercial vehicle administration center. |
Fleet Maintenance Management | 01 | The fleet maintenance center shall collect and process operational and safety data from its fleet of commercial vehicles - data includes mileage data, repairs, diagnostic data, driver logs, and on-board safety system data. | ||
03 | The fleet maintenance center shall report required commercial vehicle repairs and other corrections of identified deficiencies to the appropriate commercial vehicle administration center. |
Related Sources
Document Name | Version | Publication Date |
---|---|---|
ITS User Services Document | 1/1/2005 |
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 OBE | High | High | High | Class 5 |
Fleet and Freight Management Center | High | High | Moderate | Class 4 |
Location and Time Data Source | Moderate | High | High | Class 5 |
Transportation Information Center | Low | Moderate | Moderate | Class 1 |
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 | Fleet and Freight Management Center | 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 | Fleet and Freight Management Center | 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 | Fleet and Freight Management Center | route restrictions | Low | Moderate | Low |
Should be public data, so no need for obfuscation. | Incorrect route restrictions data will not affect the FFMC but will affect the eventual user, and may result in a commercial vehicle being in a place the vehicle is not permitted. | This information should not need to be updated often. | |||
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 OBE | Commercial Vehicle Driver | cv driver safety alert | Low | High | High |
Unlikely that this information could be leveraged, unless the vehicle was being deliberately operated in an unsafe manner. | If this is incorrect or compromised, the driver may operate the vehicle in a non-optimal manner. A lack of alarm during a real safety issue (such as loss of driver awareness) could result in an accident, thus HIGH. | Safety related real-time data communicated on-board to the driver. This has a direct impact on the safe operation of the vehicle. | |||
Commercial Vehicle OBE | Commercial Vehicle Driver | trip log information | Moderate | Moderate | Moderate |
This data is informing the driver of operational information that is relevant to the operation of the vehicle. It may contain sensitive cargo information. | 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 | commercial vehicle location data | Moderate | Moderate | Moderate |
If observed, could be used by a criminal in the performance of a crime related to a commercial vehicle. May include PII, or pseudonymous information associated with PII. | Applications relying on this data will not function properly if the data is incorrect, so it must be protected commensurate to the value of the application. | Applications relying on this data will not function properly if the data is incorrect, so it must be protected commensurate to the value of the application. Location data is dynamic, so probably needs to be updated frequently. | |||
Commercial Vehicle OBE | Fleet and Freight Management Center | cv driver safety status | Moderate | High | Moderate |
Unlikely that this information could be leveraged, unless the vehicle was being deliberately operated in an unsafe manner. However, it is possible that this flow contains PII, such as driver identity, so it should be protected. | If this is incorrect or compromised, the FFMC may not know that the driver is operating the vehicle in a non-optimal manner. A lack of alarm during a real safety issue (such as loss of driver awareness) could result in an accident, thus HIGH. | Safety related real-time monitoring of vehicle and driver operational information. Probably less critical than on-board flows. Could be HIGH in some circumstances though. | |||
Commercial Vehicle OBE | Fleet and Freight Management Center | driver to fleet request | High | Moderate | Moderate |
Contains trip and payment details that if disclosed would compromise the driver, load and carrier. | Payment details need to be correct or the vehicle may be delayed. Likely limited in scope to individual vehicles that suffer corrupted messages. | If this flow is not available the commercial vehicle in question will be delayed and/or misrouted, which will inconvenience that vehicle, costing time and money. | |||
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. | |||
Commercial Vehicle OBE | Fleet and Freight Management Center | on-board vehicle data | Moderate | Moderate | Moderate |
Contains identifiers, location and other data related to freight systems. Interception of this information would compromise the owner and/or operator of the commercial vehicle. | Sensitivity of data will vary depending on what is being requested and what the commercial vehicle is carrying. In the most extreme case this could be data describing the condition of a hazardous material, which should be correct and timely to avoid the FFMC erroneously taking emergency-related actions. | Sensitivity of data will vary depending on what is being requested and what the commercial vehicle is carrying. In the most extreme case this could be data describing the condition of a hazardous material, which should be correct and timely to avoid the FFMC erroneously taking emergency-related actions. | |||
Commercial Vehicle OBE | Fleet and Freight Management Center | trip log | Moderate | Moderate | Moderate |
Contains post-actual vehicle positioning and operations data, that if reviewed end masse with similar data from other operators, could compromise business interests. | Needs to be timely and accurate to support commercial vehicle operations and regulations. | Needs to be timely and accurate to support commercial vehicle operations and regulations. | |||
Fleet and Freight Management Center | Commercial Vehicle Administration Center | cv repair status | Moderate | Moderate | Low |
Repair status implies uptime/downtime, which could be competitive information that if exposed to a third party could provide business leverage. | Some degree of assurance of correctness is necessary for the application to function. | Probably does not need to be active all the time, though it does need to function on state change. Generally LOW, though for large fleets may need to be MODERATE. | |||
Fleet and Freight Management Center | Commercial Vehicle OBE | fleet to driver update | High | Moderate | Moderate |
Contains PII, routing instructions and tasking, predictive of vehicle future, all of which if compromised would provide leverage over vehicle, driver and owner. | Contains a lot of information dedicated to the individual vehicle, any of which if incorrect or corrupted would negatively affect the vehicle and driver. | There is a great deal of information in this flow that would be challenging to assemble through other sources. A delay in receiving this information would negatively affect the vehicle and driver. | |||
Fleet and Freight Management Center | Fleet-Freight Manager | fleet status | Moderate | High | High |
Commercial Vehicle Operations human interfaces should not be casually viewable for competitive and physical security reasons. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | |||
Fleet-Freight Manager | Fleet and Freight Management Center | fleet manager inquiry | Moderate | High | High |
Commercial Vehicle Operations human interfaces should not be casually viewable for competitive and physical security reasons. | Data needs to be correct and available as it relates to CVO. | Data needs to be correct and available as it relates to CVO. | |||
Location and Time Data Source | Commercial Vehicle OBE | location and time | Moderate | High | High |
While time reference should be universally available, time reference coupled with vehicle location is tracking data. This flow is internal to a vehicle, but should probably be encrypted to discourage hacking and snooping on the vehicle bus. Thus MODERATE. | Location and time data is the basis for crash imminent safety and a host of other applications. Corruption of this flow could lead directly to a vehicle accident. | If this information is not available, crash imminent safety applications depending on this information will not function properly. | |||
Transportation Information Center | Fleet and Freight Management Center | incident information for public | Low | Moderate | Moderate |
This data is desensitized for public consumption. While this destination is not public, the information content and sensitivity is similar to other instances of this flow. | Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. | A few missed messages should not have a significant effect. However, most messages should make it through and the TMC should be able to know if the EMC has received a message. | |||
Transportation Information Center | Fleet and Freight Management Center | road network conditions | Low | Moderate | Moderate |
No harm should come from seeing this data, as it is eventually intended for public consumption. | While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. | WYO internally thinks Low or Moderate, depending on the application |
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 send data concerning enrollment of commercial vehicles for electronic clearance and tax filing to the appropriate commercial vehicle administration center. The data may include driver and vehicle identification, safety inspections/status | 01 | Fleet and Freight Management needs to know the location and status of its vehicles, drivers, and loads in order to efficiently manage and maintain its fleet. |
002 | The system shall obtain and manage commercial vehicle routes for its fleet of vehicles, taking into account route restrictions, advance payment of tolls, HAZMAT restrictions, current traffic and road conditions, loading zone conditions, and incident infor | 02 | Fleet and Freight Management needs access to accurate and current information about traffic road conditions in order to make informed decisions regarding its fleet. |
03 | Fleet and Freight Management needs to provide accurate and appropriate routes for its drivers and vehicles that include such factors as size and weight restrictions, times of day, and type of load, e.g. Hazmat loads. | ||
003 | The system shall support an interface with a map update provider, or other appropriate data sources, through which updates of digitized map data can be obtained and used as the background for commercial vehicle fleet administration - includes commercial v | 01 | Fleet and Freight Management needs to know the location and status of its vehicles, drivers, and loads in order to efficiently manage and maintain its fleet. |
004 | The system shall monitor the locations and progress of commercial vehicles against their planned routes and raise appropriate warnings based on route monitoring parameters. | 01 | Fleet and Freight Management needs to know the location and status of its vehicles, drivers, and loads in order to efficiently manage and maintain its fleet. |
005 | The system shall provide routes to its fleet of vehicles, taking into account route restrictions, advance payment of tolls, HAZMAT restrictions, current traffic and road conditions, and incident information. | 02 | Fleet and Freight Management needs access to accurate and current information about traffic road conditions in order to make informed decisions regarding its fleet. |
006 | The system shall maintain records of the mileage and time in service of its fleet of vehicles and freight equipment. | 04 | Fleet and Freight Management needs to monitor and record the mileage, repairs, and safety violations of its vehicles in order to efficiently manage its fleet. |
007 | The system shall monitor the status of its fleet, including vehicles and freight equipment, for maintenance issues or repairs that may be needed. | 04 | Fleet and Freight Management needs to monitor and record the mileage, repairs, and safety violations of its vehicles in order to efficiently manage its fleet. |
008 | The system shall report required commercial vehicle repairs and other corrections of identified deficiencies to the appropriate commercial vehicle administration center. | 05 | Fleet and Freight Management needs to make its fleet vehicle repair status available to the appropriate commercial vehicle administration agencies in order to update their credentials. |
009 | The system shall collect and process operational and safety data from its fleet of commercial vehicles - data includes mileage data, repairs, diagnostic data, driver logs, and on-board safety system data. | 04 | Fleet and Freight Management needs to monitor and record the mileage, repairs, and safety violations of its vehicles in order to efficiently manage its fleet. |
05 | Fleet and Freight Management needs to make its fleet vehicle repair status available to the appropriate commercial vehicle administration agencies in order to update their credentials. | ||
010 | The system shall use data from its fleet of commercial vehicles to schedule maintenance and repair activities. | 04 | Fleet and Freight Management needs to monitor and record the mileage, repairs, and safety violations of its vehicles in order to efficiently manage its fleet. |
011 | The system shall provide safety data to the commercial fleet management center upon request. | 01 | Fleet and Freight Management needs to know the location and status of its vehicles, drivers, and loads in order to efficiently manage and maintain its fleet. |
04 | Fleet and Freight Management needs to monitor and record the mileage, repairs, and safety violations of its vehicles in order to efficiently manage its fleet. | ||
012 | The system shall compute the location of the commercial vehicle and its freight equipment based on inputs from commercial vehicle measures (e.g. identity, distance traveled, etc.) and a positioning system. | 01 | Fleet and Freight Management needs to know the location and status of its vehicles, drivers, and loads in order to efficiently manage and maintain its fleet. |
013 | The system shall provide details of the route to the driver as received from the commercial vehicle fleet management center. | 03 | Fleet and Freight Management needs to provide accurate and appropriate routes for its drivers and vehicles that include such factors as size and weight restrictions, times of day, and type of load, e.g. Hazmat loads. |
014 | The system shall provide warnings to the driver when the vehicle's location has deviated from its planned route. | 01 | Fleet and Freight Management needs to know the location and status of its vehicles, drivers, and loads in order to efficiently manage and maintain its fleet. |
015 | The system shall warn the commercial vehicle fleet management center when the vehicle's location has deviated from its planned route. | 01 | Fleet and Freight Management needs to know the location and status of its vehicles, drivers, and loads in order to efficiently manage and maintain its fleet. |
016 | The system shall maintain the driver's daily log, vehicle location, mileage, and trip activity (includes screening, inspection and border clearance event data as well as fare payments) and distribute it to the driver and to the commercial vehicle fleet ma | 01 | Fleet and Freight Management needs to know the location and status of its vehicles, drivers, and loads in order to efficiently manage and maintain its fleet. |
017 | The system shall provide on-board vehicle data to the commercial vehicle fleet management center upon request - includes location, credentials, driver license citations, fuel purchase data, identity details, inspection data, log data, service records, saf | 01 | Fleet and Freight Management needs to know the location and status of its vehicles, drivers, and loads in order to efficiently manage and maintain its fleet. |
018 | The system shall maintain the interface between the vehicle, its driver, and the commercial vehicle fleet management center for dispatch, routing, and special instructions as well as payment, and enrollment information. | 01 | Fleet and Freight Management needs to know the location and status of its vehicles, drivers, and loads in order to efficiently manage and maintain its fleet. |