Assets

An asset is anything in your plant that you track for maintenance: a CNC mill, a forklift, a paint booth, a server, a building’s HVAC unit. The asset register tells you what you own and where it is, what it’s costing you, how healthy it is, and what it’s doing for you.

The asset card

Every asset row gives you:

• Identity — code (the asset tag printed on the QR sticker), name, manufacturer, model, serial number.
• Where it lives — its functional location in the plant (e.g., “Building 1 / Line 3 / Press station”).
• What it does — if the asset is a production machine, the work-center link tells the scheduler.
• How it’s tracked — its meter unit (hours, kilometers, cycles) and the latest cumulative reading.
• What it’s worth — purchase cost, warranty supplier and end date, lifetime maintenance cost so far.
• What’s coming — the next planned WO if one is scheduled.

Asset classes

Assets are grouped into classes — a small, organization-curated taxonomy like CNC_MILL, FORKLIFT, HVAC_UNIT. The class drives the defaults a new asset inherits:

• Default failure-catalog filter (a CNC mill operator sees CNC-relevant problems, not forklift problems).
• Default maintenance-plan templates (a CNC mill comes with the standard annual overhaul plan).
• A default account-code label for maintenance costs (a free-text accounting code such as 6151, copied onto new assets as a hint — you can override it per asset).

You can rename a class freely; KPIs reference the stable code, not the human label. Classes are hierarchical: CNC_MILL rolls up into MACHINE_TOOL rolls up into PROD_EQUIP.

Functional locations

A functional location is a logical slot in your plant — a position, a role — that one asset occupies at a time. Think of it as the floor plan: plant → building → line → station → position.

The point of functional locations is to make KPIs survive a like-for-like replacement. When you retire Press SN-AL-44720 and install Press SN-AL-44990 in the same slot, the new asset takes the same functional_location_id. Reliability metrics (MTBF, availability) roll up against the location, so “Line 3 — Press station” has continuous history even though the physical asset has changed.

The functional location can optionally cross-link to a warehouse bin so that parts-picking knows where to deliver the spares.

Criticality

Every asset carries an A / B / C criticality rating:

• A — Critical. Stops the line or the building if it fails. Drives priority in the dispatcher inbox, faster approval routing, more frequent preventive maintenance.
• B — Important. Production continues but with degraded capacity or quality.
• C — Non-critical. Spare equipment, low-impact infrastructure.

Criticality combines with the problem-code severity to compute the SLA tier on new work requests — a problem on an A-critical machine has a much faster due-by than the same problem on a C asset.

Lifecycle status

Assets progress through a controlled lifecycle:

1. PLANNED — On order or being installed. KPIs don’t compute yet.
2. COMMISSIONED — Installed and accepted; maintenance plans activate.
3. OPERATIONAL — In service. The normal state.
4. IN_MAINTENANCE — Currently down for an open WO. This state is driven automatically by the WO’s downtime tracking — you don’t set it manually.
5. IDLE — Mothballed or on standby. Plans pause; KPIs ignore the period.
6. DECOMMISSIONED — Retired from service. The row stays for historical reporting; by convention you only open disposal work against it.
7. DISPOSED — Sold, scrapped, or otherwise disposed of. Terminal.

Moving an asset to DECOMMISSIONED or DISPOSED is a controlled step: it needs the dedicated decommission permission, and Beelocity blocks it while the asset still has active sub-assets under it.

is_active is the soft-delete flag — separate from lifecycle. An inactive asset is hidden everywhere; lifecycle is its operational state.

Sub-assets

Assets can be nested. A press has a hydraulic pump as a sub-asset; a fleet has individual vehicles. WOs written against the sub-asset roll up to the parent for KPI purposes — so the press’s availability accounts for the pump being down too.

Warranty

Assets carry an optional warranty window: supplier (a partner), start date, end date, free-form notes. When a breakdown lands inside the warranty window, the WO UI flags “warranty applicable” so the planner can route the repair to the OEM rather than book it as in-house cost. A KPI surfaces the gap — work the org did in-house when the OEM was on the hook.

Documents

Each asset can store linked documents — manuals (PDF), drawings (CAD/PDF), warranty certificates, calibration certificates, photos of the nameplate so the serial doesn’t have to be re-keyed. Categories drive how the documents tab is grouped.

Quick navigation from an asset

The asset detail page is a hub — it carries shortcuts so you don’t have to hunt through other modules:

• Open work centre — A button in the page header. Click it to jump straight to the work centre this asset represents (the production hub the scheduler considers when planning around maintenance). The button is only visible when the asset is wired to a work centre.
• Next scheduled work order — A link inside the Scheduling section of the overview. When a maintenance plan has generated the next planned work order on this asset, that link takes you to it. The link disappears once the work order closes.

Counter rollover warning

Counters (kilometres, engine hours, presses cycles) wrap around to zero when they hit their ceiling. Beelocity normally knows the ceiling from a per-asset value set in the asset’s metadata — for example, a press might roll over at exactly 999 999 cycles.

When that per-asset value is missing, the system uses a default ceiling based on the unit (1 000 000 km, 100 000 hours, 100 000 000 cycles). It still works, but it can hide a real rollover: if the equipment actually wraps at a different number, readings can roll over silently against the default.

The asset detail page shows a yellow warning banner when the default ceiling is in use:

Default counter rollover ceiling in use — This asset is using the default counter rollover ceiling — set a per-asset value to avoid stale readings rolling over silently.

The asset list page shows the same status as a small “Default counter” chip in the Warnings column, so you can see at a glance which assets still need the per-asset value set. To clear the warning, set the asset’s metadata.counter_max_value to the equipment’s real rollover point — the next meter reading you log will silence the flag.