Fuel
Diesel is issued on paper, reconciled monthly, and the variance is written off.
Every receipt, restock and refuel is bound to equipment, operator and work order, so the balance closes daily instead of quarterly.
Per shiftvariance visibility
Mining operations platform11 modules
Run the entire mine on one operational record
Production, drill & blast, plant, processing, fuel, logistics, people and sales — captured at the face, reconciled automatically, and reported before the shift ends.
- Deploys module by module
- No spreadsheet handoffs
- Role-based access throughout
app.terrasakti.com/dashboard
Operations overviewOperationsSite overview
LiveOre moved · today
48,210 t
+6.4%
Fleet utilisation
91.4%
+2.1 pts
Fuel variance
0.42%
in band
Crusher uptime
97.8%
+1.2 pts
Production vs plan · 12 weeks
3.42 stripping ratio · on plan
ActualPlan
Attention required
5- HD-1148 tire wear 82%Plant · position 4
- Fuel issue without work orderFuel · bay 2 · 14:20
- Blast BL-2291 recovery −4%Drill & blast · Pit B
- Stock below reorder: filtersLogistics · WH-01
- Shift 2 attendance reconciledPeople · 642 records
Shift progress · today
3 crews| Crew AlphaPit A · Bench 940 | 14,120 t | |
| Crew BravoPit A · Bench 925 | 12,480 t | |
| Crew DeltaPit B · Bench 880 | 9,940 t |
Fuel issued · last 14 days
428,600 L100% work-order matched
Instrumented across the full mining value chain
Open pitDrill & blastHaul fleetCrushing plantProcessingFuel logisticsWorkshopWarehouseCamp & rosterMaterial sales
Why sites consolidate
One record, or four versions of the truth
Most mines already have the data. What they don't have is one place where production, maintenance, finance and HR are looking at the same row.
11
Integrated modules
Production, drill & blast, engineering, plant, processing, fuel, logistics, HR, sales, analytics and admin — one schema, one login.
Shift
Reporting granularity
Every tonne, litre, hour and work order is captured against a shift, a crew and a piece of equipment.
Zero
CSV handoffs
Operations, maintenance, finance and HR read the same records. No exports, no reconciliation meetings.
24/7
Live operating picture
Dashboards stream from the same tables your crews write to, so leadership sees the pit as it is right now.
Figures describe the platform, not a customer average — every one is verifiable inside a demo tenant.
The platform
Three hubs, one underlying record
Terrasakti is organised the way a mine is actually run — the pit, the plant, and the business behind them. Each hub is a full workspace, and they all read from the same tables.
Production hub
Know your real tonnage before the shift handover
Ore and overburden, stripping ratio, blast recovery and fleet productivity reconcile against the plan continuously — not in a monthly review deck.
- Plan versus actual, liveMonthly production plans sit next to actual movement so variance surfaces the day it appears.
- Blast-to-tonne traceabilityDrilling records, blast work orders, recovery and fragmentation all tie back to the same block.
- Weather in the same viewRainfall and site conditions annotate the production curve, so lost hours have a cause attached.
app.terrasakti.com/production
Pit & ProductionProduction / Daily reconciliation
Ore moved
18,420 t
+4.1% vs plan
Overburden
62,970 bcm
−1.8% vs plan
Stripping ratio
3.42
on plan
| Pit A — Bench 940Shift 1 · Crew Alpha | 6,210 t |
| Pit A — Bench 925Shift 1 · Crew Bravo | 4,980 t |
| Pit B — Bench 880Shift 2 · Crew Delta | 3,120 t |
| Pit C — Haul roadShift 2 · rain delay 90m | 1,845 t |
Reconciled 2 minutes agoView full report
Modules
Eleven workspaces that already know about each other
Every module ships with its own reporting, its own permissions and its own capture forms — and none of them keep a private copy of your data.
How it works
From the bench to the boardroom, without the gaps
The loop that used to take a month — capture, reconcile, analyse, act — closes inside a single shift.
- 01
Capture at the face
Plans, work orders, attendance, refueling and inspections are recorded where the work happens.
Shift records - 02
Reconcile automatically
Production, engineering, plant and fuel data are cross-validated against work orders, equipment and shifts.
Matched ledger - 03
Analyse continuously
Cost, revenue, throughput and risk surface as live KPIs and forecasts instead of month-end findings.
Live KPIs - 04
Act the same shift
Alerts route to the crew that owns the asset, so decisions move from boardroom to bench in minutes.
Routed actions
Advanced analytics
Operational history that finally works for you
Every transaction the mine generates lands in one analytics layer — ready for forecasting, anomaly detection and decision support. No exports, no shadow spreadsheets, no waiting for month-end close.
app.terrasakti.com/analytics/forecasts
ForecastsProduction forecast · next 6 months
1.82 Mt P50 · ±4.1% band
Anomalies flagged
3
fuel · 2, stock · 1
Forecast accuracy
94.2%
trailing 90 days
Risk score
Low
weather-adjusted
Throughput by crushing line · last 14 shifts
Performance metrics
OEE, MTBF, MTTR and shift productivity computed on live operational records.
Operational insight
Cross-module correlations that show where the bottleneck actually lives.
Production forecasts
Forecast tonnage and stripping ratio with confidence bands and scenario toggles.
Maintenance analytics
Predictive signals drawn from equipment health and inspection history.
Fraud detection
Catch fuel siphoning, payroll anomalies and inventory shrink while they are small.
Inventory intelligence
Reorder timing tied to real consumption and supplier lead-time risk.
Where it earns its keep
The leakage is never in the reports. It's in the handoffs.
Six places where a mine loses money quietly, and what closing the handoff actually looks like.
Maintenance
A planned service stalls because the part was never actually in the warehouse.
Maintenance plans read live inventory and open purchase orders, so an unbuyable work order is caught at scheduling.
At plan timeparts confirmed
Drill & blast
Blast performance is judged on feel, and poor fragmentation quietly taxes the crusher.
Design, hole records, recovery and fragmentation distribution are scored against the plan for every blast.
Every blastscored against design
Commercial
Sold tonnage and produced tonnage live in different spreadsheets and never quite agree.
Sales records reconcile against production and processing tonnage inside the same system before reporting.
One ledgerops to invoice
People
Attendance is re-keyed from site sheets into payroll, and errors only surface on payday.
Roster, attendance, pay rates and payroll are a single chain with validation at each step.
No re-keyingsite to payslip
Reporting
The monthly pack takes a week to assemble and is out of date the day it lands.
Reports are views over live records, so the pack is a permalink rather than a rebuild.
Always currentno rebuild cycle
Getting there
A rollout that survives contact with a live site
No twelve-month big-bang migration. Each phase leaves the operation better off on its own, and nothing goes live until the crews can run it.
Foundation
Map the operation
We model your pits, benches, equipment register, crews and cost centres so the system speaks your site’s language on day one.
- Asset & site register
- Role matrix
- Cost centre mapping
First value
Go live on the first module
Usually production or fuel — the surfaces where variance is largest and the payback is easiest to see.
- Shift capture live
- Daily reconciliation
- Supervisor training
Integration
Connect the chain
Plant, logistics, HR and sales come online against the register you already trust, closing each handoff in turn.
- Maintenance & stock linked
- Payroll chain
- Sales reconciliation
Intelligence
Turn on the analytics layer
With clean operational history in place, forecasting, anomaly detection and risk scoring have something real to work with.
- Forecasts
- Anomaly alerts
- Executive reporting
Built around the mine cycle
Not a generic ERP with a mining skin. The data model starts at the block, the shift and the work order.
Rolls out module by module
Start with the module that hurts most. Each one is useful alone and compounds as the next goes live.
Designed for site crews
Forms that a supervisor can finish on a tablet at end of shift, without training in accounting.
Fits your existing stack
Exports, APIs and structured data so finance, fleet telemetry and BI keep the tools they already use.
Built to be trusted
Security and governance in the foundation, not the roadmap
A mine site can't afford guesswork about who changed what. Terrasakti is engineered with the controls finance, safety and IT expect from production software.
Access control by design
Role-based permissions are enforced per module and per action, with every mutation validated before it lands.
Fraud and risk aware
Built-in anomaly detection watches fuel, payroll and inventory for the patterns that precede real losses.
Auditable by default
Records carry who entered them, when, and against which shift — so a number can always be traced to its source.
- Role-based access control
- Validated inputs end to end
- Audit trail on records
- Encrypted in transit
- Environment isolation
- Least-privilege service accounts
What's new
Shipped recently
The platform moves every month. Here's what has landed across the modules.
- v2.7Jul 2026New
Logistics promoted to a top-level section
Inventory, purchase requisitions, purchase orders and goods receipt notes now sit together as one warehouse backbone.
- v2.6Apr 2026New
Fragmentation analytics for blasting
Score every blast against its design with image-based fragmentation distribution and recovery deltas.
- v2.5Mar 2026Improved
Crusher flow & energy overlays
Throughput, downtime and energy consumption now plot on a single timeline for the crushing line.
- v2.4Feb 2026New
Equipment-level fuel reconciliation
Tie every refuel to a work order, equipment and operator, and detect variance against plan as it happens.
- v2.3Jan 2026New
Camp & meal management
Plans, assignments, daily records and meal types — purpose-built for remote site logistics.
- v2.2Dec 2025Improved
Forecasts with confidence intervals
Production forecasting now exposes confidence bands and scenario toggles in the analytics workspace.
Questions we always get
The things a GM asks in the first ten minutes
Do we have to adopt every module at once?
No. Each module stands on its own and shares the same asset, site and people registers. Most operations start with production or fuel, then extend along the chain as the value becomes obvious internally.
How does this differ from the ERP we already run?
An ERP is built around ledgers and documents. Terrasakti is built around the mine cycle — blocks, benches, shifts, equipment and work orders — and reconciles into commercial reporting from there. The two coexist: operational truth here, statutory accounting where it already lives.
Will supervisors actually use it at end of shift?
That is the design constraint. Capture forms are short, validated, and scoped to what a supervisor already knows. If a field cannot be filled from the bench, it does not belong on the shift form.
What about connectivity at remote sites?
The platform is built for intermittent links: capture is lightweight, payloads are small, and reporting is read-optimised so a thin satellite connection is enough for the pit to stay in sync with head office.
Who can see what?
Access is role-based per module and per action. A crew supervisor, a maintenance planner, a payroll officer and a general manager each see a different system built from the same records.
Can we get our data out?
Always. Structured exports and API access are part of the platform, not a paid add-on. Your operational history stays yours.
Book a walkthrough
See Terrasakti running on your own numbers
Tell us about your site and we'll build the walkthrough around it — the modules you care about, on data that looks like yours.
What the session covers
- A 30-minute walkthrough of the modules that matter to your operation
- A worked example on a sample of your real production, fuel or payroll data
- A phased rollout plan with integrations and sequencing
- A direct line to the team that builds the platform — not a call centre
Ready when you are
Bring the whole operation into one view
Start with the module that hurts most and grow along the chain. We'll show you what the first ninety days look like on your site.
No procurement cycle required to see it working