GITNUXSOFTWARE ADVICE
Transportation LogisticsTop 10 Best Dot Tracking Software of 2026
Ranking roundup of dot tracking software options for fleet teams, with comparisons of Verizon Connect, Omnitracs, and Azuga.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Verizon Connect is the strongest fit for fleet analytics teams that need driver and route timelines aligned for DOT compliance reviews, whereas Azuga works better for smaller fleets wanting telematics-backed DOT tracking with structured exceptions and assignment-aware workflows.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Verizon Connect
Correlation of telematics movement with driver log review workflows reduces manual timeline reconciliation.
Built for fits when fleet analytics teams need driver and route timelines aligned for compliance review..
Omnitracs
Editor pickCertified review workflows that route corrections and approvals through role-based queues and audit trails.
Built for fits when enterprise fleets need governed driver status workflows tied to operational dispatch..
Azuga
Editor pickDiagnostic event correlation from vehicle systems into driver and vehicle compliance exception workflows.
Built for fits when fleets need telematics-backed dot tracking with structured exceptions and assignment-aware workflows..
Comparison Table
Verizon Connect
enterpriseEnterprise fleet tracking platform with DOT compliance and vehicle maintenance tools.
Correlation of telematics movement with driver log review workflows reduces manual timeline reconciliation.
Verizon Connect records vehicle movement and operational events from connected vehicle hardware, then maps those events into driver and trip context for review. The compliance workflow is built around operational edits and certification steps, which reduces manual rework when logs require correction. Geofencing and stop-level location data help analysts validate yard movements and route conformance against operational expectations.
A tradeoff appears when tracking accuracy depends on telematics quality and device health, because intermittent connectivity can create gaps analysts must reconcile. Verizon Connect fits best when analytics teams need the dot tracking timeline to stay aligned with dispatch, telematics events, and driver records across multiple fleets.
- +Event correlation links route movement and exceptions to log review
- +Role-based access and change history support governance for log workflows
- +Geofence and stop signals improve yard and location-based validation
- +Export and integration paths support analytics pipelines
- –Tracking gaps can occur when telematics connectivity is unstable
- –Correction workflows require disciplined setup to avoid mismatched edits
- –Some analytics views depend on configuration of event-to-driver mapping
- –Deep troubleshooting takes more time than basic dashboard usage
Compliance operations teams
Audit and correct driver log timelines
Fewer manual corrections
Fleet dispatch analysts
Validate route exceptions and dwell
Faster exception triage
Show 2 more scenarios
Safety and training managers
Review location-based inspection timing
Targeted coaching plans
Managers align field events with driver activity to flag patterns that match recurring compliance risks.
Data engineering teams
Send movement events to analytics
Consistent reporting datasets
Teams export event history and map it into downstream reporting datasets for fleet KPIs.
Best for: Fits when fleet analytics teams need driver and route timelines aligned for compliance review.
Omnitracs
enterpriseTransportation fleet management offering ELD, routing, and compliance software.
Certified review workflows that route corrections and approvals through role-based queues and audit trails.
Omnitracs processes device-derived signals into driver and vehicle status events that can be reviewed and governed by fleet managers and compliance staff. The workflow focus shows up in its handling of role-based responsibilities for review, correction, and sign-off on driver records. Integration depth is strongest when Omnitracs is used as part of a broader fleet management setup, because data flows are designed to support daily dispatch, yard operations, and exception follow-up. API and automation coverage tends to be evaluated by checking how events, driver status changes, and alerts are exposed to downstream systems.
A practical tradeoff is that the governance and certification workflow adds operational overhead compared with simpler analytics-first dot tracking tools. Omnitracs is best used when compliance review, correction, and audit trails must align to internal processes and when multiple roles need consistent handling of exceptions. Fleets that want quick experimentation with event dashboards without formal review queues often find the workflow-driven approach heavier than expected.
- +Enterprise workflow design for driver record review and exception handling
- +Event trails support audit-style investigation across driver and vehicle changes
- +Tight integration with fleet operations processes like dispatch and yard activity
- +Administrative governance for roles involved in correction and certification
- –Workflow governance can feel heavy for small teams using analytics alone
- –App-level customization depends on implementation choices and integrations
- –Setup and configuration require disciplined operational ownership
Compliance operations teams
Manage daily driver record exceptions
Faster exception resolution with audit trail
Enterprise fleet managers
Coordinate compliance with dispatch
More consistent daily fleet execution
Show 2 more scenarios
Telematics and systems integration
Stream events to downstream systems
Lower manual reconciliation effort
Integrate driver and vehicle status events into existing analytics and case management.
Operations leadership
Oversee multi-role review accountability
Clear accountability for compliance actions
Enforce role separation for review, correction, and sign-off responsibilities across teams.
Best for: Fits when enterprise fleets need governed driver status workflows tied to operational dispatch.
Azuga
SMBFleet tracking software providing GPS monitoring, driver behavior analysis, and DOT compliance.
Diagnostic event correlation from vehicle systems into driver and vehicle compliance exception workflows.
Azuga’s dot tracking fit is strongest for fleet operators that want telematics-driven tracking rather than browser-style event analytics. Location updates and vehicle diagnostic data feed compliance and operational exception views, which reduces manual stitching across systems. Administration supports role separation for dispatch and compliance roles, and audit-oriented visibility into changes made to driver and vehicle records.
A key tradeoff is that Azuga’s tracking depth depends on vehicle telematics connectivity, so teams without installed hardware or vehicle integration paths will not get the same data completeness. Azuga is a strong choice for yard moves and route compliance monitoring when the fleet already runs a telematics gateway workflow and needs standardized exception handling.
- +Telematics-linked location and diagnostic events for compliance workflows
- +Role separation for dispatch and compliance operations
- +Exception handling tied to driver and vehicle assignment changes
- +Configurable data capture behavior by vehicle integration type
- –Full tracking quality depends on vehicle telematics connectivity
- –Deep configuration requires governance discipline across fleet roles
- –Reporting customization can lag behind rule-specific field needs
- –Integration testing takes time when mixing heterogeneous vehicle ECUs
Fleet compliance teams
Detect compliance exceptions by driver assignment
Fewer unresolved compliance anomalies
Dispatch operations
Monitor route adherence across vehicles
Tighter route control
Show 2 more scenarios
Fleet maintenance planners
Track diagnostic events tied to vehicles
Reduced inspection misses
Maintenance teams use diagnostic signals to trigger inspections and follow-up actions by asset.
Driver management teams
Standardize inspection and status workflows
More consistent driver records
Driver-facing workflows keep inspection and status handling consistent across multiple vehicle types.
Best for: Fits when fleets need telematics-backed dot tracking with structured exceptions and assignment-aware workflows.
Desmos
educationOnline graphing calculator that supports plotted points, regressions, and visual tracking of points on mathematical graphs.
Configurable event and property capture in a simple tracking script that reduces instrumentation plumbing.
Desmos provides dot tracking and event collection through a lightweight tracking script designed for web and app instrumentation. It focuses on analytics via events and filters, with built-in reporting views for common funnels and cohorts.
Desmos supports client-side tagging with configurable event names and properties, and it routes collected data to analysis dashboards without requiring a full data warehouse setup. The product fits teams that want fast iteration on event definitions and minimal plumbing for standard web analytics workflows.
- +Event naming and property capture via configurable tracking code
- +Built-in funnel and cohort views for standard behavioral analysis
- +Fast iteration on client-side instrumentation without backend changes
- +Clear session-level and user-level reporting patterns
- –Limited visibility into raw ingestion diagnostics and processing steps
- –Advanced governance controls for multi-team access are not prominent
- –Customization beyond core reporting can require additional engineering
- –API-first automation and extensibility surface is narrower than peers
Best for: Fits when analytics teams need quick web event instrumentation and built-in funnels.
Motive
SMBFleet management system providing ELD compliance, GPS tracking, and vehicle diagnostics.
Inspection and driver action messaging tied to the same event timeline used for post-incident log review.
Motive delivers dot tracking for commercial fleets by ingesting telematics events and mapping them to driver, vehicle, and trip timelines. It supports operational workflows around inspection readiness and daily logs, with configurable messaging for driver actions and exception handling.
Admin teams can segment fleets and users to control access to reports and event review while keeping event provenance tied to the underlying telemetry. Integration depth shows up through data exports and telematics-to-back-office handoff used for compliance and operational analytics.
- +Event timeline ties driver actions to telemetry records for investigation workflows
- +Fleet-wide configuration supports consistent tracking behavior across large operations
- +Role-based access limits who can view or edit log-related content
- +Exception and message workflows reduce missed driver tasks
- –Exception review takes more clicks when multiple events overlap in time
- –Detailed configuration can require governance discipline across regions and fleets
Best for: Fits when fleets need driver action workflows tied to telematics event review for compliance and operations.
EROAD
enterpriseElectronic logging and fleet management platform for HOS compliance and weight-mile tax reporting.
Edit certification workflows that preserve driver status correction history tied to compliance records.
ERoad fits fleet operators that need telematics-driven data flows with compliance-focused tracking workflows. It centers on Electronic Logging Device workflows, including records of duty status support and qualification for driving hours processes used in day-to-day operations.
EROAD also supports geofencing-driven events such as yard move and can align driver activity edits with edit certification workflows used for audit trails. Integration depth is driven by fleet telemetry collection and device connectivity patterns rather than generic web analytics style tagging.
- +Compliance workflows tied to RODS handling and co-driver logging patterns
- +Event triggers for yard move and geofencing align to operational analytics needs
- +Vehicle device integration supports CAN bus and J1939 signal ingestion use cases
- +Edit certification workflows provide traceability for driver status corrections
- –Governance around edits requires process discipline to avoid audit gaps
- –Advanced data use needs tighter integration than lightweight dashboard-only tooling
Best for: Fits when compliance-focused telematics analytics must stay connected to device and driver status events.
Linxup
SMBGPS fleet tracking software with driver behavior, vehicle diagnostics, and route visibility for commercial fleets.
Geofencing-based operational monitoring built around fleet device data and map views.
Linxup is a telematics-focused dot tracking solution aimed at fleets that need driver and vehicle movement visibility, not just event capture. It centers on GPS device data ingestion, map-based tracking, and configurable geofencing for operational monitoring.
The workflow emphasis is on driver-centric insights and exception handling, including route and stop behavior signals derived from tracked position updates. Admin controls focus on device-to-asset assignment and reporting outputs that are usable without deep analytics engineering.
- +Geofencing rules support site-based monitoring and exception detection
- +Driver and vehicle views make day-to-day operations easier to audit
- +Device-to-asset assignment keeps tracking tied to fleet structure
- +Reporting outputs support operational review without custom pipelines
- –API and event export are less transparent than analytics-first competitors
- –Higher-fidelity analytics require configuration discipline across devices
- –Limited evidence of deep automation for data diagnostics workflows
- –Customization for niche data fields appears constrained by the device feed
Best for: Fits when fleets need operational dot tracking with geofencing and driver-level visibility.
GPS Insight
enterpriseFleet tracking software for vehicle location, maintenance, driver safety, and compliance oversight.
Geofence eventing linked to tracked movement history for reviewing yards, stops, and route deviations in one workflow.
GPS Insight provides dot tracking built around telematics device feeds and fleet operations workflows. Location history is presented with event context, which makes it practical to review where a unit was when operational states changed.
The solution supports geofencing so teams can map boundaries to events and validate whether movement patterns match operational expectations. Tracking data can be exported so analytics teams can add custom models and reporting.
Admin workflows cover device onboarding and ongoing account operations, which helps keep tracking coverage consistent as fleet structures change. The overall experience favors fleet operations configuration more than analytics-native instrumentation.
- +Geofence events connect location history to operational action triggers
- +Vehicle and driver movement timelines support review of journey sequence and anomalies
- +Exportable tracking and event data supports external analytics pipelines
- +Device onboarding workflow supports scaling tracking coverage across fleet units
- –Higher setup effort than analytics-first tools that start from web events
- –API depth for event editing and compliance corrections may be limited
- –Governance controls depend on account configuration rather than granular in-app RBAC patterns
- –Throughput for high-volume location streams can require careful integration design
Best for: Fits when fleets need dot tracking tied to vehicles and drivers, plus exports for analytics teams.
Fleet Complete
enterpriseConnected fleet management software for vehicle tracking, asset tracking, and driver oversight.
Event-based tracking that ties location points to operational and telematics context for fleet reporting workflows.
Fleet Complete can record vehicle location signals and support compliance-oriented telematics workflows through its fleet operations suite. Its dot tracking coverage is driven by integrations to vehicle telematics hardware and managed data feeds that can support route, yard, and event-based reporting.
Admin configuration focuses on fleet setup and operational mappings across assets and drivers, rather than analytics-first event modeling. Automation is primarily built around telematics event generation and rule-based workflows for operations and reporting.
- +Works around vehicle telematics feeds and managed asset mappings
- +Supports yard and operational event context alongside location points
- +Provides workflow outputs geared to fleet operations reporting
- +Integrates with telematics hardware and gateway-style data sources
- –Less oriented toward analytics-team event schemas and instrumentation
- –API surface is not the primary path for dot tracking configuration
- –Auditability details for location edits and backfills are limited in documentation
- –Deeper rule tuning depends on admin configuration discipline
Best for: Fits when fleets need operational dot tracking tied to telematics hardware and compliance workflows, not analytics-first custom schemas.
ClearPathGPS
SMBGPS fleet tracking software focused on vehicle visibility, driver monitoring, and operational reporting.
Geofenced event rule configuration that converts yard move and location changes into time-ordered tracking records.
ClearPathGPS focuses on dot tracking for fleet operations that need location continuity across driver-led workflows and vehicle movement events. The core offering centers on telematics-style data capture, geofenced event handling, and compliance-oriented logging workflows that roll into hour tracking and audit trails.
ClearPathGPS also supports reporting around trips and driving states, with configuration options for event rules that map to operational definitions. Integration depth is best for teams that can standardize device and gateway data into consistent tracking events.
- +Geofence-driven event rules map movement changes to consistent records
- +Driver-focused workflows reduce reliance on manual entry for location events
- +Reporting supports practical trip and driving-state reviews for ops teams
- +Compliance-oriented logging workflows produce reviewable event timelines
- –Admin governance controls are less detailed than enterprise ELD-focused suites
- –Data normalization can require upfront configuration of event definitions
- –API and sandbox options are limited for custom telemetry ingestion patterns
- –Advanced device-level diagnostics coverage is narrower than some telematics competitors
Best for: Fits when fleet teams need consistent dot tracking events and operational logging without heavy custom analytics ingestion.
Conclusion
After evaluating 10 transportation logistics, Verizon Connect stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right dot tracking software
Dot tracking software connects movement events from devices to driver and vehicle workflows so fleets and analytics teams can reconcile timelines without rebuilding history in spreadsheets. This guide covers Verizon Connect, Omnitracs, and Azuga alongside analytics-instrumentation focused tools like Desmos and event-driven telemetry workflows in Motive and EROAD.
The selection emphasizes how integration breadth supports operational review, how the automation surface reduces manual reconciliation, and how governance controls like role separation and change history affect correction workflows. Each tool section maps those mechanics to real dot tracking outcomes such as event correlation for log review, governed correction routing, and geofencing rule-based event creation.
Dot tracking software for linking location events to governed driver and vehicle workflows
Dot tracking software ingests location and device events, then normalizes them into time-ordered tracking records that support operational review and exception handling. Verizon Connect focuses on correlating telematics movement with driver log review workflows to reduce manual timeline reconciliation. Omnitracs routes driver status corrections through role-based queues with audit trails for enterprise workflow governance.
Some tools emphasize faster instrumentation rather than deep ingestion diagnostics, like Desmos, which uses configurable event naming and property capture plus built-in funnels and cohorts. Other platforms center dot tracking around geofence and vehicle systems events, such as Linxup and GPS Insight, where location history and operational monitoring rules drive how exceptions appear in review workflows.
Evaluation criteria for dot tracking software tied to driver and vehicle workflows
Dot tracking software is judged by how reliably it turns device movement signals into time-ordered tracking records that operational teams can review without reconstructing history in spreadsheets. This guide prioritizes integration depth, automation and API surface, and governance controls because those mechanics determine whether corrections stay consistent across driver, vehicle, and route timelines.
Event correlation that connects movement to the right review workflow
Verizon Connect correlates telematics movement with driver log review workflows to reduce manual timeline reconciliation. Motive ties driver action messaging to the same event timeline used for post-incident log review.
Governed correction routing with audit trails
Omnitracs routes driver status corrections through role-based queues and audit trails for driver and vehicle change investigation. EROAD focuses on edit certification workflows that preserve driver status correction history tied to compliance records.
Diagnostic and telematics eventing that feeds structured exceptions
Azuga correlates diagnostic events from vehicle systems into driver and vehicle compliance exception workflows. Desmos provides configurable event naming and property capture that supports funnels and cohorts for behavioral exception analysis.
Tracking configuration workflow for rules and event creation
Linxup uses geofencing-based operational monitoring with driver and vehicle views for day-to-day auditing. ClearPathGPS uses geofenced event rule configuration that converts yard move and location changes into time-ordered tracking records.
Integration and export depth for analytics teams
GPS Insight links geofence events to tracked movement history and supports exports for analytics workflows. Fleet Complete ties location points to operational and telematics context for fleet reporting workflows but keeps event exports and APIs as a secondary path for dot tracking configuration.
Instrumentation speed versus ingestion diagnostics visibility
Desmos emphasizes quick web event instrumentation using a configurable tracking code and built-in funnels. Verizon Connect concentrates on reducing reconciliation effort by correlating telematics movement with log review timelines.
Decision framework for choosing dot tracking software by integration, automation, and governance
The second step is deciding whether the main value comes from analytics-instrumentation flexibility or from fleet device telemetry correlation. That choice determines whether tools like Desmos fit better than telematics correlation and governed edit workflows like Verizon Connect, Omnitracs, and EROAD.
Match the correction workflow to the platform’s governance shape
If corrections must be routed through role-based queues with audit-style investigation, Omnitracs is built around governed driver record review and exception handling. If corrections must preserve certified edit history tied to compliance records, EROAD emphasizes edit certification workflows.
Choose correlation-first when compliance review depends on timeline alignment
When driver log review depends on aligning movement events with review artifacts, Verizon Connect correlates route movement and exceptions to the log review workflow. When investigation depends on tying driver actions to telemetry evidence on one timeline, Motive focuses on event timeline linkage for post-incident review.
Pick event-driven diagnostics if exceptions originate from vehicle systems
When compliance exceptions must be triggered by diagnostic events arriving from vehicle systems, Azuga correlates diagnostic events into structured compliance exception workflows. If exceptions are more about web instrumentation patterns, Desmos configures event naming and properties and pairs it with funnels and cohorts.
Select geofence rule configuration when operational monitoring drives event creation
If day-to-day auditing requires geofencing rules that generate monitoring events from site logic, Linxup provides geofencing rules plus driver and vehicle views. If consistent event records are required for yard move and location changes, ClearPathGPS converts geofenced rule outcomes into time-ordered tracking records.
Validate analytics export and API expectations against the tool’s configuration path
If exports and eventing are needed to feed analytics workflows while reviewing yards, stops, and route deviations, GPS Insight ties geofence events to movement history and supports exports. If dot tracking configuration is expected to be driven mainly by fleet device mappings rather than analytics-first event schemas, Fleet Complete centers operational and telematics context and keeps its API surface less prominent for configuration.
Confirm that instrumentation control fits the team’s governance discipline
If the team can enforce setup discipline across roles and fleet roles, Azuga’s deep configuration and role separation support structured compliance exceptions. If governance and governance-visible configuration are expected to be prominent, Verizon Connect includes role-based access and change history for log workflow governance.
Who should buy dot tracking software for driver, vehicle, and route review workflows
The most direct match appears when correction routing, audit trails, and event correlation are required by the operational review process. The secondary match appears when teams mainly need configurable event instrumentation and analysis views for non-compliance operational decisions.
Fleet analytics teams aligning driver and route timelines for compliance review
Verizon Connect aligns route movement and exceptions with driver log review workflows through event correlation, which reduces manual timeline reconciliation.
Enterprise fleets requiring governed correction queues and audit-style investigations
Omnitracs routes driver status corrections through role-based queues with event trails for investigations across driver and vehicle changes.
Compliance operations teams that need telematics diagnostics to drive structured exceptions
Azuga correlates diagnostic events from vehicle systems into driver and vehicle compliance exception workflows with role separation for dispatch and compliance operations.
Analytics teams that need configurable web event instrumentation plus funnels and cohorts
Desmos provides configurable tracking code for event naming and property capture and includes built-in funnel and cohort views.
Operational monitoring teams using geofence rules to standardize event records
ClearPathGPS converts geofenced yard move and location changes into consistent time-ordered tracking records that reduce manual location event entry.
Common buying and implementation pitfalls for dot tracking software
Teams also run into quality gaps when telematics connectivity is inconsistent or when event definition governance is not treated as a cross-role process. Dot tracking buyers should verify how each tool handles timeline alignment, correction routing, and geofence rule event creation before rollout.
Assuming tracking fidelity stays stable under weak device connectivity
Verizon Connect can show tracking gaps when telematics connectivity is unstable, so connectivity patterns must be reviewed before relying on correlated review timelines.
Treating correction workflows as a manual task outside governed queues
Omnitracs relies on enterprise workflow design and role-based queues for driver record review, so running approvals without the intended workflow setup increases audit investigation friction.
Overlooking how governance discipline affects edit correctness
Azuga’s deeper configuration depends on governance discipline across fleet roles, so inconsistent role setup can produce mismatched edits in compliance exception handling.
Buying a geofence monitoring tool but expecting analytics-first event schema control
Linxup provides geofencing-based operational monitoring with driver and vehicle views, but its API and event export transparency is less explicit than analytics-first competitors.
Assuming exports and API depth cover advanced event editing and compliance corrections
GPS Insight supports exports tied to geofence eventing and movement history, but API depth for event editing and compliance corrections can be limited for workflows that require rich correction operations.
How We Selected and Ranked These Tools
We evaluated Verizon Connect, Omnitracs, Azuga, Desmos, Motive, EROAD, Linxup, GPS Insight, Fleet Complete, and ClearPathGPS for integration depth, automation surface, and governance controls that affect dot tracking corrections. Features carried 40% weight because correlation, workflow routing, and diagnostics-to-exception paths change day-to-day review effort.
Ease and value each carried 30% weight because teams need predictable configuration and manageable operational overhead during rollout and ongoing use. Verizon Connect ranked highest due to event correlation that links telematics movement with driver log review workflows, plus role-based access and change history that support governed log correction work.
Frequently Asked Questions About dot tracking software
How does PostHog differ from Verizon Connect for event-based dot tracking analytics?
Which tools provide DOT-style hours-of-service logs tied to driver actions rather than just location points?
What breaks if event provenance is not preserved during telematics ingestion?
How does geofencing support yard move and route deviation workflows across GPS Insight and Linxup?
When do admin controls matter most for compliance operations in Omnitracs and EROAD?
How do integrations and data exports differ between Desmos and GPS Insight for analytics teams?
What setup work is required to standardize device and gateway data in ClearPathGPS?
How do configurable edit and correction workflows differ between Omnitracs and ClearPathGPS?
Which tool best fits teams needing telematics gateway style ingestion rather than lightweight tagging for dot tracking?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
- Transportation LogisticsTop 10 Best Dot Driver Management Software of 2026
- Transportation LogisticsTop 10 Best Car Tracking Software of 2026
- Transportation LogisticsTop 10 Best Dot Log Book Software of 2026
- Regulated Controlled IndustriesTop 10 Best Dot Random Drug Testing Software of 2026
- Technology Digital MediaTop 10 Best Computer Tracking Software of 2026
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Transportation Logistics alternatives
See side-by-side comparisons of transportation logistics tools and pick the right one for your stack.
Compare transportation logistics tools→