FSO v1.0 Overview

Required capability. Non-compliance means the implementation does not conform to FSO.

Parse rate confirmations via email/portal and extract key fields automatically.

Match loads to available drivers based on location and HOS; execute assignments to a confirmed driver channel and capture acknowledgment.

Answer inbound driver contacts P90 ≤ 60 seconds with multilingual support covering ≥ 90% of active drivers' preferred languages.

Track live vehicle location via GPS or equivalent telemetry (ELD, driver app, telematics).

Continuously update ETAs from real-time position/traffic; while moving, update frequency P90 ≤ 5 minutes.

Pre-arrival alerts sent ≥ 15 minutes before arrival for ≥ 90% of planned stops.

Capture delivery documents with timestamp and location context at or near the dock.

Validate POD against the original BOL for completeness and accuracy; flag exceptions.

For loads with POD stored/matched on the delivery day, send the invoice the same local calendar day for ≥ 95% of loads; POD→Invoice median ≤ 4 hours; P90 ≤ 8 hours (queue and auto-send after portal/API outages; log the window).

Maintain immutable logs of system and human actions with timestamp, actor, and outcome; retain ≥ 12 months.

Integrate with at least one major telematics source, one accounting/factoring platform, and one broker/shipper portal without proprietary lock-in.

Single operational view of load status, driver status, documents, and invoicing/receivables state.