Fleet and Freight Management (Subsystem*)
The Fleet and Freight Management Subsystem (FFMS) provides the capability for commercial drivers and fleet or 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. In addition, the capability to purchase credentials electronically shall also be provided, with automated and efficient connections to financial institutions and regulatory agencies, along with post-trip automated mileage and fuel usage reporting. The Fleet and Freight Management Subsystem also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet. The subsystem also supports application for hazmat credentials and makes information about hazmat cargo available to agencies as required. Within this subsystem lies all the functionality associated with subsystems and components necessary to enroll and participate in international goods movement programs aimed at enhancing trade and transportation safety and security.Subsystem Interfaces Diagram
Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.
Functionality: Equipment Packages* and PSpecs*
- Commercial Vehicle and Freight Security (Equipment Package*)
PSpecs: - Fleet Administration (Equipment Package*)
PSpecs:- 2.1.1.1-Manage Commercial Fleet Electronic Credentials and Tax Filing
- 2.1.1.2-Manage Commercial Vehicle Routes
- 2.1.1.3-Provide Commercial Fleet Static Route
- 2.1.1.5-Manage Commercial Vehicle Fleet Map Data
- 2.1.1.6-Monitor Commercial Vehicle Route
- 2.1.2-Provide Commercial Vehicle Fleet Manager Interface
- 2.1.3-Provide Fleet Manager Commercial Vehicle Communications
- 2.1.5-Manage Driver Instruction Store
- 2.1.6-Manage Commercial Vehicle Incidents
- 2.6.1-Provide Commercial Vehicle Manager Tag Data Interface
- Fleet Credentials and Taxes Management and Reporting (Equipment Package*)
PSpecs: - Fleet HAZMAT Management (Equipment Package*)
PSpecs:- 2.1.1.4-Provide HAZMAT Incident Support
- Fleet Maintenance Management (Equipment Package*)
PSpecs: - Freight Administration and Management (Equipment Package*)
PSpecs: - Manage CV Driver Identification (Equipment Package*)
PSpecs:
Inputs/Outputs: Architecture Flows* and Data Flows*
Alerting and Advisory Systems
Fleet and Freight Management
- alerts and advisories (Architecture Flow*) - Assessments (general incident and vulnerability awareness information), advisories (identification of threats or recommendations to increase preparedness levels), and alerts (information on imminent or in-progress emergencies). This flow also provides supporting descriptive detail on incidents, threats, and vulnerabilities to increase preparedness and support effective response to threats against the surface transportation system.
Data Flows*:
Border Inspection Administration
Fleet and Freight Management
- clearance notification (Architecture Flow*) - Notification that cargo has been cleared through customs.
Data Flows*: - client id (Architecture Flow*) - A common identification number that can be used by all BIFA agencies and organizations to reference the carrier.
Data Flows*: - expedited clearance information (Architecture Flow*) - Includes carrier ID, importer ID, broker ID, conveyance ID, driver ID, service options, and associated information that is used to support expedited border clearance.
Data Flows*: - expedited clearance status (Architecture Flow*) - Status of expedited clearance registration.
Data Flows*: - manifest receipt confirmation (Architecture Flow*) - Confirmation that a shippers manifest has been received.
Data Flows*:
Commercial Vehicle
Fleet and Freight Management
- commercial vehicle breach (Architecture Flow*) - Information about a breach or tamper event on a Commercial Vehicle or its attached freight equipment which includes identity, type of breach, location, and time.
Data Flows*: - driver alert response (Architecture Flow*) - Commercial Vehicle Driver response to a breach alert for a Freight Equipment breach or tamper event.
Data Flows*: - driver log (Architecture Flow*) - A daily log showing hours in service for the current driver. The query flow is not explicitly shown.
Data Flows*: - driver to fleet request (Architecture Flow*) - Requests from the driver and vehicle for routing, payment, and enrollment information.
Data Flows*: - freight equipment information (Architecture Flow*) - 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, Bill of Lading, and sensor status.
Data Flows*: - identities (Architecture Flow*) - Identification information for the Commercial Vehicle (e.g., license plate number or USDOT number), Freight Equipment (e.g., container, chassis, or trailer identification), and Driver.
Data Flows*: - on-board safety data (Architecture Flow*) - Safety data measured by on-board sensors. Includes information about the vehicle, vehicle components, cargo, and driver. The query flow is not explicitly shown.
Data Flows*: - on-board vehicle data (Architecture Flow*) - Information about the commercial vehicle stored on-board (for maintenance purposes, gate access, cargo status, lock status, etc.).
Data Flows*: - route deviation alert (Architecture Flow*) - An alert that indicates a deviation from a planned route has been detected. The alert will contain the current Commercial Vehicle location and identity.
Data Flows*: - trip log (Architecture Flow*) - Driver's daily log, vehicle location, mileage, and trip activity (includes screening, inspection and border clearance event data as well as fare payments).
Data Flows*:
Commercial Vehicle Administration
Fleet and Freight Management
- accident report (Architecture Flow*) - Report of commercial vehicle safety accident. 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.
Data Flows*: - border clearance status (Architecture Flow*) - Notification regarding the crossing status of commercial freight shipment scheduled to enter the U.S. Includes portions of border agency and transportation agency clearance results, as they become available.
Data Flows*: - citation (Architecture Flow*) - 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.
Data Flows*: - commercial vehicle permit (Architecture Flow*) - Permit for oversize, overweight, or hazmat shipments.
Data Flows*: - compliance review report (Architecture Flow*) - Report containing results of carrier compliance review, including concomitant out-of-service notifications, carrier warnings/notifications. The information may be provided as a response to a real-time query of proactively by the source. The query flow is not explicitly shown.
Data Flows*: - credentials information (Architecture Flow*) - 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.
Data Flows*: - credentials status information (Architecture Flow*) - 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.
Data Flows*: - cv driver record (Architecture Flow*) - 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.
Data Flows*: - route restrictions (Architecture Flow*) - 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).
Data Flows*: - safety inspection report (Architecture Flow*) - Report containing results of commercial vehicle safety inspection. 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.
Data Flows*: - safety status information (Architecture Flow*) - 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.
Data Flows*: - trigger area (Architecture Flow*) - 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.
Data Flows*: - trigger area notification (Architecture Flow*) - Notification to activate wireless roadside inspection safety data message collection.
Data Flows*:
Driver Identification Card
Fleet and Freight Management
- cv driver credential (Architecture Flow*) - 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.
Data Flows*:
Emergency Management
Fleet and Freight Management
- disable commercial vehicle (Architecture Flow*) - A request that a specific commercial vehicle should be safely disabled.
Data Flows*: - hazmat information request (Architecture Flow*) - Request for information about a particular hazmat load.
Data Flows*:
Fleet and Freight Management
Alerting and Advisory Systems
- fleet and freight threat information (Architecture Flow*) - Information about threats detected by commercial vehicle fleet and freight operators. The threats include incidents involving commercial vehicles (i.e. hijacking), unusual activities observed by commercial vehicle operators (i.e. truck parked under a bridge), and incidents involving freight equipment (i.e. freight equipment tampering).
Data Flows*:
Fleet and Freight Management
Border Inspection Administration
- expedited clearance registration (Architecture Flow*) - Registration of the importer, carrier, conveyance, and driver, as applicable, for border clearance programs such as FAST, Customs Self Assessment (Canada), C-TPAT (US), PIP (Canada), ACI (Canada), and ACE (US). Includes electronic filing of forms and associated payment.
Data Flows*: - manifest data (Architecture Flow*) - Identifies Port of Entry, date, and information on carrier and goods, origin, etc.
Data Flows*:
Fleet and Freight Management
Commercial Vehicle
- commercial vehicle disable (Architecture Flow*) - This flow safely disables a specific commercial vehicle.
Data Flows*: - driver log (Architecture Flow*) - A daily log showing hours in service for the current driver. The query flow is not explicitly shown.
Data Flows*: - expected driver identity characteristics (Architecture Flow*) - Driver identification information e.g. encrypted PIN codes issued to drivers, encrypted driver biometric parameters.
Data Flows*: - fleet to driver update (Architecture Flow*) - Updated instructions to the driver including dispatch, routing, and special instructions.
Data Flows*: - on-board vehicle request (Architecture Flow*) - Request for on-board vehicle data.
Data Flows*: - safety inspection record (Architecture Flow*) - Record containing results of commercial vehicle safety inspection.
Data Flows*: - trigger area (Architecture Flow*) - 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.
Data Flows*: - trigger area notification (Architecture Flow*) - Notification to activate wireless roadside inspection safety data message collection.
Data Flows*: - trip identification number (Architecture Flow*) - The unique trip load number for a specific cross-border shipment.
Data Flows*: - trip log request (Architecture Flow*) - Request for trip log.
Data Flows*:
Fleet and Freight Management
Commercial Vehicle Administration
- audit data (Architecture Flow*) - Information to support a tax audit.
Data Flows*: - credential application (Architecture Flow*) - Application for commercial vehicle credentials. Authorization for payment is included.
Data Flows*: - cv repair status (Architecture Flow*) - Information about the completion of a repair to a commercial vehicle.
Data Flows*: - driver log (Architecture Flow*) - A daily log showing hours in service for the current driver. The query flow is not explicitly shown.
Data Flows*: - on-board safety data (Architecture Flow*) - Safety data measured by on-board sensors. Includes information about the vehicle, vehicle components, cargo, and driver. The query flow is not explicitly shown.
Data Flows*: - request for permit (Architecture Flow*) - Request by fleet management for oversize, overweight, or hazmat permit.
Data Flows*: - tax filing (Architecture Flow*) - Commercial vehicle tax filing data. Authorization for payment is included.
Data Flows*:
Fleet and Freight Management
Emergency Management
- alarm (Architecture Flow*) - Information about a Commercial Vehicle or Freight Equipment breach, non-permitted security sensitive hazmat detected at the roadside, route deviation, or Commercial Vehicle Driver / Commercial Vehicle / Freight Equipment assignment mismatches which includes the location of the Commercial Vehicle and appropriate identities.
Data Flows*: - hazmat information (Architecture Flow*) - Information about a particular hazmat load including nature of the load and unloading instructions. May also include hazmat vehicle route and route update information.
Data Flows*:
Fleet and Freight Management
Fleet-Freight Manager
- fleet and freight alerts (Architecture Flow*) - This flow represents the visual or auditory interface with ITS equipment containing security alert status information regarding commercial vehicle fleets and freight equipment.
Data Flows*: - fleet status (Architecture Flow*) - 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.
Data Flows*:- tffm-confirm_enrollment_data_stored
- tffm-data_input_request
- tffm-driver_route_instructions
- tffm-enrollment_confirmation
- tffm-enrollment_payment_confirmation
- tffm-freight_data_input_request
- tffm-other_data_request
- tffm-output_tag_data
- tffm-preclearance_results
- tffm-roadside_activity_report
- tffm-route_data
Fleet and Freight Management
Freight Equipment
- freight monitoring parameters (Architecture Flow*) - Parameters to configure the Freight Equipment for event reporting and keep alive functions.
Data Flows*:
Fleet and Freight Management
Information Service Provider
- route request (Architecture Flow*) - Request for a tailored route based on given constraints.
Data Flows*: - toll data request (Architecture Flow*) - Request made to obtain toll schedule information or pay a toll in advance. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
Data Flows*:
Fleet and Freight Management
Intermodal Freight Depot
- booking status (Architecture Flow*) - Status of the freight transport booking that includes the identities of the Commercial Vehicle and driver who will pick-up the freight or a request for more information from the originator.
Data Flows*: - freight transportation status (Architecture Flow*) - A time-stamped status of a freight shipment as it passes through the supply chain from manufacturer through arrival at its final destination; including cargo movement logs, routing information, and cargo ID’s.
Data Flows*:
Fleet and Freight Management
Intermodal Freight Shipper
- booking status (Architecture Flow*) - Status of the freight transport booking that includes the identities of the Commercial Vehicle and driver who will pick-up the freight or a request for more information from the originator.
Data Flows*: - freight breach (Architecture Flow*) - Information about a breach or tamper event on Freight Equipment which includes identity, type of breach, location, and time.
Data Flows*: - freight transportation status (Architecture Flow*) - A time-stamped status of a freight shipment as it passes through the supply chain from manufacturer through arrival at its final destination; including cargo movement logs, routing information, and cargo ID’s.
Data Flows*:
Fleet and Freight Management
Map Update Provider
- map update request (Architecture Flow*) - Request for a map update which could include a new underlying map or map layer updates.
Data Flows*:
Fleet and Freight Management
Payment Administration
- toll data request (Architecture Flow*) - Request made to obtain toll schedule information or pay a toll in advance. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
Data Flows*:
Fleet-Freight Manager
Fleet and Freight Management
- alert response (Architecture Flow*) - This flow represents the tactile or auditory interface with ITS equipment containing the response by a Commercial Vehicle Driver or Fleet-Freight Manager that confirms or cancels an alert.
Data Flows*: - fleet manager inquiry (Architecture Flow*) - This flow represents the tactile or auditory interface with ITS equipment containing an inquiry from fleet manager requesting data from commercial vehicle management system.
Data Flows*:- fffm-carrier_number
- fffm-driver_number
- fffm-enrollment_payment_request
- fffm-enrollment_request
- fffm-freight_data_input
- fffm-other_data_input
- fffm-preclearance_data
- fffm-request_driver_route_instructions
- fffm-request_on_board_vehicle_data
- fffm-request_tag_data_output
- fffm-roadside_activity_report_request
- fffm-route_data
- fffm-route_function_request
- fffm-trip_identity
- fffm-update_driver_route_instructions
- fffm-vehicle_number
Freight Equipment
Fleet and Freight Management
- freight breach (Architecture Flow*) - Information about a breach or tamper event on Freight Equipment which includes identity, type of breach, location, and time.
Data Flows*: - freight equipment information (Architecture Flow*) - 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, Bill of Lading, and sensor status.
Data Flows*:
Information Service Provider
Fleet and Freight Management
- incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*: - road network conditions (Architecture Flow*) - 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 architecture 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 along with a definition of the links, nodes, and routes that make up the road network.
Data Flows*: - route plan (Architecture Flow*) - Tailored route provided by ISP in response to a specific request.
Data Flows*: - toll data (Architecture Flow*) - Current toll schedules for different types of vehicles as well as advanced toll payment information.
Data Flows*:
Intermodal Freight Depot
Fleet and Freight Management
- freight transportation status (Architecture Flow*) - A time-stamped status of a freight shipment as it passes through the supply chain from manufacturer through arrival at its final destination; including cargo movement logs, routing information, and cargo ID’s.
Data Flows*:
Intermodal Freight Shipper
Fleet and Freight Management
- breach response (Architecture Flow*) - This is an Intermodal Freight Shipper's response to a breach or tamper event of their freight equipment. There maybe instructions for handling of the shipment, possible re-routing or pickup.
Data Flows*: - freight transport booking (Architecture Flow*) - Booking information for the transport of freight that includes company, contact information, point of origin, pick-up location, drop-off location, and freight equipment identifier.
Data Flows*: - freight transportation status (Architecture Flow*) - A time-stamped status of a freight shipment as it passes through the supply chain from manufacturer through arrival at its final destination; including cargo movement logs, routing information, and cargo ID’s.
Data Flows*:
Map Update Provider
Fleet and Freight Management
- map updates (Architecture Flow*) - Map update which could include a new underlying static or real-time map or map layer(s) update.
Data Flows*:
Payment Administration
Fleet and Freight Management
- toll data (Architecture Flow*) - Current toll schedules for different types of vehicles as well as advanced toll payment information.
Data Flows*:

