Skip to main content
KSM Transport Advisors FreightMath logo FreightMath is KSM Transport Advisors’ freight data product. It receives data from your TMS, organizes historical shipment data, calculates operating ratios on your lanes, and provides aggregated market rates from across the FreightMath client base. BidRight reads from FreightMath. When you open a lane in bid detail, the historical OR, volume, revenue per mile, and market rate on that row come from FreightMath, matched to that specific lane. How FreightMath data reaches BidRight: your TMS and Carrier First feed FreightMath (KSMTA); BidRight reads from FreightMath

​
What FreightMath gives you in BidRight

When you’re pricing a lane, FreightMath populates these data points on the row:
Open the columns to review the Source of the information. Some lanes have enough density with that bidding customer to populate with orders you hauled for that exact customer. Other lanes show data from your areas across your customer base.You can also identify this at a glance by text style. Standard font means these orders were actual shipments on this lane with this customer. Lighter gray text means freight is aggregated from other customers as well.Bid Detail Historical table with Source column and row styling for lane vs. aggregated data
  • Historical OR — Your operating ratio on this lane (or area), based on actual shipments.
  • Historical volume — How many loads you’ve run on this lane historically.
  • Historical RPM — What you charged on this lane in past periods.
  • Carrier First market rate — A market benchmark aggregated from FreightMath’s client base, matched by trailer type and origin/destination.
  • FM Operation — The match type used to pull historical data.

​
How data is matched

FreightMath matches data to bid lanes at the same level the lane is bid at: city-to-city lanes match to city-to-city history, ZIP-to-ZIP to ZIP-to-ZIP, and ZIP3 to ZIP3. When there is not enough data at that level, BidRight falls back through a defined hierarchy. For OR specifically, “enough data” means at least 12 loads in the last 12 weeks. Below that threshold, OR rolls up to a broader level until the threshold is met. See OR Modeling Fallback Hierarchies for how the fallback works.

​
Related content