Product line 02

DIBS Freight OS

A brokerage operating system that decides and proves what happened: who the carrier really is, what the load is worth, where the freight is, and what to do when the network breaks.

Carrier trust and risk scoring

A single 0–100 score composed from positive and negative factors, recomputed on every material event.

Carrier Score = Operational Reliability
              + Compliance Integrity
              + Identity Confidence
              + Financial Reliability
              – Fraud Penalty
              – Concentration Penalty
              – Current Exposure Penalty

Hard blocks bypass the score entirely: inactive authority, expired insurance, double-brokering, impersonation, forgery, cargo theft, or a sanctions match.

BandRangeEffect
Preferred85 – 100Full tender eligibility, highest exposure ceiling
Approved70 – 84Standard tender eligibility
Conditional55 – 69Tender with additional verification
Restricted40 – 54Manual approval required per load
Suspended1 – 39No new tenders
Hard Block0Blocked outright — authority, fraud or sanctions trigger

Load lifecycle

Fifteen states from draft to closed. Every transition is authorised, timestamped and hash-chained into the audit ledger.

  • Draft
  • Quoted
  • Customer approved
  • Carrier sourcing
  • Tendered
  • Accepted
  • Dispatched
  • Picked up
  • In transit
  • Delivered
  • POD verified
  • Invoiced
  • Approved for settlement
  • Settled
  • Closed

Tender controls

  • Authority active and insurance meets requirements.
  • Equipment matches cargo; HOS and geography are feasible.
  • Risk score at or above threshold with no hard block.
  • Payment instructions verified against the carrier of record.
  • Exposure limits respected at carrier and concentration level.

Carrier pay ceiling

Ceiling = Base Lane Rate
        + Scarcity Premium
        + Urgency Premium
        + Reliability Discount
        – Fraud / Risk Discount
        – Required Margin Buffer

Tracking, evidence and fraud graph

Multi-source telemetry normalised into one event standard, then bound into a tamper-evident ledger.

Sources

  • ELD, GPS and IoT (temperature, humidity, shock).
  • AIS vessel data, port/terminal and rail APIs.
  • Weather, DOT and traffic feeds.
  • Driver app and voice agent commitments.

Event standard

{ eventId, shipmentId,
  eventType, occurredAt,
  source, confidence,
  payload, evidenceHash }

Hₙ = SHA256(Hₙ₋₁ ‖ Payloadₙ)

High-risk patterns

  • Multiple carriers sharing one payment account.
  • Rapid banking changes immediately before settlement.
  • Reused insurance documents across entities.
  • Shared devices or IPs across suspicious entities.
  • Freight moved by an undeclared carrier; custody gaps.

Emergency recovery and the shadow network

Seven operating states, an alternate physical network, and priority allocation that puts life-safety freight ahead of everything else.

  1. 01Normal

    Baseline operations; standard routing and tender controls apply.

  2. 02Watch

    Signal thresholds breached; monitoring elevated, no reroute yet.

  3. 03Pre-emptive diversion

    Routes re-scored ahead of impact; shadow capacity put on standby.

  4. 04Recovery mode

    Shadow network activated, priority tiers allocated, campaigns launched.

  5. 05Degraded network mode

    Reduced capacity operating plan; deferrable freight held.

  6. 06Manual command mode

    Human commander owns allocation; automation advisory only.

  7. 07Return to baseline

    Controlled unwind of overrides with full reconciliation of exposure.

Shadow network

  • Alternate ports
  • Cross-docks
  • Micro-hubs
  • Regional carriers
  • Hotshot / sprinter
  • Air charter
  • Mobile fueling
  • Temporary reefer power
  • Satellite dispatch
  • Offline controls

Priority allocation

  • Tier 0 — life-safety: immediate override.
  • Tier 1 — perishables and critical: automated recovery.
  • Tier 2 — high value: best available capacity.
  • Tier 3 — standard: queue and consolidate.
  • Tier 4 — deferrable: hold.

Edge dispatch authority

Edge nodes keep active manifests, shadow routes, approved carriers and local policy so dispatch survives a central outage for 24–72 hours.

Action at the edgeAutonomous
Pre-approved rerouteYes
Shadow-carrier retender below capYes
Emergency rate increase below capYes
International diversionConditional
Air charterNo — human approval
Bank or payment changeNo
Hard-block overrideNo
High-value custody exceptionNo