What Is Mining Scheduling Software?

Mining scheduling software is a system for planning and sequencing mining work against time, resources and constraints. Depending on the layer, that work may be tonnes to be moved, equipment to be maintained, shutdown tasks to be executed, or crews to be allocated to shifts and jobs. What makes it 'mining' rather than generic scheduling is the constraints it has to respect: roster and fatigue rules, worker competencies and site access, equipment availability, permits and isolations, and client shutdown windows that cannot move.

This is the most common confusion. Mine planning and production scheduling tools such as Deswik, Vulcan and XPAC answer 'what material do we move, in what sequence, over the coming years'. They are engineering tools used by the mine operator. Operational or crew scheduling answers 'who is on shift tomorrow, on which job, with what plant, and are their tickets current'. Contractors and service providers almost always need the second, and are sometimes sold the first by mistake.

It builds shift and roster schedules that reflect reality: crew availability across FIFO swings, competency and licence currency, equipment allocation, job and client priorities, and travel or camp logistics. Good systems flag conflicts before they are published — a worker rostered while their high-risk work licence expires, two crews assigned the same excavator, a shift that breaches a fatigue rule, or a job with no supervisor allocated. Once published, the schedule becomes the basis for pre-starts, timesheets and job costing rather than a separate spreadsheet.

A mining schedule is a compliance artefact as much as a plan. It has to respect competency and licence currency, medicals and site inductions, fatigue and hours-of-work limits, permit and isolation requirements, and supervision ratios. In Australia that sits under model Work Health and Safety laws plus jurisdictional mining regulation — for example the WHS (Mines) Regulations in Western Australia and Queensland's mining safety and health legislation. Scheduling software that cannot see competency expiry dates will happily produce a non-compliant roster. Confirm your specific obligations with your WHS advisor or regulator.

Maintenance scheduling is usually driven by a CMMS or ERP module that generates preventive work orders from meter readings and time intervals. Shutdowns are different again: a compressed, high-risk window where hundreds of tasks compete for the same permits, cranes, scaffolds and trades. Shutdown scheduling therefore emphasises critical path, resource levelling, permit sequencing and daily re-planning. Contractors delivering shutdown scope need their crew schedule to stay synchronised with the client's task schedule, which is where most of the friction occurs.

A schedule that only exists in a browser tab in the head office is not a schedule the crew can use. On remote sites across the Pilbara, Goldfields, Bowen Basin and NT, coverage is intermittent, so supervisors need today's crew and job list available offline on a phone or tablet, with changes and completions syncing when signal returns. This is the practical dividing line between software that gets adopted and software that gets printed out and taped to a donga wall.

Scheduling is a financial control, not just an administrative one. The schedule determines committed labour cost before a single hour is worked, and it is where over-allocation, unnecessary overtime and idle travel days originate. When the schedule, timesheets and job costing share the same data, a supervisor can see planned versus actual hours per job during the job. When they are separate, variance is only discovered at month-end, by which point the work is done and the invoice is already contested.

The common symptoms are consistent: the published roster and the actual crew differ by the second day; competency expiries are discovered at the gate; equipment is double-booked between crews; overtime appears in the pay run that nobody approved; and changes are communicated by group chat with no record of who was told what. Any two of these together usually mean the constraint volume has outgrown manual scheduling — typically somewhere between 20 and 50 field workers or three concurrent jobs.

Pick the layer first, then the product. For operational and crew scheduling, evaluate: competency-aware allocation that blocks or warns on expiries; equipment and plant allocation alongside people; fatigue and roster rule checking; offline access for supervisors; the ability for the schedule to generate pre-starts and timesheets; integration with payroll and accounting; and how quickly you can change the configuration yourself. Test with a real multi-crew week on your worst-signal site rather than a demo dataset.

SprintSuite operates at the operational and crew scheduling layer, built for Australian mining, civil, maintenance and field service contractors. It links rosters and shift allocation to competencies, plant, pre-starts, timesheets and job costs, with offline access for supervisors on remote sites. It is not a mine planning or geological sequencing tool — if you need pit design and reserve scheduling, an engineering platform such as Deswik or Vulcan is the right category, and the two layers work alongside each other.