Use this predictive maintenance cycle time calculator to turn routine predictive maintenance records into a clear operating measure. Enter the time, workload, and performance values from one consistent period. The result includes the headline metric plus supporting figures that make bottlenecks, capacity gaps, or avoidable losses easier to discuss before changing staffing or schedules.
The headline result summarizes predictive maintenance cycle for the values entered. Read it alongside the supporting measures, because a change in workload, staffing, delay, or quality can move the result for very different reasons.
This is an operational estimate. Keep definitions and time boundaries consistent when comparing teams, assets, or periods.
With 240 hands-on minutes, 90 waiting minutes, 6 completed events, and 2 technicians, elapsed cycle time is 35 minutes per job, labor content is 40 labor-minutes per job, and delays are 27.27% of adjusted elapsed time.
Use one consistent shift, day, week, or planning window. Do not mix output from one period with time or staffing from another.
Yes where the field allows zero. The calculator will show a zero-rate result without displaying undefined or infinite values.
Use net available or planned time as described by each field. Record unplanned stops separately when the calculator requests downtime.
Enter the average number actively available during the measured period. If staffing changes materially, calculate each segment separately.
Dashboards may use different time boundaries, exclusions, rounding, or definitions. Match those rules before comparing the numbers.
| Input | How it is used |
|---|---|
| Hands-on minutes | Use a verified value from the same measurement period. |
| Waiting minutes | Use a verified value from the same measurement period. |
| Completed jobs | Use a verified value from the same measurement period. |
| Technicians | Use a verified value from the same measurement period. |