Categories
Mining Guides

Mining sites run around the clock and the work is electrical. Why fatigue is an operations risk rather than a wellness topic, and what a real program controls.

Every operator can tell you their shift pattern. Far fewer can tell you how many hours the technician who answered last night’s breaker trip had already been awake. Those are different questions, and only the first one usually has an owner.

Our guides to staffing a mining operation and to facility staffing roles and workforce planning cover how to build the roster: which roles you need, how to rotate them, what to pay for on-call. This is about what happens to people once they are on that roster, and why it belongs in the operations column rather than the human-resources one.

Mining is a bad combination of conditions

Plenty of industries run continuously. Mining stacks several fatigue drivers at once, which is what makes it worth treating deliberately.

The load never drops, so there is no quiet part of the night when nothing needs attention. The environment itself is tiring: sustained noise loud enough to require protection, heat on the hot aisle, and in a container, cramped working space. Sites are frequently remote, which means either a long commute at the ends of a shift or living on site, and our note on crew facilities at remote sites covers why the quality of that accommodation is an operational variable rather than a courtesy.

Then there is the call-out. A site that trips at three in the morning does not wait for the day shift, and the person who responds is usually the person who already worked that day. That is the structural problem: the moments of highest consequence and the moments of highest fatigue are the same moments.

What fatigue actually degrades

The useful framing is not that tired people make mistakes. It is that tiredness attacks exactly the three capabilities a mining site depends on.

Vigilance for rare events. Most of what a fleet does is run correctly. The job is noticing the exception: the one unit behaving differently, the reading that drifted, the smell that is new. Sustained attention to a mostly-uneventful signal is the first thing to go, and it goes before anyone feels impaired.

Decision quality under time pressure. An outage is a sequence of judgments made quickly with incomplete information, which is precisely the condition in which a tired operator reverts to the most familiar action rather than the correct one. Our guide to outage response and postmortems describes the process; fatigue is what determines whether the process is actually followed when it matters.

Procedural discipline. This is the dangerous one. Safe electrical work is procedural by design, and procedures are what get shortened when someone wants to be finished. Lockout and tagout is a sequence of steps that each feel skippable individually. The arc-flash boundary exists because the consequence of being wrong about energized equipment is not a bad shift. A fatigued person does not decide to work unsafely. They stop noticing that they are.

A program is a set of rules, not a message

Fatigue management goes wrong when it becomes encouragement. Telling people to rest well is not a control, because it places the whole burden on the individual and gives the operation nothing to enforce or audit. A real program is made of rules that can be checked.

  • A ceiling on continuous hours, written down. Not a guideline. A number the site commits to, with a named person who can authorize an exception and a record when they do. The specific figure depends on your jurisdiction, your insurer and the nature of the work, which is exactly why it has to be decided deliberately rather than inherited by accident.
  • A harder rule for energized work. The threshold at which someone may no longer open a panel should be lower than the threshold at which they may no longer be on site. Separating those two is the single most useful rule in the set, because it lets a tired technician still be useful for monitoring and escalation without putting them in front of live equipment.
  • Rest after a call-out, not just before a shift. If answering a two-in-the-morning alarm does not change what time the same person is expected back, the rota is only nominally a rota. This usually requires deciding in advance who covers the following morning, because nobody will arrange it at the time.
  • Journey management. At a remote site the drive is part of the shift. The last hour of a long shift followed by an hour on a rural road at night is the highest-risk part of many mining jobs, and it is almost never counted as work.
  • Somewhere to actually stop. Relief has to be physically possible. A site with no quiet space out of the noise means a break is a worse version of working.

Self-reporting only works if it is safe

You will never measure fitness for duty from the outside with any accuracy. The only reliable source is the person themselves, and they will tell you honestly only if saying so costs them nothing.

That means a technician declining to perform energized work because they have been awake too long must be treated as the system working, recorded as such, and never framed as unreliability. The first time someone is made to feel difficult for it, the information stops arriving and you are back to guessing. This is the same cultural mechanic that makes incident reporting work, and our guide to running a safety program covers how that gets built and how quickly it can be destroyed.

It also means the rule has to bind upward. If the person most likely to work through the night is the owner or the site manager, a policy that applies only to employees is decoration.

Measure hours worked, not hours scheduled

Most sites can produce a roster and cannot produce the thing that matters, which is what actually happened. A few figures are worth tracking, and none of them require new systems.

  • Actual hours per person per week, including call-outs and travel, rather than rostered hours.
  • Call-out distribution. Not the total, but how it is spread. One name against most of the alarms is a fatigue concentration, and it is usually the most capable person on the team.
  • Consecutive call-outs by the same individual. Two nights in a row is a different situation from two nights in a month.
  • Time from alarm to a person on site, read alongside the above. A number that is improving because one person keeps answering is not an improvement.

The pattern that should prompt action is concentration rather than volume. Fatigue problems at small sites are almost always about a single indispensable person absorbing the irregular work.

The small-site problem, honestly

All of this is straightforward at a site with enough people and dishonest to present as easy at a site with three. When the team is small, every rest rule has the same cost: for someone to be off, nobody is covering.

There is no arrangement that makes that disappear. What it does is turn a hidden risk into a visible decision, and there are only a few real answers. Carry enough people to absorb the irregular work. Accept a slower response at night and say so in writing, including to anyone whose machines you host. Share cover with another operator nearby. Or move the irregular work to somebody whose business is staffing it.

Pretending the roster is adequate is the one option that keeps the exposure and gives you nothing for it. Fatigue is a cost that is already being paid; the only question is whether it is being paid deliberately.

The spike nobody plans for

Fatigue at a running site is a steady-state problem and reasonably easy to see. The sharper risk is the deployment, and it is the one most often left out of the roster entirely.

When a batch of machines arrives, the same small crew receives freight, racks hardware, pulls circuits, terminates connections and brings units up, usually against a date that was set before anyone knew what the site would actually require. Days run long by consent, because everyone wants it finished and the work feels finite.

That period has two properties worth noticing together. It is when the crew is most tired, and it is when nearly all of the energized electrical work of the entire year happens. Terminations, panel work, and commissioning and load-bank testing are concentrated into exactly the window where hours are longest and the pressure to be done is highest.

The practical control is to treat the deployment as its own staffing problem rather than an intense version of normal operations. That generally means bringing in additional hands for the duration, sequencing the energized work into the early part of a shift rather than the end, and accepting that a commissioning schedule which only works if nobody rests is not a schedule. A deployment that runs a few days longer costs less than an arc-flash incident or a termination that has to be found later.

If you are hosting, it is your host’s practice that matters

For anyone whose machines sit in someone else’s building, this is not an abstraction. Response time at night, the quality of decisions made during an outage, and whether the switchgear maintenance gets done properly rather than quickly all depend on a crew you never meet.

It is a reasonable thing to ask about, and the answer is informative. How many people are on site overnight. Who responds to an alarm at three in the morning, and what they were doing twelve hours earlier. Whether there is a written limit on hours, and who can authorize an exception to it. A facility that can answer plainly has thought about it. One that answers that the team is dedicated and works whatever hours are needed has told you something too.

If you are weighing where to place a fleet and want to know how a site is actually staffed overnight rather than how it is described, get in touch. It is a more useful conversation before the machines ship than after an outage.

Explore Rax Mining

Categories