Getting around eTMS
The shell, the menu, how a page is put together, how to read the tables — and how to make the workspace your own.
Choose a walkthrough and jump straight into the eTMS workspace. Sample data. Real controls. Room to experiment.
Connecting to the public showcase… Browse the library below.
The shell, the menu, how a page is put together, how to read the tables — and how to make the workspace your own.
The ⌘K palette: one query across every context you are allowed to see, grouped by where each record lives — and what it means when something is not there yet.
The first screen you see every morning, arranged around your job: pick widgets, size them, keep several boards side by side.
The board answers one question all day: is anything going wrong? Learn the search grammar, the sort and grouping, and the five dispatcher tools that turn a wall of trucks into a short list.
You were off for a night, a weekend or two weeks. This is the one screen that answers "what happened on my trips while I was away" — per trip, in one modal, borrowed trucks included.
A four-hour wait at a border is not traffic, driving time or rest — and until somebody says how long it is, no ETA knows about it. Learn where the board shows a queue, how much to trust the figure, and how to file one.
Take a transport order from the client to the trips list: the two fields that matter, demo data for the rest — and the route, tolls and save shown live.
Compare truck and crew recommendations using driver scores, pickup distance, program availability and equipment needs. Practise reviewing a warning and saving your choice.
Clients run the same routes again and again — apply a stored route to a new trip instead of retyping its stops, and manage the routes the platform records by itself.
Five trucks down one road is one phone call, not five typings. Plan the shared route once, rank the fleet by who is closest to it, and let the platform create one trip per truck.
Set a standing shuttle up once and its trips plan themselves. Learn the rhythm editor, the materializer, and what "next departure" really promises.
Romania's e-Transport code is the client's to obtain and the carrier's to show. Learn where the requirement comes from, how a code is recorded and withdrawn, and what the dispatch board does about a missing one.
You are about to leave, and the trip still owes somebody three small things. Learn to hand one of them to the trip itself — a moment, an action, and what happens when it breaks while you are away.
Keep the fuel stations, parkings, customs offices and depots your drivers actually use — hand-added or bulk-imported — as a layer on every map.
A truck's standing dispatcher, client and trailer live in one place — and every trip you plan reads from it. Assign them in bulk, see what a change costs, and read the history back.
Two drivers, one truck: seat a co-driver on a trip, then read what changes on the board — the crew, the phone numbers, the tachographs, and an arrival time that stops looking like a mistake.
Leaves, swaps and parked trucks all end the same way: an empty seat. Read the board, rank the candidates, and plan a swap end-to-end.
File an employee request on their behalf, read the conflicts it raises before saving, then decide it from the approvals queue.
Five sources, one grid: trips, leaves, driver changes, recurring series and planned events. Learn to read a bar at a glance — then schedule one yourself.
One row per truck: position, crew, current order, ETA, problems — and the schedule remarks that explain the trucks standing still.
Register a vehicle end to end — and learn the one rule that surprises everyone: a model spec is copied onto the truck, not linked to it.
Put the manager's car and the parts van in the fleet register — and learn why a car can never turn up in a vehicle selector.
The mechanic’s own app: the jobs at your workshop, the clock, the photos that prove what you found, and the checklist that resets the intervals.
Book a delivery in with a barcode scanner: known codes fill the line in for you, unknown ones get named once and answer forever after.
The Estimate tab shows a total and never says why. Follow one charge from the rule on the client’s profile to the line it produces on a trip — including a rule that bills only when the trailer is right.
What would this trip have been worth on other terms? Re-price a finished job against an edited contract, a different route and another client’s deal — then ask the same question across a whole month.
Your own legal entities are the spine of the system — employees belong to one, trips are run by one, invoices are issued by one. Register one end to end.
Three things here are called a "role", and only one of them grants access. Create one, decide what it may do, and hand it to a colleague.
Someone's away — don't widen their stand-in's roles forever. Lend the absent person's capabilities for a period, then watch the loan end itself.
The dropdowns all over eTMS are lists you own. Add an entry and watch its code mint itself — then retire one, because nothing here is ever deleted.
Your company's name on the tab, your logo in the rail, your accent on every button — one page whitelabels the whole app, sign-in included.
Bring old records in without fear: map a file onto eTMS fields, dry-run every row, and only then write anything.
Every write in eTMS leaves a record — who, what, when, and with which payload. Learn to narrow the trail and read one entry to the bottom.
Routing, weather, fuel prices — capabilities arrive as plugin modules. Install one from the catalog and watch the platform converge it to running.
Turn a Superset dashboard into a report your colleagues can open — and decide both who may open it and which rows they see inside.