Foundry research · Great Library of SISO

US logistics and freight service firms

Start with load-intake completeness, dispatch packet coordination, shipment exception follow-up and proof-of-delivery billing reconciliation. Compare matched work against the incumbent TMS or dispatch process; keep carrier selection, hours-of-service, routing, claims and customer commitments with authorized humans.

Research dated 2026-09-05. Business value remains unmeasured. Software descriptions are documented capabilities; each project must verify fit, rights and outcomes before adoption.

United States research pilot; carrier, safety, hours-of-service, privacy, contract and state requirements require qualified owner review.

What the evidence supports

49 CFR Part 395 establishes hours-of-service and recordkeeping requirements that bound any dispatch assistant. Vendor pages show workflow capabilities, not an automation rate, adoption prevalence or achieved savings; regulated and commercial authority remains human.

[ecfr-hos] [descartes-tms] [onfleet-platform]

Processes to test

Customer load-intake and shipment-record completeness review

Capture requested pickup, delivery, commodity, equipment and contact fields; flag missing or contradictory fields for review. Do not quote binding terms, classify regulated goods or accept a shipment without authorized review.

Measure
Net human minutes per accepted complete load record including review, rework and exception handling; missed-critical-field rate
Reject the idea if
Reject if unsafe or regulated details are silently accepted, correction/rework rises, critical fields are missed or private data crosses an unauthorized boundary.
Human authority
Authorized operations staff determine acceptance, terms, commodity treatment and customer commitments; qualified safety and compliance personnel retain authority.

[descartes-tms] [repo-fleetbase]

Dispatch packet preparation and driver/carrier confirmation

Assemble approved load details, contact records and timestamps; draft confirmation requests and surface missing acknowledgements. Do not select carriers, assign unsafe work, alter hours-of-service records or issue binding instructions without human approval.

Measure
Net human minutes per accurately acknowledged dispatch packet including review and rework; missing-acknowledgement and unsafe-instruction rate
Reject the idea if
Reject if an acknowledgement is mistaken for legal or safety clearance, HOS records are changed or obscured, rework offsets time saved, or an unapproved instruction is sent.
Human authority
Dispatcher and designated carrier/safety authority approve assignment, instructions, records and escalations; the system is not a carrier-authority substitute.

[onfleet-platform] [ecfr-hos] [repo-fleetbase]

Shipment-status exception detection and approved follow-up

Normalize status events, flag stale or contradictory milestones and draft follow-ups to verified recipients. Do not infer fault, promise delivery, change routing or send customer claims responses without human review.

Measure
Net human minutes per accurately triaged and approved exception; stale-event, duplicate-send, missed-escalation and privacy-error rates
Reject the idea if
Reject if stale or incorrect status causes a customer commitment, routing or claims error, review/rework is not reduced, or an escalation is missed.
Human authority
Operations lead approves status interpretation, customer commitments, routing changes and claims/escalations; verified recipients and channel controls remain mandatory.

[onfleet-platform] [descartes-tms] [repo-fleetbase]

Proof-of-delivery and freight-billing evidence reconciliation

Match approved delivery events, signed or electronic proof, accessorial evidence and invoice fields; surface mismatches for review. Do not approve payment, waive claims, alter invoices or determine contractual liability.

Measure
Net human minutes per correctly reconciled invoice packet including exception review; false-match, missed-mismatch and duplicate-payment rates
Reject the idea if
Reject if a mismatch is silently accepted, payment or claim authority is bypassed, false matches/rework rise, or evidence is unavailable for audit.
Human authority
Authorized finance and operations staff approve invoices, accessorials, claims and contractual interpretations; the workflow only organizes evidence.

[onfleet-platform] [descartes-tms] [repo-greaterwms]

Existing software

Descartes Transportation Management

Vendor advertises transportation-management capabilities for planning, execution, visibility and freight workflows.

No current quote, billing basis, avoided spend or implementation cost verified.

[descartes-tms]

Onfleet

Vendor advertises delivery management, dispatch, tracking, notifications and proof-of-delivery workflows.

No current quote, billing basis, avoided spend or implementation cost verified.

[onfleet-platform]

Reusable code candidates

fleetbase/fleetbase

Repository presents an open logistics and supply-chain operating system with orders, fleet and shipment-oriented workflows.

Possible reuse
Read-oriented load, order and status sidecar over redacted fixtures; preserve incumbent dispatch/TMS authority and human approval for external actions.
Limits
Repository capability is not evidence of carrier authority, regulatory compliance, security, availability, integrations or production fitness.
Rights
Coverage inventory records AGPL-3.0 with high reuse risk; verify current license, dependencies, security and deployment obligations before reuse.

[repo-fleetbase]

Revision: unverified

GreaterWMS/GreaterWMS

Repository presents a warehouse-management application with inventory and warehouse workflow capabilities.

Possible reuse
Inventory and fulfillment evidence prototype only, using synthetic or redacted records; no authority over freight release, routing or customer commitments.
Limits
README capability is not evidence of warehouse controls, carrier compliance, scan accuracy, integrations, support or production operation.
Rights
Coverage inventory records Apache-2.0; verify current repository license, dependencies, security and deployment obligations before reuse.

[repo-greaterwms]

Revision: unverified

Business value and a falsifiable pilot

No firm baseline, achieved automation rate, review/rework data, operating cost, displacement proof or eligible-population measurement. Null is not zero.

Within one authorized freight operator, compare matched redacted or synthetic loads, dispatches, exceptions and invoice packets under the incumbent and supervised candidate workflows; pre-register HOS, privacy, approval and rollback gates.

  • Human time including review/rework is not lower than matched baseline.
  • Any HOS, carrier-authority, routing, payment or customer commitment action occurs without authorized human approval.
  • Private shipment, driver or customer data crosses an unauthorized boundary or a critical exception is missed.
  • Measured first-year net cash is not positive for a cash-savings offer; capacity gains alone are not cash.
Read the shared value model

Limits

  • This is not transportation, safety, customs, legal, regulatory or carrier-authority advice, product admission or an industry-wide forecast.
  • Current software adoption prevalence and subscription prices were not verified; named offerings are not assumed installed.
  • No generic repository is claimed to replace a TMS, WMS, carrier records, HOS records, contractual authority or professional judgment.
  • Rights, security, retention, restoration, integrations, accessibility, data quality, claims handling and state/local requirements remain product-owner gates.

Sources

  1. 49 CFR Part 395 — Hours of Service of Drivers · Electronic Code of Federal Regulations

    Supports hours-of-service and recordkeeping boundaries; does not authorize software to make safety, routing or carrier decisions and is not legal advice.

  2. Transportation Management · The Descartes Systems Group

    Vendor capability claims only; no installation prevalence, price, accuracy, security or outcome measurement.

  3. Onfleet delivery management platform · Onfleet

    Vendor capability claims only; no installation prevalence, price, accuracy, security or outcome measurement.

  4. fleetbase/fleetbase repository · Fleetbase

    Repository was accessible; revision and production behavior remain unverified. Coverage inventory records AGPL-3.0 and high reuse risk, subject to current rights review.

  5. GreaterWMS/GreaterWMS repository · GreaterWMS

    Repository was accessible; revision and production behavior remain unverified. Coverage inventory records Apache-2.0, subject to current rights review.

Canonical source and machine access

Pinned Foundry source · Record JSON

SHA-256: b775b2b3748ae606f142006a868ed98f6e10a2ac39643084dc11a3ddeef43175