Skip to content
MAX4METS

Downtime and delay accounting

Record planned and unplanned delays against equipment and shifts, then report availability, utilisation and where the lost hours went.

Lost hours are lost production. Knowing that the mill ran for 21 hours yesterday is useful; knowing that two of the missing hours were a planned liner inspection and one was a feed conveyor trip is what lets a plant do something about it. MAX records downtime in enough detail to answer that question, and reports it in the same system as the production it affected.

Plant states instead of free text

Each piece of equipment in the plant model moves between plant states: running, waiting on feed, mechanical breakdown, electrical fault, planned maintenance, standby and so on. States are grouped into categories that suit your site, for example by discipline (mechanical, electrical, operational, external) or by type of loss (breakdown, delay, planned downtime, standby). Because every stoppage is recorded against a defined state rather than a free-text note, delays can be counted, summed and compared.

Each state belongs to one of five time usage classes: operating time, operating delay, operating standby, planned downtime and breakdown downtime. That classification is what turns a log of events into availability and utilisation.

MAX client sites typically model from fifty to two hundred items of plant, with a handful of state categories and anything from a dozen to several hundred states.

Workflows that keep the log consistent

A plant state workflow defines which state a piece of equipment starts in and which changes are allowed from each state, with some states, such as a site-wide power outage, reachable from anywhere. Workflows are assigned by type of equipment, so a crusher, a SAG mill and a haul truck can each follow their own rules. The result is a delay log that makes sense: a mill cannot go from “breakdown” to “running” without passing through the states your site requires.

Each change records the equipment, the new state, the period or shift, the duration and comments, along with who entered it. A quick-add action keeps recording a stoppage to a few clicks.

Importing delay logs

Where a site already logs stoppages in a control system or a spreadsheet, MAX imports those logs with a saved mapping of columns, aliases that translate another system’s equipment and state names into yours, filters, and a minimum duration below which short events are ignored. Where data is missing for part of a period, estimation rules can fill the gap for a given time usage class rather than leaving the hours unaccounted for.

Availability and utilisation

For any period, MAX calculates calendar, operating, delay, standby, planned and breakdown hours, and from them availability and utilisation percentages. Operating time can be measured from the states recorded or calculated, and the calculation can be limited to operating periods such as day shift only. Downtime can also be used in formulas through plant state duration measures, filtered by state, category or time usage class, so throughput and rate calculations account for the hours the plant was actually running.

Reports and dashboards

Period reports include plant state sections shown as tables or as stacked bar, pie, doughnut or waterfall charts, grouped by equipment, category and state with subtotals, in minutes, hours or days, with comments where needed. Every MAX client site reports downtime this way. Dashboards built on the same data let metallurgists and maintenance planners slice delays by equipment, cause and period, from a Pareto view of the biggest causes to downtime by area of the plant.

More MAX4METS features

Ready to elevate your metallurgical accounting?

Book a demonstration and see how MAX fits your plant, your data sources and your reporting cycle.