River sand-mining platform — turning one weighing pass into an immutable fact

An IoT management platform for river sand extraction and aggregate production: eight modules and 24 screens across pits, contracts, devices, vehicles, vessels, finance and administration, wired to four kinds of field equipment — weighbridge, barrier, cameras and vessel trackers. The question it answers is not “do we have a system” but whether three numbers agree: how much was taken, who bought it, and how much contract quota is left. De-identified presentation.

Industry
River sand extraction / aggregates · water authority
System type
Web admin backend + field IoT integration
Key technology
Weighbridge capture · plate and barrier control · geofencing & vessel tracking · quota deduction · audit trail
Jiding scope
Requirement shaping, process design, front and back end, device integration, launch support
8modules, from field device to financial statement
24screens covering people, trucks, vessels, contracts, devices and money
4equipment types: weighbridge, barrier, camera, vessel tracker
3ledgers reconciled: contract, weighbridge, finance
Devices in the river, ledger in the office: data flows up, permissions flow down Decision Business Ingest Sensing Operations dashboard pits · contracts · trucks · vessels · cameras · contract value + output trend Reports & filing by pit · contract · period Pits 4 screens Contracts 2 screens Devices 4 screens Trucks 1 screen Vessels 2 screens Finance 2 screens Video ingest NVR & cameras Weighing indicator readings Barrier control raise & snapshot Geofence vessel reporting Cameras zone, stockpile, gate Video recorder local storage & arming Weighbridge & barrier the physical checkpoint Vessel tracker position reporting Field equipment does two things: hand up a reading, raise a barrier. Every judgement and every entry happens in the business layer.
Four layers: sensing sees, ingest reads it correctly, business calculates, decision explains — device brands and models are isolated in the ingest layer, so hardware can be swapped without disturbing contract or finance logic

Three gaps: can't see it, can't count it, can't reconcile it

The industry is not short of rules; it is short of the traces rules leave behind. The working face is on the water, the office is kilometres away, and between them sit three breaks.

  • Nobody can see the site. A permit defines coordinates, extraction depth, permitted volume and a validity period. The work, however, happens afloat, and management depends on site visits and phone calls. Over-extraction, night shifts and extra vessels usually surface through a complaint or a surprise inspection — by which time the sand is ashore.
  • Nobody can count it. How many tonnes in a truck? The driver says a number, someone estimates, or a handwritten weigh slip goes into a drawer. Two loads from the same truck can differ by two tonnes, and at month end nobody can say which load carried the error.
  • Three books, none of them agree. The contract holds price, volume and value. The weighbridge holds entry and exit weights. Finance holds receipts and adjustments. Each is maintained separately; reconciliation takes three days, and everyone is certain they are right.
One decision shaped the rest of the system: the core of sand-mining management is not managing people, it is managing a single haul. People, vessels, contracts and finance are all derived from “this truck crossed the weighbridge once”. Get that right and every module has something to stand on; get it wrong and more reports only amplify the error.

Eight modules, one chain

The manual was written menu by menu, so it reads as eight parallel blocks. Follow the data instead and they share one key chain: pit → contract → truck / vessel → weighing record → finance. Remove one link and the far end stops adding up.

ModuleWhat is insideWho uses it
DashboardSix headline figures — pits, contracts, trucks, vessels, cameras, contract value — plus an output trend curveOwner and site manager: the first screen opened every morning
PitsPit register, vessel register, permits, geofence records — four screens covering where extraction happens, who may do it, and how farSite administrator: new pits, permits, fence maintenance
ContractsContract number, unit price, volume, contract value, amount paid; customer register; balance adjustment and reporting syncSales and finance: signing, quota checks, customer records
DevicesVideo recorders with arming, device exception records, pit weighbridges, pit barriersOperations: uptime, exceptions, arming state
TrucksPlate, home pit, rated load, status — filterable and maintained in bulkGate and weighing staff: an unknown plate should never raise the barrier
VesselsTrip records and position messages, searchable by vessel, pit and periodSite management: where is the dredger, how long has it been there
FinanceSand sale records (query and backfill), contract balance adjustment recordsFinance: one truck one entry, quota deducted line by line
AdministrationUsers, roles, departments, menus, IP allowlist, login history, audit log, exceptions — eight itemsSystem owner: accounts, and who changed which number

One deliberate split: the device module holds both the asset register and the exception log. The register answers “which pit does this weighbridge belong to, what model, which IP”; the exception log answers “it was offline for 47 minutes today”. One is an asset, the other is operations — merged, neither works well.

