Equipment & Asset Utilization¶
Location: Dashboards → Asset Utilization
Track equipment usage, idle time, and utilization metrics across your fleet. All data is based on accelerometer movement detection from Wirepas EverTag sensors.
The Equipment dashboard showing fleet KPIs, utilization chart, and asset table.
Overview Tab¶
Fleet-level summary with four KPI cards:
| KPI | What it shows |
|---|---|
| Total Assets | Number of assets (filtered by selected type) |
| Assets Used | Assets with detected movement in the period |
| Avg Utilization | Active Hours ÷ (Active + Idle) × 100% |
| Idle Time Share | Share of measured time the assets were reporting but not moving |
Charts:
- Utilization by Asset — top 10 assets ranked by utilization rate. Hover for exact percentage.
- Fleet Active vs Idle — donut chart showing the split between total active and idle hours.
Asset Utilization Details table — every asset with Active Hours, Idle Hours, Utilization %, Sessions, and data source (Accel or Pos). Click any row to drill into Per Asset details.
Per Asset Tab¶
When no asset is selected, shows a fleet comparison:
- Active vs Idle by Asset — stacked horizontal bars. Click a bar to select that asset.
- All Assets table — click a row to see daily details.
When an asset is selected, shows its individual breakdown:
- KPI cards — Active Hours, Idle Hours, Utilization %, Movement Sessions
- Daily Active vs Idle — stacked bar chart by date
- Daily Utilization Rate — line chart of utilization % over time
Per Geofence Tab¶
Shows how much time assets spent in each geofence zone.
| Column | Description |
|---|---|
| Geofence | Zone name |
| Type | Geofence category (Storage, Office, etc.) |
| Total time | Time spent inside this geofence, from consecutive position intervals |
| Active time | Accelerometer movement time, prorated by zone share |
| Assets | Number of distinct assets detected |
| Per asset | Breakdown per asset with time, visits, and position pairs |
Total Time by Geofence chart — stacked horizontal bars. Green = active movement time, cyan = remaining time in zone. If accelerometer data is available, the chart shows both; otherwise just total time.
Outside Geofences — a virtual zone showing time between tracked positions that were not inside any geofence.
How time is calculated
Total time is the sum of intervals between consecutive position reports while the asset is inside a geofence. Gaps longer than 2 hours are not counted (the asset is assumed to have left). A zone must have at least two position fixes to appear. The last position's remaining time to the query end is included.
Active time vs Total time
Total time = time spent in the zone (from positions). Active time = accelerometer-detected movement, distributed across zones in proportion to time spent. Active time is always ≤ total time.
Trends & Analysis Tab¶
Understand usage patterns across days and hours.
Movement time per weekday and accumulated movement per hour of day, for the selected assets and period.
KPI cards:
| KPI | Description |
|---|---|
| Total Active Time | Accumulated movement hours from accelerometer |
| Avg Active / Day | Average per day (only days with activity) |
| Busiest Day | Weekday with the highest average active hours |
| Peak Hour | Hour of day with the most activity |
Charts:
-
Daily Active Hours — bar chart with one bar per day. Color intensity shows relative activity (green = peak, yellow = moderate, gray = low). Cyan trend line shows direction. Tooltip includes asset count.
-
Which Days Are Busiest? — weekday averages (Mon–Sun). Identifies weekly usage patterns.
-
Hourly Utilization — accumulated accelerometer movement time per hour of day (0–23). Orange bars matching the energy dashboard style. Tooltip shows percentage of total.
Filters¶
| Filter | Effect |
|---|---|
| Time range | Last 24h, 7 days, 30 days, or 90 days |
| Asset Type | Select one or more types in the dropdown (empty = all). Multi-select with checkmarks. |
| Asset | Focus on a specific asset |
Configuration¶
Click the Configuration button (top-right) to open the settings modal.
Asset Types — checkbox grid matching the Cold Chain configuration style. Select types to filter the dashboard. Leave all unchecked for all types. Selection is persisted in your browser (localStorage) and remembered across page loads and tab switches.
Working Hours — define the weekly schedule used for utilization calculations:
- Configuration Name — label for this schedule (e.g., "Standard Shift")
- Day toggles — enable/disable each day (Mon–Sun)
- Shift times — start and end time per day (e.g., 08:00–16:00)
- Saved to the backend and shared across the organization
Working hours affect utilization %
Available hours = sum of enabled shift hours in the selected period. If no schedule is configured, a default 8h/day Mon–Fri is used.
How active, idle and no-data are measured¶
The Wirepas EverTag reports two cumulative counters: total_time_s (how long
the tag has been running) and movement_time_s (how much of that it sensed
motion). Because they are cumulative, a silent stretch between two reports
loses nothing — the next report's delta says exactly how much of it was spent
moving. The tag also wakes on a movement interrupt, so silence is itself
evidence of stillness.
Each period is therefore split three ways, and the three always add up to the whole period:
| Bucket | Meaning |
|---|---|
| Active | Seconds the accelerometer sensed motion |
| Idle | Seconds the tag accounted for without motion — genuinely standing still |
| No data | Seconds the tag was off, rebooting, or out of the mesh |
"No data" is deliberately kept out of "Idle": not knowing is not the same as standing still, and folding the two together made offline tags look like well-parked ones.
Utilization is measured against active + idle, not against the working-hours schedule. A cleaning robot that runs at 02:00 and a forklift that runs at 10:00 are then judged on the same terms.
The schedule is not lost, though — it comes back as an observation. The Movement vs working hours panel on each asset splits the measured motion into the part that fell inside the scheduled shifts and the part that fell outside, with a per-day breakdown, and the asset tables carry an In Hours column for scanning the fleet. For a robot configured to clean at night that reads ~98 % off-hours, which is the answer you want — not a 0 % utilization that looks like a broken asset.
Reporting interval¶
The measurement and reporting interval is configured per tag from the Wirepas app, so it differs across a fleet: production has tags reporting roughly every two minutes and others every fifteen. The counter's step size is therefore inferred per tag from its own data rather than assumed, so a short outage is detected just as reliably on a fast-reporting tag as on a slow one.
Daily breakdowns are bucketed on local days, so a night shift lands on the day it belongs to rather than being split across two bars by UTC midnight.
Data Sources¶
| Metric | Source |
|---|---|
| Active / idle / no-data hours | Accelerometer movement_time_s and total_time_s from Wirepas sensor data (counter step inferred per tag) |
| In-hours / off-hours movement | The same measurement clipped to the shifts in the working-hours schedule |
| Total time in geofence | Position report intervals from rtls_positions (2-hour gap threshold) |
| Utilization % | Active hours ÷ (active + idle) — the time the tag accounted for |
| Positions | Wirepas mesh triangulation via anchors |