POD → invoice → settlement
Owned load, invoice, and settlement IDs stay linked.
Automatic exchange / sampleD-ONE / Demo workspace
Operations / harmony layer
A visual blueprint for synergetic, cross-workspace automation: one owned record moves through the network, with guardrails at every consequential handoff.
ELOHM Command Signal
Automation guardrails active
ELOHM can prepare work while D-ONE keeps approvals, dispatch holds, and money movement with named owners.
Review automationsD-ONE natively detects triggers, evaluates conditions, runs automated actions, routes approvals, and records every event in its audit history. This page is a static showcase of that owned operating model, not an enabled automation engine.
Record journey / end to end
Relationships
Commercial terms become the first owned record.
Operations
A committed lane becomes a D-ONE load.
Operations
Capacity, driver, and equipment are assigned.
Operations
The cab receives the next clear action.
Operations
Milestones and proof stay in D-ONE.
Finance
Delivery evidence opens the finance path.
Finance
Approved work becomes driver settlement.
Finance
Receivables and payables keep moving.
Finance
Fuel records support tax and margin views.
Fleet
Asset signals open service work.
Compliance
Risk signals become accountable controls.
Insights
Owned history compounds into decisions.
Arrows show the intended D-ONE handoff direction. D-ONE detects each trigger, runs the next automated action, and records the event in its audit history. Every stage is sample data; no records are created, persisted, or pushed to an external service.
D-ONE automation catalog / sample rules
| Trigger | Condition | Automated action | Resulting record / workspace | Owner / approval needed |
|---|---|---|---|---|
01POD captured | Load status = delivered and document passes review | Auto-generate invoice | Invoice / Finance | Billing lead approval before send |
02Invoice paid | Payment clears the approved receivable | Auto-release settlement | Settlement / Finance | Finance approval on first release |
03Low stock threshold hit | On-hand quantity ≤ reorder point | Auto-create reorder | Purchase order / Fleet | Parts manager approval |
04HOS violation risk | Projected drive time breaches configured limit | Block dispatch assignment | Dispatch hold / Compliance | Safety manager override |
05COI expiring | Expiration is within 30 days | Send renewal reminder | Insurance record / Compliance | Compliance owner review |
06Claim reported | Incident includes loss or injury signal | Open claim file | Claim file / Compliance | Risk owner approval |
07Part issued to work order | Part is scanned against an active work order | Attach part to maintenance record | Asset history / Fleet | Technician confirmation |
08Truck enters shop for service | Asset status = in shop | Create road-service work order | Work order / Fleet | Fleet manager assignment |
09Customer hits credit limit | Open balance ≥ approved credit limit | Hold new loads | Credit hold / AR/AP | Finance release required |
10Load delivered on time | Actual delivery ≤ promised delivery | Update lane performance | Lane insight / Insights | Operations review only |
D-ONE workflow map / owned exchange
D-ONE detects the trigger, runs the automated action, updates the owned record, and writes the event to audit history at every handoff.
POD → invoice → settlement
Owned load, invoice, and settlement IDs stay linked.
Automatic exchange / sampleAsset event → risk control
Service, qualification, and safety signals share the same history.
Automatic exchange / sampleContract → credit → payment
Commercial terms and account health inform finance work.
Automatic exchange / sampleEnriched signal → labeled insight
Outside context can inform analysis without owning the record.
Automatic exchange / sampleDispatch → asset readiness
Assignment checks equipment availability before movement.
Automatic exchange / sampleRisk status → dispatch guardrail
Authority, HOS, COI, and claims signals can stop unsafe work.
Automatic exchange / sampleApprovals & guardrails
Automation can prepare an invoice, settlement, or payment instruction. A named owner approves the release.
D-ONE detects triggers, evaluates conditions, runs actions, routes approvals, and records every outcome in its own audit history.
Every decision, action, status, exception, approval, and audit event is reviewable in the D-ONE record.
If a connection is ever added, it can execute or enrich a selected step only. It is never part of D-ONE’s automation engine or the owner of its history.
Stage-ready gate
Trigger inventory
MappedEvery automation names a clear event that can be observed in D-ONE.
Condition logic
MappedRules state the threshold or review condition before an action runs.
Action ownership
MappedThe resulting record and workspace are explicit for every row.
Approval boundary
ReadyMoney movement, dispatch blocks, and overrides have a named owner.
History retention
ReadyAutomation events, outcomes, and exceptions remain in D-ONE history.
Optional connections
Demo onlyOutside services remain disconnected enhancements and are not dependencies of D-ONE automation.
Exception handling
Stage-readyFailed or disputed actions route to a visible work queue instead of disappearing.
Production controls
Demo onlyAuthentication, storage, imports, API calls, persistence, and live analytics stay disabled.
Connected workspace routes