Skip to content

Transport Configurations

Build the vehicle combinations the business sells and prices, and set what each one is priced as and sent to iDrv4 as.

Fleet → Transport Configurations (/operations/fleet/transport-configurations). The vehicle combinations this business sells and prices — a rigid, a semi, a B-double, a road train. Rate cards price against them, and dispatch can start a unit from one.

Two fields in Identity decide how a configuration is priced and what iDrv4 is told. Its Name does not decide either, so renaming a configuration is just a label change.

  • Priced as is the vehicle type the configuration’s rate entries are priced against. Same as the power unit uses the power unit’s type. For example, a B-Double is led by a prime mover but is priced as the B-Double type. Changing this field moves the configuration’s pricing, so change it only on purpose. If a configuration is priced as a type that has since been retired, that type still shows in the list marked retired, not in the palette, so saving another edit doesn’t clear it.
  • iDrv4 service type is what iDrv4 is told the vehicle is, for example 8T12P. Suggestions come from the types iDrv4 is known to have. If you enter one it doesn’t have, the hint warns you that iDrv4 would fall back to its default (2T4P). ⚠️ If you leave this blank, it is worked out from the configuration’s name. In that case, renaming the configuration can change what iDrv4 is told.
AreaWhat it does
Register (left)Every configuration. Search by name or code; Show retired includes retired ones.
IdentityName, Code, regulatory Class, In service, Description, Priced as, iDrv4 service type.
Combination (canvas)The vehicle, drawn to scale, with what is coupled behind it.
ReadoutOverall length, axles, pallet spaces, tare mass and rated GCM, each checked against the class limit.
Equipment (palette)Power units and trailers you can drag onto the canvas.
  1. New configuration, or pick one from the register.
  2. Drag a power unit onto the canvas first — Save refuses without one.
  3. Drag trailers on behind it. A unit may only follow one that offers the coupling it needs (a kingpin needs a fifth wheel, a drawbar needs a tow coupling). A coupling nobody recorded is unknown and is never a refusal.
  4. Read the readout and the warnings under it. A figure over the class limit is flagged; when everything checks out it says so.
  5. Save. Revert throws away unsaved changes.

Rated GCM is read off the power unit, never added up across the combination. A figure nobody recorded reads Not specified, with Missing from: naming the equipment — click a name to fill it in. Overall length reads Not specified until the power units are measured; that is expected, not a fault.

Click a palette tile, a unit on the canvas or a Missing from name to open the equipment editor. It edits the type (every configuration using it), not this configuration: axles, axle configuration, length, pallet spaces, tare, GVM, GCM, payload, deck length/width/height, rear coupling, and the lowest licence class a driver needs. A power unit also has Allowed trailers — tick the trailer types it may pull and how many. Not configured means unknown, so no rule can check it yet.

Deck dimensions matter beyond this page: the dispatch load plan uses them, and a deck with no recorded size produces no plan. Deck height is the usable load height, not the 4.3 m road limit.

New equipment adds a power unit or trailer type. Show retired in the palette includes retired equipment.

Retire hides a configuration (or a piece of equipment) from new use. If rate entries, configurations or vehicles still depend on it, the first press is refused with the counts; press Retire again to confirm. Rate entries that referenced it are left untouched.