DURANDISSEONETRANSPORTATION OPERATING NETWORK

D-ONE / Workspace

Data Foundation

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 / normalized load-data layer

Give every provider the same canonical load language so DIAL can compare freight from different sources on equal terms, inside the current organization boundary.

Talk through setup ↗Back to overview

ELOHM Command Signal

Record quality monitored

ELOHM identifies missing links, conflicting statuses, and incomplete source records before they weaken an operating decision.

Review record quality

Platform capability / organization data

One canonical load record. Many source shapes.

Normalization is a D-ONE platform capability. The records, providers, customers, lanes, policies, and history flowing through it belong to the current organization.

Canonical fields

24

Source mappings

06

Record ownership

D-ONE

Quality state

Illustrative

Field normalization

Different words. Equal comparison.

External fields map into one internal vocabulary before DIAL evaluates rate, feasibility, risk, or margin.

Provider field: “Rate”D-ONE: gross rate
Provider field: “Offer”D-ONE: gross rate
Provider field: “Miles”D-ONE: loaded miles / total miles
Provider field: “Appointment”D-ONE: pickup or delivery appointment
Provider field: “Broker MC”D-ONE: MC
Provider field: “Pay terms”D-ONE: days to pay

Why this matters to DIAL

Freight is compared on equal terms.

Trucker Path, Truckstop, DAT, direct broker APIs, customer tenders, TMS feeds, private freight networks, and partner networks may describe the same concept differently. Normalization lets DIAL compare them using the current organization’s policy, HOS and ELD feasibility, market zones, fuel economics, maintenance readiness, and safety constraints.

Source

Labeled provider context.

Normalize

Canonical D-ONE field.

Decide

Organization policy + data.

Canonical schema

The normalized load record

Target schema
01

source

DAT / Trucker Path / tender / TMS

02

external load ID

Provider-specific identifier

03

origin

City, state, postal zone

04

destination

City, state, postal zone

05

pickup date + appointment

Date, window, appointment ID

06

delivery date + appointment

Date, window, appointment ID

07

deadhead

Miles before pickup

08

loaded miles

Planned loaded distance

09

total miles

Deadhead + loaded miles

10

gross rate

Canonical offer amount

11

loaded RPM

Gross ÷ loaded miles

12

total RPM

Gross ÷ total miles

13

market rate

Comparable lane context

14

weight

Declared cargo weight

15

equipment

Trailer / equipment type

16

stops

Pickup, delivery, intermediate stops

17

broker

Organization account reference

18

contact

Authorized source contact

19

MC + USDOT

Authority identifiers

20

credit score

Broker risk context

21

days to pay

Payment timing context

22

notes + special requirements

Free text and constraints

23

source timestamp

Provider event time

24

last updated

D-ONE normalized update time

Operating inputs

Policy is data, too.

DIAL also consumes the current organization’s HOS and ELD feed, market zones, fuel prices and MPG, maintenance readiness, safety and compliance status, broker history, customer lanes, and approval thresholds. A missing delivery appointment yields REVIEW REQUIRED — DELIVERY APPOINTMENT MISSING.

Configure organization policy

Data quality boundary

Source context never becomes silent truth.

Every normalized value retains its provider, source timestamp, last updated time, and confidence. D-ONE owns the canonical record and history; outside sources remain labeled and organization-scoped.

Review connection scopes