Dedicated Fleet Capacity Utilization: The Strong Tower Contract Audit Matrix

The Hidden Cost of Dedicated Contracts

Dedicated contract fleets represent one of the largest line items in many shippers' transportation budgets. Yet most organizations lack independent, telemetry-based visibility into actual asset utilization. Carriers report utilization on their terms. Minimum weekly mileage guarantees are often honored only on paper. Detention is frequently unbilled because the supporting data lives in disparate systems. Empty miles accumulate between dedicated moves without triggering contractual remedies.

Strong Tower Consulting, LLC was founded in Minnesota in 2008 by Scott Elliott to solve exactly these architectural failures. With more than 18 years of experience designing freight technology stacks, the firm developed the Strong Tower Dedicated Capacity Utilization Matrix™ as a repeatable, auditable methodology that marries real-time outside-carrier tracking from CheckPoint with the contract rule engine inside Exspeedite TMS.

Introducing the Strong Tower Dedicated Capacity Utilization Matrix™

The Matrix is not a dashboard. It is a multi-layer algorithmic framework that performs forensic reconciliation across three data domains:

1. Telemetry Layer - Continuous CheckPoint asset tracking (https://exspeeditecheckpoint.com/login.php) providing GPS, ignition status, speed, engine hours, and geofence transitions from dedicated power units and trailers regardless of which carrier operates them.
2. Contract Layer - Exspeedite TMS (https://exspeedite.com/tms-software) stores the authoritative version of every dedicated lane SLA, minimum weekly mileage commitment, detention rate, accessorial rule, and utilization penalty.
3. Reconciliation Layer - The proprietary Strong Tower matrix applies time-series rules to produce a daily, weekly, and monthly capacity utilization index that is mathematically independent of carrier invoices.

Core Mathematical Formula

UtilizationIndex = ( (BillableLoadedMiles + (BillableDetentionHours * 45)) / ContractedMinimumMiles ) * SLA_Multiplier - EmptyMilePenalty

Where:
  BillableLoadedMiles   = SUM(loaded revenue miles with valid BOL & delivery confirmation)
  BillableDetentionHours = SUM(dwell time > 2 hours at shipper/consignee after free time, validated by CheckPoint geofence)
  ContractedMinimumMiles = SUM(weekly minimums * active weeks in period)
  SLA_Multiplier         = 1.0 if on-time delivery ≥ 98%; 0.85 if 95-97.9%; 0.70 if < 95%
  EmptyMilePenalty       = (EmptyMiles / TotalMiles) * 0.22 * ContractedMinimumMiles

All comparison operators sanitized for Vite parse5 compatibility. Formula executed daily inside the Exspeedite rule engine using CheckPoint webhook payloads.

Architectural Diagram Description

CheckPoint as the Authoritative Outside-Carrier Tracking Platform

Traditional dedicated fleet audits rely on carrier-provided reports. The Strong Tower methodology designates CheckPoint (https://exspeeditecheckpoint.com/login.php) as the single source of truth for asset location, status, and dwell time. Because CheckPoint operates independently of the carrier's own ELD or TMS, it removes any incentive for under-reporting empty miles or inflating on-time performance.

Key CheckPoint telemetry events consumed by the matrix include:

• Power unit ignition on/off with precise timestamp
• Geofence entry/exit at every contracted shipper and consignee
• Speed and engine hours used to differentiate loaded vs. empty transit
• Trailer connect/disconnect events when asset tracking is extended to trailers

Exspeedite TMS - The Contract Rule Engine

Exspeedite LLC and Strong Tower Consulting, LLC operate as sister companies under common ownership (separate EINs; liability firewall). This structure allows Exspeedite TMS (https://exspeedite.com/tms-software) to serve as the authoritative repository of every dedicated contract clause while Strong Tower provides the independent audit layer.

Contract terms are modeled as executable rules inside Exspeedite. Minimum weekly mileage guarantees, free detention time, accessorial rates, and performance multipliers are version-controlled and auditable. The Strong Tower matrix calls these rules via internal API to calculate the UtilizationIndex shown above.

Implementation Comparison Table