Diesel is issued on paper and reconciled once a month. Any shortfall is written off.
Every delivery, restock and refuel is tied to a machine, an operator and a work order. The fuel balance closes daily.
Crews log the work on site. Terrasakti checks each entry as it's made, so the shift report is ready at handover.
Ore Moved · Today
48,210 t
Fleet Utilisation
91.4%
Fuel Variance
0.42%
Crusher Uptime
97.8%
Production vs Plan · 12 Weeks
3.42 stripping ratio · on plan
Attention Required
5Shift 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
From the Pit to the Sales Invoice
Production, maintenance, finance and HR each keep their own copy, and the copies rarely agree. Terrasakti keeps one.
All Sites
Side by Side
Coal, nickel, gold, tin and quarries run in one system. Each site keeps its own units, and tonnes of different commodities are never added together.
Shift
Level of Every Record
Every tonne, litre and work order is tied to a shift, a crew and a machine. A shortfall points to where it happened.
One
Version of the Figures
The site, the GM and the owner read the same numbers. Nothing to pass around, nothing to reconcile by hand.
Live
Shift Reporting
Dashboards read what crews enter. The shift report is ready at handover, not at month end.
These describe how the product works, not customer results. Check each one in a demo account.
Four workspaces cover the pit, the plant, the business and the licences. Each works alone. All four read the same records.
Ore, overburden and stripping ratio are tracked against plan all day. A shortfall shows on the shift it happens, not at the monthly review.
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 |
Each module has its own forms, reports and permissions, and none keeps a separate copy of your data. Start with one. Add the rest in any order.
A decision used to wait a month for the data. With every team on the same records, it takes a shift.
Supervisors, fuelmen and planners enter the work on site. The people who did it are the ones who log it.
Shift RecordsEach entry is checked against its work order, machine and shift. Mistakes are caught when they're made, not at month end.
Checked RecordsOutput, cost and throughput update as records arrive. The shift report is ready at handover.
Shift ReportKPI alerts reach the person responsible, so the problem is handled on the same shift.
KPI AlertsEvery entry from site sits in one place, so forecasts and variance checks run on live records. No exports to clean, no side spreadsheets to keep.
Month-End Forecast · Ore Moved
412,600 t plan 405,000 t
Variances to Review
3
fuel · 2, stock · 1
Forecast vs Plan
+1.9%
month end
Fuel Variance
0.42%
in band
Throughput by Crushing Line · Last 14 Shifts
Worked out from the work orders and downtime your planners already record.
Production projected to month end and compared with plan.
See where measured fuel, deliveries, stock counts and surveys differ from the records, and by how much.
Tyre wear, equipment health and inspection history in one view.
Scheduled PDF and Excel packs, emailed to owners and managers.
Set a threshold on a KPI and the right person is told when it's crossed.
Eight places mines lose money without noticing, and how Terrasakti closes each gap.
Diesel is issued on paper and reconciled once a month. Any shortfall is written off.
Every delivery, restock and refuel is tied to a machine, an operator and a work order. The fuel balance closes daily.
A planned service stalls because the part was never in the warehouse.
Maintenance plans read current stock and open purchase orders, so a missing part is flagged when the job is scheduled.
Blasts are judged by eye, and poor fragmentation quietly slows the excavators and the crusher.
Each blast is measured against its design, with hole records, recovery and fragmentation kept together.
Sold tonnes and produced tonnes live in different spreadsheets and never quite agree.
Sales are checked against production and processing tonnes before anything is reported.
A barge is priced in a spreadsheet from the index, the survey and the CoA, and the royalty is worked out again somewhere else.
The shipment carries its draft survey, CoA and price formula. Price, exchange rate and royalty are worked out together and fixed on approval.
A group runs a coal pit and a quarry, and their tonnes get added into one meaningless number.
Each licence is a site with its own commodity and units. Head office sees them side by side; a site login sees only its own.
Attendance is copied by hand from site sheets into payroll, and the errors show up on payday.
Rosters, attendance, pay rates and payroll are linked, and each step is checked before the next begins.
The monthly report pack takes a week to build and is stale when it lands.
Reports read straight from current records, and packs are emailed on a schedule as PDF and Excel.
No twelve-month migration. Each phase pays off on its own, and nothing goes live until the crews are ready.
Foundation
We set up your sites first: each licence and what it mines, pits and benches, the equipment register, crews and departments. From day one, every screen uses your own names and units.
First Module
Usually production or fuel, where losses are largest and the gain is easiest to see.
Integration
Plant, logistics, HR and sales join one at a time on the same register, covering each handover in turn.
Analytics
With a reliable operating history, forecasts and variance checks have real data to work with.
Not a general ERP adapted for mining. Records start with the licence, the block, the shift and the work order.
Start where the loss is largest. Each module works alone and is worth more as others go live.
A supervisor can finish the shift forms on a tablet. No accounting training needed.
Exports let your finance and reporting teams keep the tools they already use.
Access is set by role, each company's data is kept apart, and every record shows who entered it and when.
Permissions are set per module and per action, and a login can be limited to some sites. Approval is its own permission, so nobody signs off their own work.
Measured fuel, deliveries, stock counts and surveys are compared with the records, and the worst gaps come first.
Each record shows who entered it, when, and for which shift. Any figure traces back to its source.
Terrasakti ships often. Here is what changed lately.
Each licence is a site with its own commodity, method and units. Switch between sites, limit logins by site, and tell setup what each site mines.
RKAB against actual, reclamation and guarantees, environmental readings against limits, incidents with LTIFR and TRIFR, and a compliance report pack.
Weighbridge tickets and gradation for quarries, development and ventilation for underground, dredge and concentrate logs for alluvial tin, and wash plant runs that move the stock ledger.
Barges and vessels as one lot, with draft survey, CoA, HBA or HPM price formulas, royalty, and an approval that fixes the exchange rate.
See where measured fuel, deliveries, stock counts and surveys differ from the records, and by how much, with the worst records one click away.
Grinding, flotation, thickener, filter press and tailings logs for the processing plant, and customer deposits with the sales paid from them.
Inventory, purchase requisitions, purchase orders and goods receipt notes now sit together in one place.
Camp plans, room assignments, daily records and meal types, built for remote sites.
Compare each blast with its design, with fragmentation analysis beside the recovery figures.
Straight answers on cost, rollout, connectivity and data.
We quote per site after a walkthrough, based on the modules you start with. Add others later. Data exports are included.
No. Each module works alone and shares the same equipment, site and staff records. Most sites start with production or fuel and add more once the first has proved itself.
Coal, nickel, bauxite, manganese, gold mining, alluvial tin and quarries, across open pit, underground, alluvial and quarry sites, plus washing plants. Smelters and gold leaching plants are not covered. Choose what a site mines at setup and its units, moisture basis and grade attributes follow.
Yes. Each licence is a site with its own commodity and units. Head office sees every site side by side, tonnes of different commodities are never added together, and a login can be limited to the sites that person works on.
Yes. Each licence's RKAB is compared with actual production and sales month by month. Reclamation, guarantees, environmental monitoring and incidents sit on the same licence, and the compliance pack is built from them.
It depends on the first module and how ready your site data is. We set up pits, equipment and crews first, then one module goes live, usually production or fuel. The walkthrough shows what the first 90 days would look like at your site.
Yes. Forms are light, so a basic satellite link keeps site and head office in step. Refuel sheets entered offline stay on the device and send when the link returns.
No, it works beside it. An ERP is built around accounts; Terrasakti is built around blocks, shifts, equipment and work orders. Operations live in Terrasakti, statutory accounting stays in your ERP, and exports move figures between them.
You do. Export it any time. Each company's data is kept separate from every other company's.
Access is set by role, per module and per action. A supervisor, a planner, a payroll officer and a GM each see what their role needs, all from the same records.
That's what it was designed for. Shift forms are short, check entries as they're made, and ask only what a supervisor already knows. If a field can't be filled from the bench, it doesn't belong on the form.
Training is part of rollout. We train supervisors on each module before it goes live, and nothing goes live until the crews are ready.
Bahasa Indonesia and English. The team is based in Indonesia, so you can talk to us in your site's language.
Tell us about your site. We'll build the walkthrough around the modules you care about, using data that looks like yours.
Pick the module for your biggest problem and add the rest at your own pace. The walkthrough shows what your first 90 days would look like.
See It Working Before You Sign Anything