Operations
Downtime Tracking
Record when assets are not working, categorized correctly, to power reliability metrics like MTBF, uptime percent, and availability cost.
Updated June 5, 2026
Logging downtime
There are two ways to record it. From a work order: marking a critical asset In progress prompts whether it is down, starting a period that ends when you close the work order. Standalone: Asset detail then Downtime tab then Log downtime, useful for planned shutdowns. Each entry captures start and end timestamps, reason category, optional cost impact, and linked work orders.
Reason categories
The category shapes the data:
- Failure: the asset broke; counts against MTBF and reliability
- Planned: scheduled shutdown; counts against uptime but not reliability
- Environmental: weather, power, or external causes
- Operational: operator-induced, revealing process issues
Category discipline matters; logging everything as failure or planned skews metrics.
Metrics and alerts
MTBF equals total uptime divided by number of failures (failure category only). Uptime percent equals uptime over uptime plus downtime (all categories). Availability cost equals downtime hours times asset hourly cost. Under Settings then Alerts then Downtime auto-start, alerts on critical assets can auto-start a period for IoT equipment.
Capture short outages, do not backfill from memory, and close windows when assets return.
Still need help?
Reach out for broken behavior, account-specific help, or billing questions.