One weighing pass is one complete transaction

Six steps from gate to gate, each doing exactly one thing, each leaving a raw record that cannot be edited afterwards. This is the part of the system we refused to compromise on.

123 456 Truck in plate + snapshot Tare weight empty truck Loading at the face Gross weight loaded truck Net × rate on the server Release quota · photo checked against fleet unknown, no barrier read off the indicator no manual entry photo on file timestamp by system same scale, twice two readings subtracted rate from contract amount generated with it blocked if quota short override, with a record One weighing pass = one sale record = one quota deduction, committed in a single transaction and rolled back entirely if any step fails Net = gross − tare; amount = net × contract price. Both formulas live on the server, so the gate cannot change the tonnage or the price. Two photos per pass, entry and exit, are the evidence base: “which pit did this load come from” stops being an argument.
Weighing loop: only two of the six steps produce data; the other four exist to confirm and to leave a trace. Net weight and amount are computed server-side — the site submits readings and photos, nothing else

Why refuse manual entry for net weight? Because it is the cheapest thing to negotiate. Once the net figure can be typed, the scale in front of it and the contract behind it become decoration: the scale is accurate, the number was written by a person. The system therefore accepts only two things — an indicator reading and a weighing event bound to that reading. Net is gross minus tare, two decimals, one rounding rule across the whole system. If it truly must be corrected, it goes through backfill, and it shows up in reports as backfill.

Wiring the barrier is what gives the software any authority on site. Without it the system only records history: the truck has already left, the entry is typed afterwards, blocking is meaningless. With it, an unregistered plate or an exhausted quota simply does not raise the barrier. But a hard block creates a new problem — a queue — so the rule is configurable: block by default, allow an authorised override with a record. The site keeps moving, and the record shows who let the truck through.

Three ledgers, one evidence chain

Contract, weighbridge and finance can each defend themselves and each be doubted. What turns them into evidence is not a richer field list but whether three records point at the same event.

Contract ledger · quota Contract no.CS-2024-XXXX Unit price55 CNY / t Volume6,000 t Contract value330,000 CNY Paid / balance162,000 / 168,000 Weighbridge ledger · tonnage Tare (entry)12.40 t Gross (exit)51.34 t Net (computed)38.94 t Photos1 entry + 1 exit Weighed bynamed · auto time Finance ledger · settlement Sale amount2,141.70 CNY Quota deducted−2,141.70 Adjustmentswho · when · why Backfill flagfilterable Sale record1 : 1 Join key: plate + entry and exit timestamps + two photos — if the three records do not point at one event, someone touched the data Example: 38.94 t × 55 CNY/t = 2,141.70 CNY. Figures are de-identified and shown only to explain the calculation.
Three ledgers: contract holds the quota, weighbridge holds the tonnage, finance holds the settlement. They are not three datasets but three writings of one event — if the join key fails, something is wrong

A trade-off we argued about: block or warn when the quota runs out. Blocking is the compliant answer, but one queue at the gate and drivers simply take another exit — the system loses the data it was built to capture. Warning keeps traffic moving, but by month end sales and finance are arguing about an overdrawn contract. We shipped block by default, authorised override: the barrier stays down, an administrator can post a balance adjustment (reason mandatory) which lands in the adjustment log, and only then does the truck leave. Compliance and throughput both hold, at the cost of one human confirmation — and that confirmation is exactly where responsibility should sit.

The second trade-off: volume or value, whichever runs out first. A contract for 6,000 t at 55 CNY/t implies 330,000 CNY, but rates change by batch, so “tonnage exhausted, value left” and the reverse both happen. The system tracks both available quantities and treats either reaching zero as exhaustion, showing the two side by side. We deliberately do not auto-convert one into the other: once the system decides which measure closes the contract, reconciliation gets harder, not easier.

The permit has a boundary — draw it

A permit carries coordinates, depth, permitted volume and a validity period. On paper, the site can only hope. The first thing the system does is turn those coordinates into a fence.

Permitted extraction zone Vessel 01 Vessel 02 Vessel 03 Vessel 04 outside Pit · scale · barrier Beyond the fence past a threshold → an alert record: which vessel, when, where, how long An alert is not a siren but evidence: it does not stop the act, it makes the act visible afterwards Working inside Fence alert
Geofence: permit coordinates become a line the server can test against. The judgement happens server-side; the tracker only reports position — terminals can be replaced or fail without changing the rule

