Skip to main content
The Vehicle Taxonomy section organizes your product lineup into a hierarchical structure that supports document management, maintenance scheduling, and parts compatibility.

Taxonomy structure

The platform uses a three-level hierarchy: CategoriesFamiliesTypes. Each vehicle can be assigned one type per organization, which automatically links it to the corresponding family and category. Parts are orthogonal, and can be associated with individual vehicles.
  • Categories: High-level groupings (e.g., “Adventure,” “Cruiser,” “Marine”)
  • Families: Product lines sharing design characteristics (e.g., “Tenere series,” “Sportster line”)
  • Types: Specific models (e.g., “Tenere 700,” “Sportster 883”)
  • Parts: Components and hardware installed on vehicles

Vehicle categories

This tab lets you manage the highest level of vehicle organization with broad product categories. Add new categories with the add category button. Each category needs at least a name, optionally a description can be added.
The system prevents deletion of categories that still have families assigned to them.
Categories serve as the foundation for organizing your entire product portfolio and can be used to share documents, maintenance schedules, etc. with the respective vehicles.

Vehicle families

Similarly, this tab lets you organize related vehicle types that share common characteristics within each category. Family management:
  • Create families using add family button
  • Select parent category and define family characteristics
  • Group models with shared design, features, or market positioning
  • Delete unused families (system prevents deletion if types exist)
Families enable bulk management of related products and streamline maintenance scheduling across similar vehicles.

Vehicle types

On the lowest level, this tab lets you define specific vehicle models that customers purchase and register in your system. Type management:
  • Create specific models using add type button
  • Associate with parent family and define detailed specifications
  • Configure model-specific features and capabilities
  • Delete unused types (system prevents deletion if vehicles exist)
Vehicle types represent the actual products in your catalog and serve as the basis for vehicle registration, maintenance scheduling, and parts compatibility. Vehicle type may also be associated with additional properties such as fuel type, maximum speed, or weight class. These properties may be used to custom-tailor UI elements in the mobile app(s).

Vehicle parts

Vehicle parts can be assigned to vehicles to represent installed components, hardware, or accessories. They are independent of the vehicle taxonomy and can be used to track both factory-installed and aftermarket parts. Vehicle parts are particularly useful for:
  • Managing component inventories
  • Keeping track of serial numbers and warranties
  • Associating firmware updates with specific hardware
The detail view lets you additionaly declare if a vehicle part is updateable (firmwares may then be associated with it) and add a part image that may be shown in the mobile app to vehicle owners. If you enable firmware updates for a vehicle part, the last box will appear, allowing you to manage firmware versions associated with this part. You can add new firmware versions, and set existing ones as active / inactive to control deployments.
By default, the latest active firmware version will be offered to vehicles with this part installed (following semantic versioning).
By defining “development” parts and assigning them to test vehicles, you can test firmware updates before rolling them out to production vehicles.
I