Skip to main content
A vehicle type is a model of vehicle rather than an individual one. Everything structural hangs off the type, so it is described once and applies to every vehicle of that type. The page is a grid of types, with a drawer holding the two trees that define a type’s structure: its product groups, and the mounting positions within them.

​
Vehicle type

A code and a name, unique within the project. Vehicles reference it, and so do maintenance plans and inspection templates.

​
Product groups

A tree of systems within the type, following the EN 15380-2 standard — brakes, doors, bogies, each subdividing further. Standard top-level groups are seeded automatically when a type is created and marked as standard; anything deeper is defined here. Codes are unique within a type. Product groups matter well beyond this page: they classify defects, they structure inspection campaigns, and they are the grouping dimension on the dashboards.

​
Slots

A slot is a place a component can sit: “bogie 1, axle 2, left wheel”. Each slot belongs to a product group and has a position plus a human-readable label, and can be marked as required. Two things make slots more than labels:
  • Each slot lists which component types are allowed in it. The mounting import rejects the whole file if a component’s type is not on that list.
  • Slots nest, so a bogie slot can contain axle slots.
Positions are unique per type and product group. The position string is also what the measurements import matches against, so it has to agree with whatever the source system calls that position.

​
Order of setup

Because imports resolve codes rather than identifiers, this page comes first in a new project:
1

Create the vehicle type

Its standard product groups appear automatically.
2

Extend the product-group tree

Add the subgroups the fleet actually uses.
3

Define component types

On Component Types — slots need them to exist.
4

Define slots

With their allowed component types.
Only then can vehicles, components and any imported operational data resolve.

​
Tables

Field reference

assets_vehicletype, assets_productgroup and assets_vehicletypeslot, plus the join table listing which component types each slot allows.

​
Roles

Reading requires Asset Manager. Creating and editing requires Project Admin.