Crews record the work on site, from the bench to the workshop. Terrasakti checks every entry, so the shift report is ready before the next shift starts.
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
Most mines already collect the data they need. Production, maintenance, finance and HR each keep their own copy, and the copies rarely agree. Terrasakti keeps one copy for everyone.
11
Modules on one database
Pit, plant and office teams work in one system with one login. Nobody types the same figures twice.
Shift
Level of every record
Every tonne, litre, hour and work order is tied to a shift, a crew and a machine. A shortfall can be traced to where it happened.
One
Version of the figures
The site, the GM and the owner read the same numbers. There are no exports to pass around and nothing to reconcile by hand.
Live
Shift reporting
Dashboards read the records crews enter. The shift report is ready before the next shift starts, not at month end.
These figures describe the platform itself, not customer results. You can check each one in a demo account.
Three workspaces cover the pit, the plant and the business behind them. Each one works on its own. All three read the same records.
Ore, overburden and stripping ratio are compared with the plan through the day. A shortfall shows up 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. None of them keeps a separate copy of your data. Start with one and add the rest in any order.
Turning site data into a decision used to take a month. With every team on the same records, it happens within the shift.
Supervisors, fuelmen and planners enter the work on site. The people who did the work are the ones who record it.
Shift recordsEach entry is checked against its work order, machine and shift. Errors are caught when they are made, not at month end.
Checked recordsOutput, cost and throughput update as records come in. The shift report is ready before handover.
Shift reportKPI alerts reach the people responsible by email. The problem is dealt with on the same shift.
Assigned actionsEvery entry from site is kept in one place and is ready for forecasts and anomaly checks. There are no exports to clean and no side spreadsheets to keep.
Production 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
OEE, MTBF and MTTR calculated from live operating records.
Read across modules to find where the real bottleneck is.
Tonnage and stripping ratio forecasts with confidence bands and alternative scenarios.
Early warnings from equipment health and inspection history.
Spot fuel theft, payroll errors and stock losses while they are still small.
Reorder points set from actual use and supplier lead times.
These are six places where mines lose money without noticing. Each card shows how Terrasakti closes the gap.
Diesel is issued on paper and reconciled once a month. Any shortfall is written off.
Every delivery, restock and refuel is linked to a machine, an operator and a work order. The fuel balance can be closed every day.
A planned service stalls because the part was never in the warehouse.
Maintenance plans read current stock and open purchase orders. A missing part is flagged when the job is scheduled.
Blasts are judged by eye. Poor fragmentation quietly slows the excavators and the crusher.
Each blast is measured against its design. Hole records, recovery and fragmentation are kept together.
Sold tonnes and produced tonnes sit in different spreadsheets and never quite agree.
Sales are checked against production and processing tonnes in the same system before anything is reported.
Attendance is copied by hand from site sheets into payroll. The errors appear on payday.
Rosters, attendance, pay rates and payroll are linked. Each step is checked before the next one starts.
The monthly report pack takes a week to build and is out of date when it arrives.
Reports read straight from current records. Report packs are emailed on a schedule, in PDF and Excel.
There is no twelve-month migration. Each phase is useful on its own. Nothing goes live until the crews are ready to use it.
Foundation
We set up your site first. That means pits and benches, the equipment register, crews and cost centres. From day one, every screen uses your site’s own names.
First module
This is usually production or fuel. Losses there are largest, and the gain is easiest to see.
Integration
Plant, logistics, HR and sales join one at a time on the same register. Each handover between teams is covered in turn.
Analytics
Once you have a reliable operating history, forecasts and anomaly alerts have real data to work with.
Terrasakti is not a general ERP adapted for mining. Its records start with the block, the shift and the work order.
Start where the loss is largest. Each module works on its own and is worth more as others go live.
A supervisor can finish the shift forms on a tablet. No accounting training is needed.
Exports and an API let your finance, telemetry and reporting teams keep the tools they already use.
Terrasakti has the controls that finance, safety and IT teams expect from business software. Access is set by role, and each company’s data is kept apart.
Permissions are set per module and per action. Every entry is validated before it is saved.
Anomaly checks watch fuel, payroll and stock for the patterns that come before real losses.
Each record shows who entered it, when, and for which shift. Any figure can be traced to its source.
The platform is under active development. These are the latest changes.
Inventory, purchase requisitions, purchase orders and goods receipt notes now sit together in one place.
Compare each blast with its design. Image-based fragmentation analysis sits beside the recovery figures.
Throughput, downtime and energy use for the crushing line now share a single timeline.
Every refuel is linked to a work order, a machine and an operator. Differences from plan show as they happen.
Camp plans, room assignments, daily records and meal types, built for remote sites.
Production forecasts in the analytics workspace now show confidence bands and alternative scenarios.
Straight answers on cost, rollout, connectivity and data.
We quote each site after a walkthrough. The quote is based on the modules you start with, and you can add others later. Data exports and API access are included at no extra cost.
No. Each module works on its own and shares the same equipment, site and staff records. Most operations start with production or fuel. They add other modules once the first one has proved its value.
It depends on the first module and on how ready your site data is. We set up your pits, equipment register and crews first. Then one module goes live, usually production or fuel. In the walkthrough we show you what the first 90 days would look like at your site.
Yes. Forms are light and send little data, so a basic satellite link is enough to keep site and head office in step. Refuel sheets entered while the link is down stay on the device. They are sent when the connection returns.
No. It works beside your ERP. An ERP is built around accounts. Terrasakti is built around the mine, with its blocks, shifts, equipment and work orders. Operational data lives in Terrasakti and statutory accounting stays in your ERP. Exports and the API move figures between the two.
You do. You can export it at any time, and API access is included at no extra cost. Each company’s data is kept separate from every other company’s.
Access is set by role, for each module and each action. A crew supervisor, a maintenance planner, a payroll officer and a general manager each see only what their role needs. They all read from the same records.
It was designed for exactly that. Shift forms are short and check entries as they are made. They ask only for what a supervisor already knows. If a field cannot be filled in from the bench, it does not belong on the shift form.
Training is part of the rollout. We train supervisors on each module before it goes live. Nothing goes live until the crews are ready to use it.
Bahasa Indonesia and English. Our team is based in Indonesia, so you can talk to us in the language your site uses.
Tell us about your site. We will build the walkthrough around the modules you care about, using data that looks like yours.
Pick the module that solves your biggest problem. Add the rest at your own pace. In the walkthrough we show you what the first 90 days would look like at your site.
See it working before you sign anything