Positioning is a trade-off between accuracy and cost. Reporting every minute is precise, but it drains the terminal, consumes data plans and writes millions of rows a year across a fleet. We made reporting frequency situational: a low base rate normally, a higher rate inside the zone or when a deviation is suspected, and a lower rate when docked. The cost is a delay of seconds to minutes before an excursion is flagged — acceptable when the business is measured in hours, not seconds.

Cameras are for checking, not for watching. Nobody can watch dozens of streams all day. Video earns its place after the fact: when a sale record looks odd, replay the gate at that timestamp and compare plate, load and time. This is also why video recorders sit in the device module — a recorder offline means a gap in the evidence chain, and that “offline for 47 minutes” entry matters more than any explanation when a case has to be defended.

Backfill is not a back door

Field operations will meet a dead network, a broken scale, an ad-hoc truck. Remove backfill and the business routes around the system: paper ledgers return and the software is dead within a quarter. So the path must exist — just make it narrow.

  • Pit and contract are mandatory. No contract, no quota to deduct, no sale.
  • Two weights, always. Backfill still requires entry and exit weight, and the server still computes net — there is no “just type the net” option.
  • Two photos. One at entry, one at exit; a submission without either cannot be saved.
  • Two timestamps. When it happened and when it was entered are recorded separately.
  • A reason from a fixed list. Network down, device failure, ad-hoc truck — not a free-text box that says “special case”.

Every backfilled record is flagged, the sale list can filter to backfill only, and reports carry a separate column. The effect is practical: backfill stops being a quiet way to change numbers and becomes an exception that has to be explained. Used rarely, it is a safety valve; used often, management sees it immediately. That feedback is what a process is supposed to have.

The balance we aimed for: normal business should be smooth enough to need no training; exceptional business should be awkward enough to demand an explanation. Achieve both and the system survives its first year.

Access and audit: the risk is usually inside

The real threat to a sand-mining platform is not an outside attacker but an insider editing one number. All eight administration screens exist to answer a single question: who changed this figure, when, and from which IP.

FunctionWhat it solvesHow it lands
UsersOne person, one accountCreated by an administrator, never shared; disabling revokes access but keeps history
RolesWhat can be seen and changedRoles bind menus and actions: a weighing clerk cannot edit contract rates; sales cannot see raw scale readings
DepartmentsData scopingVisible pits are scoped by department, so several operations share one system without leaking data
MenusNavigation matches permissionMenus are issued per role; the front end hides what is not permitted and the server checks again
IP allowlistAccounts are not lent outOnly site and office ranges may sign in; off-network attempts are refused
Login historyWho came in, and whenAccount, IP and time in three columns; odd-hour logins stand out
Audit logWho changed whatContract adjustments, deletions and device parameter changes, each with before and after values
ExceptionsThe system's own faultsInterface errors, failed jobs and device timeouts collected in one list, so operations need not read server logs

One detail worth naming: the audit log stores the value before and after, not merely the action. A log of clicks is useless in a dispute; a log that restores the exact number is what auditing means.

What the client got

  • Eight modules and 24 screens on one key chain, so a plate, a contract and a payment can be traced to the same weighing event.
  • Two independent weights and two photos per haul, with net weight and amount computed on the server instead of typed at the gate.
  • A barrier that enforces the rules physically, with an override path that leaves a name behind.
  • Contract quota tracked in tonnage and value simultaneously, so exhaustion is visible before the month ends.
  • Geofence alerts and vessel tracks that turn “we heard a dredger at night” into a dated record.
  • Backfill and adjustments that are possible, narrow, and always visible in reports.
As agreed with the client, this page shows no client name, no site location, no permit numbers and no screenshots of production screens. Amounts and tonnages are de-identified examples used only to explain the calculation.

Building something similar?

Projects like this — site outdoors, ledger in the office — rarely fail on interface design. They fail on three questions: how the field devices connect, how exceptions leave a trace, and how one set of numbers is agreed. Bring your current paperwork to the first call and we will tell you which of the three is your bottleneck, then scope it. Related: smart factory & IoT and how we build.

MORE CASES

More Related Cases

River sand-mining management platform
Government SystemSmart sand production site, smart manufacturing

River sand-mining management platform

An IoT management platform for river sand extraction and aggregate production: eight modules and 24 ...

View Details →

View All Cases →

Planning a similar production line or enterprise system?

Start with our pricing logic, then let's talk requirements — cost structure, technology comparison and acceptance criteria, all laid out in the open.