ClideyEvery shipment, vehicle and lane in one working picture.
Transport management, telematics and customer systems each hold part of the story. WhoDB connects them, models shipments and capacity once and gives planners tools built on live data.
In placeTMS, telematics and ERP stay where they are
1shipment model for planners and customers
Livestatus from the systems that hold it
Per personaccess for partners and staff
IN THE PRODUCT
One project for planning and operations.
Pick a point on the left to see where it lives on the screen. Every screen shown here comes from the Clidey ERP demo project.
APP.WHODB.COM / APPS / CONTROL-TOWERDARK
HOW IT WORKS
How a shipment stays visible from order to delivery.
01
Connect the systemsConnect the TMS, telematics feeds and ERP in place.02
Model the shipmentDefine shipments, stops, vehicles and lanes as shared entities.03
Plan on live dataPlanners work in apps that read current status and capacity.04
Answer customersCustomer service sees the same shipment record, with its history.SHIPMENTS
Orders, stops and vehicles, related once.
A shipment knows its order, its stops and the vehicle carrying it, so status questions have one answer.
✓Shipment, stop and vehicle entities✓Declared relationships between them✓Sample rows for every entity
Shipment9 PROPERTIES
shipment_idStringRequiredProminent
order_idStringRequiredNormal
statusStringRequiredProminent
vehicle_idStringNormal
etaDateNormal
laneStringNormal
LINEAGE
See what every status update feeds.
Trace a telematics update through to the apps and customer views that rely on it.
✓Sources to entities to apps✓Run status on every transform✓Impact before any change
Lineage6 NODES
SOURCE
SOURCE
TRANSFORM
TRANSFORM
ENTITY
APP
What it changes for each team
PLANNERSCapacity you can see.Loads, vehicles and lanes in one planning view.
CUSTOMER SERVICEOne answer per shipment.Status and history from the same record operations uses.
FINANCECost per lane.Shipment costs connected to the work that created them.
THE DETAILS
For the people who will ask.
The specifics your architects and security reviewers will want before a rollout.
SOURCESTMS, telematics, ERP and partner files
MODELShipment, stop, vehicle and lane entities
APPSBuilt in the WhoDB app editor
CHANGESDraft, review and promote
ACCESSProject members, roles and teams
DEPLOYMENTWhoDB Cloud or Managed Private
EXAMPLE WORKFLOWOne
Shipment record for planning and service.Planners and customer service read the same shipment, so the status a customer hears is the status operations sees.
Common questions
No. WhoDB connects to it in place and builds a shared model on top.
Keep exploring Industries
Industries overview →01Manufacturing→Testable pricing logic and quote records.02Retail→Allocation plans from your own rules.03Warehousing and distribution→Receiving, put away, picking and stock.04Banking→Customer, account and risk data in one model.05Accounting and finance→Close faster with reconciled, traceable numbers.06Insurance→Policies, claims and pricing on one model.07Wholesale and trade→Orders from every channel in one model.08Energy and utilities→Assets, readings and work orders connected.09Healthcare operations→Capacity, supplies and staffing on shared data.