DURANDISSEONETRANSPORTATION OPERATING NETWORK

D-ONE / Workspace

ELOHM Command Center

OrganizationDurandisse International Transport

Session-only perspective. Each organization has its own isolated operating environment; controlled cross-organization sharing is not enabled.

Illustrative data · no persistent tenant changes
RoleExecutive / CEO

Role switching is session-only. Organization roles remain inside the selected organization. Platform Administrator is distinct and never receives carrier records implicitly.

OrganizationDurandisse International Transport
BoundaryOrganization-scoped

Network health and outcome review with policy-bounded approvals.

Session-only role context
412

Role-aware operation · session context

Executive / CEO · Durandisse International Transport

Full navigation remains available. Role controls dashboard composition, sensitive fields, exception scope, and action authority inside the selected organization.

PermittedApproval requiredDenied with reasonRead-only
Workspace reference

Intelligence / organization-aware operating layer

ELOHM works within the current organization’s permitted policies, assets, history, and integrations. DIAL is its specialized freight-decisioning logic; Freight Decisioning determines what should be booked and Dispatch executes what is booked.

Talk through setup ↗Back to overview

ELOHM Command Signal

Network intelligence online

ELOHM applies DIAL logic for freight decisions, then carries the result into assignments, risks, and actions.

Ask ELOHM

D-ONE intelligence hierarchy

The signal changes with the carrier.

ELOHM is the Durandisse One platform intelligence layer. It reads the current organization’s permitted policies, assets, load and broker history, fuel and maintenance data, financial data, historical performance, and integrations. Another carrier receives recommendations from its own policies and data, never DIT’s.

01 / Platform

Durandisse One

Commercial transportation operations platform sold to many trucking companies.

02 / Intelligence

ELOHM

Cross-platform intelligence layer that respects organization and user permissions.

03 / Specialized logic

DIAL

Freight-decisioning logic derived from the current carrier’s policy and operating situation.

Current organization signal

DIAL uses this organization’s configuration.

No cross-tenant learning in view

Durandisse International Transport

Total-mile economics using $3.50 / total mile, 500–600 mi / day, and Dry van + reefer configuration.

Minimum gross$3,200
Margin floor28%
Max deadhead75 mi

Ranked recommendation example

#1 RecommendedACCEPTLane clears current economics and HOS feasibility
#2NEGOTIATERate or payment terms need a human counter
#3REVIEW REQUIREDMissing appointment, policy input, or feasibility evidence

REJECT remains available when the organization’s risk, economics, safety, compliance, or approval rules block the opportunity.

Decision audit trail

Why DL-2051 was recommended

Illustrative traceability for one load. The protected Freight Decisioning drawer remains unchanged; this history view makes the outcome explainable after the decision.

Audit fieldIllustrative record
DIAL recommendationACCEPT · #1 Recommended · 94 confidence
Inputs usedTotal RPM, deadhead, HOS fit, equipment, reload probability, market rate, broker credit, fuel assumption
Policy appliedCurrent organization DIAL policy · not a platform default
Approved byJordan Davis · Operations lead · session-only authorization
Rate changedNo · offer retained at illustrative confirmation
Booked by / outcomeJordan Davis · approved for assignment, not yet dispatched

Decision inputs

Feasibility is never mileage alone.

HOS + ELD

Organization-scoped input to ELOHM / DIAL.

Market Zones

Organization-scoped input to ELOHM / DIAL.

Fuel economics

Organization-scoped input to ELOHM / DIAL.

Maintenance readiness

Organization-scoped input to ELOHM / DIAL.

Safety + compliance

Organization-scoped input to ELOHM / DIAL.

ELOHM operating context · canonical reads

Ask the records you already own.

Choose an operating question. The answer is deterministic, session-only reasoning over the active organization’s permitted canonical Load, Truck, Driver, Customer / Broker, Invoice, Document, and Exception records. This is an honest product preview: no live model, API, credentials, persistence, or background reasoning is connected.

Advisory only · illustrativeRecommendations remain in the existing module and require the existing human owner.

The question runs locally against the current sample context. It does not call a model or change a canonical record.

Supported question patterns

Illustrative answer · current organization

DIT-TRUCK-01 is projected to become empty in Atlanta, GA tomorrow.

Derived from canonical records

Scope

Organization: DIT · serving role: Executive / CEO · Organization aggregate health, margin, exceptions, and decision outcomes.

Basis

Read only the selected organization’s canonical records; no separate ELOHM load, truck, driver, customer, invoice, or document dataset is used.

Assumption

This is deterministic sample-data reasoning. “Tomorrow,” market availability, and missing live updates are estimates from the dated illustrative records.

Limit

No live model, API, provider feed, persistence, or background refresh is connected. ELOHM cannot approve, dispatch, move money, change policy, close exceptions, or access credentials.

Canonical records read

1 record
DIT-TRUCK-01 · Kenworth T680Truck · inspect module ↗Atlanta, GA · DL-2051 delivery window · unload timing remains an estimate

Human next step

Review the Fleet and Network Planning context before any reposition or assignment decision.

Approval owner

The existing role owner remains responsible for any approval or action.

Existing audit concept · ELOHM interaction event

Questions stay inspectable.

Session-only · not immutable

Each submitted question records the serving actor, organization, role, question context, canonical record IDs read, result, and session timestamp. This is the existing audit concept extended in the preview; durable append-only storage is not implemented.

No ELOHM question has been submitted in this session.