Maintenance indicators allow you to evaluate asset performance and operational efficiency based on data recorded in the platform, such as work orders, downtime, and operation windows.
This article gathers all metrics calculated by the platform, explaining how each one works and how to interpret them correctly.
Important Definitions
Before understanding each indicator, it is essential to know the concepts that appear in the calculations:
Failure: Work order created for an asset, associated with a category configured with the “Include in indicators” option enabled.
To learn how to create categories, check this article.
Filtered period: Date range selected in the reports (e.g.: last 30 days, last quarter). All calculations use this period as a reference.
Downtime: Total time the asset was unavailable due to failures. Calculated from work orders with an unavailability status. If overlapping downtimes occur, the system considers only the union of these periods to avoid double counting.
Uptime: Time the asset was operating during the filtered period. Calculated by subtracting downtime from the expected operating time.
Expected time: Total time the asset should be available in the filtered period.
Standard availability: 24/7 operation is considered.
Operational availability: Only the configured operating window is considered.
Operation window: Configuration of days and hours when the asset is scheduled to operate. Directly affects operational availability.
Repair Time: Total time required to repair a failure, counted from the start to the conclusion of the work order. Overlaps between repairs are not eliminated.
Time to Action: Time between the creation of the work order and the start of service (or conclusion, if never started).
Availability
Availability shows, as a percentage, the time an asset was operating as expected in a given period.
Standard Availability
Considers that the asset must operate 24 hours a day, seven days a week. The expected uptime is the total hours of the filtered period.
Example: 30-day period = 720 expected hours. If the asset was stopped for 72 hours, availability will be (720 – 72) ÷ 720 = 90%.
Operational Availability
Considers the configured operation window for the asset, adding only the expected hours in the filtered period.
Example: Operation window of 8h/day, 5 days/week = 160 expected hours in the month. With 8 hours of downtime, availability will be (160 – 8) ÷ 160 = 95%.
Uptime Calculation
Uptime corresponds to the filtered period minus the downtime recorded in work orders marked as unavailable. Overlapping downtimes are unified to avoid double counting.
Propagation rules:
Failure in child asset → parent unavailable in the same period.
Failure in parent asset → all children unavailable in the same period.
Failure in child does not affect siblings at the same level.
Locations and Production Lines
For locations, availability is the average of the elements directly below. For production lines, it is recommended to register the line and its components as assets to ensure correct propagation.
MTBF – Mean Time Between Failures
MTBF indicates the average time an asset remains operating between one failure and another.
Calculation modes:
Total Period (Accumulated): considers from asset creation until the end of the period, including failures before the interval.
Selected Period: considers only time and failures within the chosen period.
Calculation in grouped assets: For locations or parent assets, MTBF is the average of the MTBFs of the direct assets below, avoiding distortions in total time.
Reliability
Reliability measures the probability of an asset not failing in a defined period, calculated based on MTBF. The higher the MTBF, the higher the reliability. Changing the reliability period in the reports changes the projection.
Example: MTBF of 20 days and reliability period of 10 days → reliability of about 60%.
MTTR – Mean Time to Repair
MTTR shows the average time required to restore an asset after a failure.
How it is calculated:
Sum the repair time of all failures in the period and divide by the number of failures.
Example: repair times of 4h, 2h, and 6h → MTTR = (4 + 2 + 6) ÷ 3 = 4 hours.
Overlaps between repairs are not removed, as each failure is counted separately.
Calculation in grouped assets: Follows the logic of averaging the values of the direct assets.
MTTA – Mean Time to Action
MTTA indicates how long it takes, on average, to start executing a work order after its creation.
How it is calculated:
Created by request: time between the creation of the request and the start of the work order (or conclusion, if never started).
Created directly: time between the creation of the work order and the start (or conclusion, if never started).
Example: Work order created on day 1 and started on day 3 → MTTA = 2 days.
Calculation in grouped assets: Average of the MTTAs of the direct assets below.
Available vs. Unavailable Assets Chart
This chart shows which assets had any period of unavailability in the filtered interval.
If an asset appears as “Unavailable,” it means that there was at least one recorded stop, not that it is currently stopped.
Important Notes
The calculation of all indicators respects the filtered period.
If the asset was created after the start of the period, the calculation starts on the creation date.
Only work orders with the “Include in indicators” option enabled are considered.
Changing filters in the reports updates the values immediately.