The Best Mining ERP Decisions Start with the People Doing the Work

Walk into almost any mine and, sooner or later, you'll hear someone say, "The system doesn't do that."

It's a comment we've heard countless times over the years, whether we're talking with maintenance, procurement, finance or operations. Sometimes it's said out of frustration. Sometimes it's followed by a spreadsheet that's become the "real" system. Other times, it's simply accepted as the way things are. But after spending time with the people actually doing the work, we've found that the conversation usually takes a different turn. The system often can do it. The real question is whether it still reflects the way the business operates today.

Mining operations don't stand still. Sites expand, new equipment is introduced, production targets change, people move into new roles, and processes evolve over time. What worked five or ten years ago doesn't always support the way the operation runs today, yet many businesses continue asking their ERP to support processes that have gradually changed without anyone stepping back to look at the bigger picture. That's why we believe the most valuable part of any ERP conversation has very little to do with software.

It starts by asking the people who use it every day. The maintenance planner knows where work orders slow down. The warehouse team knows why inventory counts don't always match. Procurement understands where approvals create delays, and finance can quickly point out where reporting takes more effort than it should. Individually, each team sees one part of the operation. Together, they tell the real story.

One of the things we enjoy most about working with mining companies is getting out onto site and following those stories. We'll trace a purchase order from the moment a need is identified through to receiving and payment. We'll sit with maintenance to understand how shutdown planning really works. We'll spend time with warehouse teams to see how materials move through the operation. Those conversations almost always uncover opportunities that would never appear in a project plan or software demonstration.

More often than not, the ERP isn't the problem. The process has simply evolved around it. Someone created a spreadsheet because it was quicker. A temporary workaround became standard practice. An approval step was added years ago and never questioned. None of those decisions were wrong at the time, but over the years they create layers of complexity that make even the best ERP system feel like it's holding the business back.

Technology is only as effective as the processes it supports. That's why the best ERP projects don't begin by asking, "What software should we buy?" They begin by asking, "How does work actually get done here?" At PSA, that's always been our approach. Before recommending technology, we take the time to understand the operation, because every mine is different, every team works differently, and every successful ERP project starts with understanding the people behind it.

The next time someone says, "The system doesn't do that," don't stop at the software. Ask why.