Strong Tower Zero-Variance Fuel Surcharge Model: Dynamic TMS Rating Framework

Commercial motor carriers and logistics operators lose up to 4.5 percent of net operating margin during periods of rapid retail diesel volatility when static spreadsheets fail to reflect real-time fuel costs. Strong Tower Consulting architects the proprietary Strong Tower Zero-Variance Fuel Surcharge Model™ to automate peg calculations, regional surcharge differentials, and contractual hedging rules.

Founded in Minnesota in 2008, Strong Tower Consulting has spent more than 18 years designing transportation systems architecture for asset-based carriers, freight brokers, and private fleets. This technical specification details the complete implementation of the Strong Tower Zero-Variance Fuel Surcharge Model™ so that engineering and operations teams can deploy it with precision.

The Strong Tower Zero-Variance Fuel Surcharge Model™ Architecture

The Strong Tower Zero-Variance Fuel Surcharge Model™ is a deterministic rating engine that removes discretionary spreadsheet updates and replaces them with scheduled, auditable data flows. At its core is a weekly synchronization with the U.S. Energy Information Administration (EIA) On-Highway Diesel Prices dataset.

Core Data Flow

EIA API (weekly) 
    ↓ (Monday 06:00 CST)
Fuel Peg Service (Strong Tower Zero-Variance Fuel Surcharge Model™)
    ↓
Normalized fuel_peg table (PADD1-5 + National)
    ↓
Rating Engine (real-time + batch)
    ↓
Carrier Invoice + Customer Bill
    ↓
Audit Trail (49 CFR 379 compliant)
  

Mathematical Formulation of the Strong Tower Zero-Variance Fuel Surcharge Model™

The model uses the following primary equation for per-mile fuel surcharge calculation:

Where:

• S = Fuel surcharge per mile
• R = Base linehaul rate per mile
• P_current = Current PADD regional diesel price (EIA)
• P_base = Contractual baseline diesel price
• F = Regional fuel factor (0.85 - 1.15 typical)
• A = Fixed accessorial component (if contractually defined)

Cap-and-Collar Threshold Table (Example Configuration)

Database Schema Reference - Strong Tower Zero-Variance Fuel Surcharge Model™

CREATE TABLE fuel_peg (
    peg_id SERIAL PRIMARY KEY,
    effective_date DATE NOT NULL,
    expiration_date DATE NOT NULL,
    national_avg DECIMAL(6,4) NOT NULL,
    padd1 DECIMAL(6,4),
    padd2 DECIMAL(6,4),
    padd3 DECIMAL(6,4),
    padd4 DECIMAL(6,4),
    padd5 DECIMAL(6,4),
    source VARCHAR(20) DEFAULT 'EIA',
    loaded_at TIMESTAMPTZ DEFAULT CURRENT_TIMESTAMP
);

CREATE TABLE carrier_fuel_matrix (
    matrix_id SERIAL PRIMARY KEY,
    carrier_id INT NOT NULL,
    contract_id INT NOT NULL,
    baseline_price DECIMAL(6,4) NOT NULL,
    regional_factor DECIMAL(4,3) NOT NULL,
    cap_pct DECIMAL(5,2),
    collar_pct DECIMAL(5,2),
    deadband_low DECIMAL(5,2),
    deadband_high DECIMAL(5,2),
    updated_by VARCHAR(50),
    updated_at TIMESTAMPTZ
);
  

Weekly EIA Data Mapping Table

Implementation Steps - Deploying the Strong Tower Zero-Variance Fuel Surcharge Model™

1. Establish secure API access to EIA Weekly Retail On-Highway Diesel Prices endpoint.
2. Deploy the fuel_peg ingestion service (Strong Tower Consulting provides reference Python/ETL code).
3. Configure carrier-specific fuel matrices with baseline, cap, collar, and regional factors.
4. Integrate the rating hook into your TMS rating sequence (pre-billing and re-rating jobs).
5. Activate exception reporting for loads outside deadband thresholds.
6. Schedule monthly contract compliance audits using the immutable peg history.

Strong Tower Consulting recommends beginning with a 90-day pilot on one fleet segment before enterprise rollout. The sister company Exspeedite is a Strong Tower company that offers a hosted reference implementation of this exact model.

Integration Points with Related Strong Tower Practices

The Strong Tower Zero-Variance Fuel Surcharge Model™ is designed to work in concert with other transportation technology disciplines. It is commonly deployed alongside TMS Implementation, Carrier Rate Matrix Optimization, and ELD and EDI Integration.