Fleet assets

This page describes the assets sub-module in src/cluster_erp/modules/fleet/assets/. A fleet asset (FleetAsset) is one vehicle, trailer, or machine. An asset class (FleetAssetClass) groups assets and decides whether they are powered and which meters they get at birth. The module overview is on fleet module.

Scope and source¶

• Defined in: src/cluster_erp/modules/fleet/models.py (FleetAssetClass, FleetAsset), assets/services.py (FleetClassService, FleetAssetService), assets/routes.py, assets/schemas.py, and assets/metadata.py.
• Count: 2 tables, 10 routes (@...router. decorators in assets/routes.py), 6 ActionMeta entries in assets/metadata.py.

Asset fields¶

Asset class fields¶

The form edits default_meters as one key per line (src/cluster_erp/modules/fleet/assets/services.py:112-116). A key without a meter template is skipped without error (src/cluster_erp/modules/fleet/meters/services.py:145-172).

Statuses and actions¶

An asset is draft, active, in_maintenance, inactive, or disposed (src/cluster_erp/modules/fleet/models.py:46-52). The service holds the allowed transitions in _TRANSITIONS and refuses others with FLEET_INVALID_STATUS (src/cluster_erp/modules/fleet/assets/services.py:41-48, src/cluster_erp/modules/fleet/assets/services.py:277-305).

Send to Maintenance asks for the work to be done, the mechanic or service party, a planned date, and notes (src/cluster_erp/modules/fleet/assets/metadata.py:110-135). The service creates the work order and releases it at once (src/cluster_erp/modules/fleet/assets/services.py:307-338).

stateDiagram-v2
 [*] --> draft
 draft --> active: activate
 active --> in_maintenance: send_to_maintenance
 in_maintenance --> active: return_to_service or last work order completed
 active --> inactive: deactivate_asset
 in_maintenance --> inactive: deactivate_asset
 inactive --> active: activate
 active --> disposed: dispose
 inactive --> disposed: dispose
 in_maintenance --> disposed: dispose

In prose: an asset starts as a draft and becomes active through Activate. From active it can go to maintenance, out of service, or disposal. A work order completion returns an asset in maintenance to active when no other order is open (src/cluster_erp/modules/fleet/workorders/services.py:246-265). Disposal is final; no transition leaves disposed (src/cluster_erp/modules/fleet/assets/services.py:41-48).

Routes¶

The list response hides tenant field values the caller may not see, through redact_extra_items (src/cluster_erp/modules/fleet/assets/routes.py:74-81). See field and row access.

Constraints and validation¶

• Creating an asset checks that the class exists and that plate and vin are free among live rows (src/cluster_erp/modules/fleet/assets/services.py:199-233).
• Tenant field values in extra are validated against their definitions, with the asset row as context for class-scoped fields (src/cluster_erp/modules/fleet/assets/services.py:233-235). See tenant fields.
• A new asset gets the meters its class declares and the reminders of class-scoped maintenance plans at once (src/cluster_erp/modules/fleet/assets/services.py:238-249).
• A class code is unique among live classes; a duplicate is refused with a conflict (src/cluster_erp/modules/fleet/assets/services.py:68-76).
• DELETE sets deleted_at on the asset and on its live reminders. The code comment separates this record-level soft delete from the operational status inactive (src/cluster_erp/modules/fleet/assets/services.py:340-363).

Terms introduced¶

Related pages¶

• Fleet module
• Meters and fuel
• Maintenance and work orders
• Tenant fields
• API reference for this module

Verified against commit 92f8051 on 2026-11-13.