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 the systems within the type — brakes, doors, bogies, each subdividing further. Codes are unique within a type. A node that data refers to is deactivated rather than deleted. The tree starts in one of two ways, chosen when the type is created and fixed afterwards:
  • Seeded from EN 15380-2. The standard’s main groups and subgroups are created as template nodes. Template nodes are locked — no rename, move or delete, only deactivation. Custom nodes can be added under any node and must carry EN 15380-2 codes themselves.
  • Empty. The fleet builds its own tree. Every node is custom and fully editable.
Product groups matter well beyond this page: they classify defects and warranty claims, they structure inspection campaigns, and they are the grouping dimension on the dashboards.

​
EN 15380 mapping

Each node carries a mapping to an EN 15380-2 product group. It is maintained in A7 manager only and never imported.
  • On a seeded tree the mapping is the node’s own code and cannot be edited.
  • On an empty-start tree the mapping is optional and set per node in the node dialog. A valid value is a main-group code (R), a subgroup code (RB), or a subgroup code followed by free text (RB1). Anything else is rejected.

​
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

Choose whether its product group tree is seeded from EN 15380-2 or starts empty. The choice cannot be changed later.
2

Extend the product-group tree

Add the groups the fleet actually uses. On an empty-start tree, set each node’s EN 15380 mapping as you go.
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.