DEV Community: I SOL

Three Different Numbers for the Same Truckload: A Data Reconciliation Problem in Mining

I SOL — Fri, 21 Aug 2026 06:15:23 +0000

Picture a single truckload of ore. By the time it's gone from the pit to the crusher, it has three different weight readings attached to it, recorded by three different people, on three different paper forms, none of which talk to each other. That's not a hypothetical — it's the default state of ore flow accounting at most mine sites, and it's a surprisingly clean example of a distributed data consistency problem playing out with clipboards instead of databases.

Here's the setup, why it breaks down, and what fixing it actually looks like.

Why end-to-end ore data matters

For any mineral resource company, reliable ore flow data isn't a reporting nicety — it's the input to real decisions: how you value reserves by site and deposit, what your actual extraction volumes and grades are, how much you're losing in-situ during mining and re-evaluation, and how much ore is genuinely available for downstream processing. Get the data wrong and every decision built on top of it inherits the error.

The pipeline, as it actually exists

Ore flow accounting happens across several stages: appraising explored and newly discovered resources, estimating reserves before extraction, adjusting for losses during haulage and handling, and assessing ore prepared for blasting and fragmentation, among others.

In practice, the same underlying event — one truckload of ore moving from point A to point B — gets recorded manually, independently, in separate paper logs at every stage, from the moment a loaded haul truck leaves the pit to the moment it discharges at the crusher. Nothing links those records together. Nothing reconciles them. Each log is its own silo, filled in by a different person, at a different point in the workflow, with no shared source of truth.

Where it actually falls apart

This is the part that'll be familiar to anyone who's dealt with eventually-consistent systems that never actually converge. Here's a single load, tracked through three independent writers:

A mine surveyor at the pit logs 42 tons for a load from Block 7, based on the excavator's onboard scale.
The dispatcher at the plant gate logs the same haul at 43.5 tons on the weighbridge — because the truck came in with its body still raised.
The driver writes down 40 tons on the waybill, because that's what keeps them under the axle load limit.

Three sensors, three contexts, three numbers, zero reconciliation. By end of shift, accounting is manually trying to figure out which of three conflicting values to trust for a single event. Multiply that across a month of loads and the discrepancy compounds to 3–5% — and because nothing traced the individual events, there's no way to go back and pinpoint where the actual shortfall happened. You just know the totals don't add up.

What an actual fix looks like

The fix isn't "get people to be more careful" — it's giving the data a single, structured, traceable path instead of three disconnected paper trails. That's what an electronic log (we used logsheet.ai) is actually solving: a single-page form with clearly labeled fields, filled in at each transfer point, that becomes the one record of the event instead of a new, independent one every time.

Concretely, that gets you:

One continuous data thread from the block to the crusher, instead of three unlinked logs.
Automatic reconciliation between transfer points — if two readings for the same event don't match, the system flags it immediately instead of surfacing the gap a month later in a totals report.
Real-time visibility into the data, not end-of-shift paper collection.
Fewer disputes, because "42 vs. 43.5" gets resolved against a system of record instead of three people's memory of whose scale was right.
Production reports generated directly from the log data, on demand, instead of hand-assembled from multiple sources.

What rolling it out actually takes

This isn't a multi-month systems integration project. The rollout is three steps: set up the logs using ready-made templates configured for your blocks, equipment, and warehouse; train the team to work from tablets they carry to the actual measurement point instead of a clipboard; run one trial shift to confirm it holds up under real conditions. In practice that's a three-day turnaround to a working system tailored to a specific quarry.

The actual payoff

The real shift isn't "digital instead of paper" — it's moving from average, backfilled indicators to real, event-level data you can trust. That changes what you can actually do with it: supply planning based on real numbers instead of estimates, an accurate read on subsurface balances, and processing efficiency gains that come from finally knowing where the material actually is instead of reconstructing it after the fact.

Why We Didn't Build an MES: Tracking Production Data With a Glorified Spreadsheet

I SOL — Wed, 12 Aug 2026 07:13:08 +0000

If you've ever tried to get a straight answer out of a factory floor — "how much raw material did we actually use today, and how many units came off the line" — you already know the problem. Paper checklists say everything's fine. Reality says otherwise. And the gap between the two is exactly where downtime, defects, and budget overruns hide. That's the gap platforms like logsheet.ai are built to close.

We ran into this on a discrete manufacturing line — multiple departments, multiple handoffs, no single source of truth for material balances, defect counts, or output. The instinct is to reach for a full Manufacturing Execution System (MES). We didn't, and here's the reasoning, plus what we built instead.

Why bother tracking this at all

Before getting into tooling, it's worth being explicit about what production record-keeping actually buys you:

A live picture of the shop floor without needing to physically walk it.
Source data for planning — real output, consumption, and time norms only mean something if they come from real records, not estimates.
No gap between what's actually happening and what gets reported upward.
The ability to trace a defect back to the exact stage it occurred, and assign the cost to the right place instead of burying it in general opex.
Downtime visibility at every stage, not just the stages someone remembered to mention in the standup.
An audit trail for ISO and customer compliance.
Enough historical data, eventually, to build a digital twin of the process or move toward predictive maintenance.

None of that requires a six-figure platform. It requires structured, timestamped data that people actually fill in.

The MES option, and why we passed on it

The obvious heavyweight answer is a full MES: ZIIoT (Tsifra), Golfstream (Ascon), 1C:MES Manufacturing Execution — systems that plug into ERP, distribute orders across shifts and machines, and pull real-time data off the equipment itself.

They're the right tool if you're operating at serious scale. But they come with a specific cost profile:

Licensing and implementation running into the hundreds of millions of rubles.
Rollout timelines measured in months at best, years in the worst case.
A break-even point that only really makes sense north of ~10,000 employees, with high production volume and enough process variability to justify it.
A downstream requirement to rebuild your reporting and analytics methodology around the new data model.

For a mid-size line, or for tracking a secondary process that doesn't need full automation, that's a lot of infrastructure to buy just to answer "how much material did we use."

What we built instead: log sheets, not a platform

The lightweight version is closer to a well-structured spreadsheet than a platform: a system of log sheets. Setting one up is genuinely a five-step exercise:

Create a flexible table.
Define the process it covers (quality control, inter-shop equipment transfer, whatever's relevant).
Set the metrics to record — deadlines, quantities, units of measurement.
Assign who's responsible for keeping it up to date.
Set how often it needs to be filled in.

From there the system prompts people for what's due and when, and entries happen from a phone or tablet right on the floor — no walking back to a terminal. Reports roll up per shift, per period, or in real time, and a single dashboard can pull from multiple logs at once. You build the report by picking the relevant logs/checklists and a reporting window — no custom query writing.

A concrete example: a plastic container line

Here's the shape of it on an actual line — a plastic bottle manufacturer that needed live logs for raw materials, finished goods, and inspection results.

Raw material log — receipts and issues, balance recalculated automatically on every entry:

Date/Time	Material	Supplier	Received, kg	Issued, kg	Balance, kg	Responsible
Jul 1, 2026 09:15	HDPE (pellets)	PolymerTrade LLC	1000	0	1000	I. Ivanov
Jul 1, 2026 10:30	HDPE (pellets)	PolymerTrade LLC	0	200	800	P. Petrov
Jul 2, 2026 11:45	Colorant (blue)	ChemReaktiv JSC	50	0	50	S. Sidorov

When the warehouse worker receives a batch, they log the quantity and the balance recalculates on its own. When material goes out to the floor, same thing in reverse. The log is always current — no end-of-week reconciliation.

Finished goods log — plan vs. actual, by line and shift:

Date & Shift	Line No.	Product	Plan / shift, pcs	Actual, pcs	Runtime, h	Operator
Jul 1, 2026 / Shift 1	1	Bottle 0.5 L	5000	4850	7.5	A. Smirnov
Jul 1, 2026 / Shift 1	2	Bottle 1.0 L	4000	4100	8.0	V. Kuznetsov
Jul 2, 2026 / Shift 2	1	Bottle 0.5 L	5000	5020	7.8	M. Orlova

This is the log you cross-reference against the raw material log to see whether output lines up with what went in.

Quality control checklist — per batch:

Inspection Step	Answer Options	Note
1. Visual appearance	Conforms / Does not conform	Photo of defect
2. Dimensions (height, diameter)	Within spec / Deviation	Enter value
3. Seal integrity	Intact / Defective
4. Unit weight, g	(enter value)
5. Color (vs. reference)	Conforms / Does not conform
Overall verdict	Batch accepted / Rejected / Partial reject

Tie all three together and the report writes itself: how much raw material went into how many finished units, what the defect rate was, and how actuals diverge from plan — auto-calculated, not hand-tallied at the end of the month.

Where else this pattern applies

The same log-sheet-plus-checklist pattern covers a lot more than this one example: general construction logs, operations logs, equipment logs, maintenance logs, temperature logs, safety logs, incident logs, and so on. It's the same five setup steps every time.

The trade-off, honestly

This isn't a replacement for an MES if you're at real scale — it doesn't do real-time machine data capture, and it won't replace deep ERP integration. What it does do: get you from zero to structured, timestamped, queryable production data in about the time it takes to define your columns, without months of implementation or a seven-figure line item. For a lot of teams, that's the actual bottleneck — not the lack of a platform, but the lack of any structured record at all.

Your Checklist Is All Green and the Equipment Still Broke: 5 Reasons Why

I SOL — Mon, 10 Aug 2026 07:59:57 +0000

A checklist that's fully "green" tells you nothing if the boxes were ticked from habit. On an ExxonMobil subsidiary's site, every stage of production had checklists in place — and equipment was still failing far more often than the paperwork suggested. Nothing looked wrong on paper; the wrongness was in how the lists were filled.

We rolled out logsheet.ai there and, in the process, catalogued five failure modes that turn a checklist into theater. Here's each one and what we changed.

1. Ticking boxes as a ritual

Operators weren't comparing readings to reality — they were ticking to finish. Separator pressure had sat at 4.2 atm for several shifts; the spec is 4.0–4.5, so the operator marks "normal" without looking. Scrolling a long list and checking every value against limits simply takes too long, so habit wins.

The result was a shift log with zero signal: equipment running in emergency mode, two unexpected breakdowns in the same area in one week, emergency repairs replacing scheduled maintenance, and no way to pin down when degradation started. At that point the equipment is unsafe to be around.

Fix: kill the checkbox. Replace it with an actual numeric value (temperature, pressure) or a drop-down. Operators pushed back for a couple of weeks, then adapted. Buy-in only held once we also cut the volume of what they had to enter — which leads directly to #2.

2. Information overload

Depending on the unit, a checklist ran 20–40+ items. In practice people read the first few and last few lines and defaulted everything in between. Separator pressure — a critical indicator — lived on line 12 and got auto-marked "normal" forever.

Management resisted trimming: dropping any parameter felt like a safety risk. So instead of blunt deletion we made the list conditional in logsheet.ai:

show only parameters relevant to the current task, hide the rest;
force critical items first, mark the rest optional (an abnormal pressure reading auto-reveals a comment field and a photo upload);
adapt to shift and section so only what's needed is visible;
surface extra items only when a trigger value fires — hidden under normal conditions.

Net effect: 10–15 items instead of 40, and operators spent the freed-up attention actually filling them in. Reports got sharper.

3. No feedback loop

Operators had no visibility into whether their entries mattered. The job felt like "complete the checklist," not "make the entry true." Management didn't monitor completion or attach any consequence, so honesty quietly decayed.

We piped completed data into reports and dashboards visible to operators and managers. On one dynamic-equipment sound check we cross-referenced checklists against breakdown records:

not a single checklist flagged a problem;
the checklist data didn't match the breakdown history — it was false;
we lined up failure dates against checklist dates and the person who signed off right before each failure;
that surfaced exactly who was filling lists without reading the equipment.

Feedback like this makes verification feel inevitable, so lists get filled honestly. For managers it doubles as a per-employee KPI on both quality and timeliness.

4. Filling the list from memory at end of shift

The "experienced, too-busy" operator reconstructs the whole checklist from memory at 6 PM instead of logging at the point of measurement. You get inaccuracies, and you can't reconstruct when something went wrong or who owned it.

Fix: fill it on a mobile device. The app records location and entry time, so late/off-site entries get flagged. One operator — John Henderson — was entering data from the office at 8 PM that should have been logged at 2 PM on the floor. That analysis became a new KPI for logging at the point of measurement, plus a scheduled prompt for entries at set times and voice-message input for speed.

5. The checklist isn't wired into shift handover

The lists lived outside the handover, so the incoming crew re-solved problems the outgoing crew had already cracked. On a well pad, day shift found the electric actuator on the methanol dosing valve knocking and not seating — fixed by turning the valve three extra turns because the limit switch was sticking in the cold. Night shift got a vague verbal handoff. When it recurred, someone opened the valve too far, methanol had to be shut off, and 3.5 hours went into re-diagnosing what was already known. The logbook would have made it a few minutes.

Fix: the incoming shift starts by filling a checklist auto-generated from the previous shift's entries, plus a "traffic light" that rates the prior list in real time on:

where the person physically was when they filled it;
the gap between the event and the entry;
how fast it was completed — thorough vs. rushed.

What "operational" looked like

Automating a few processes turned the system into something worth trusting: lists capped at 10–15 items and split into sections; real-time completion via mobile and voice; KPIs on quality and timeliness; statistics used to analyze results; and checklists wired into handover. The checklist stopped being a wall of checkboxes and became a tool that produces an informative shift report, catches deviations early, and triggers corrective action before the breakdown.

5 digital logbooks for shift handover, compared: logsheet.ai, MaintainX, Redlist, Fiix + a Chrome extension

I SOL — Fri, 24 Jul 2026 06:53:56 +0000

If you run a continuous-process line, the shift handover is where information quietly leaks. The outgoing crew fills paper logs — process parameters, equipment failures, the decisions they made at 3 a.m. — and the incoming crew has to re-read all of it before they can safely touch anything. On paper that reconstruction is slow, and core work waits while it happens.

Moving that handover into a database fixes the leak: entries are structured, searchable, and consolidated into a report the next shift can skim instead of decode. Below is a side-by-side look at five tools that do this — with prices, the paper logs each one replaces, and the industries they actually fit.

1. logsheet.ai

Price: $99/month for up to 30 users.

logsheet.ai is built around two roles in the handover:

the outgoing shift fills out a digital logbook;
the incoming shift works through a checklist of completed tasks and checks.

Everything written to the database — text or voice messages — is consolidated into reports, so you can analyze each stage of the process and production as a whole. It covers a wide range of production docs: maintenance/repair logbooks, an operations logbook, instrument and meter readings, a transport log, employee task logs, and more. Entry works from a computer, tablet, or phone.

Fit: discrete manufacturing (electronics, furniture, automotive components, building materials, mechanical engineering, metalworking) plus mining, oil, and gas — anywhere those logs are already being kept.

2. MaintainX

Price: ~$1,950/month for up to 30 users.

MaintainX is a mobile-first logbook app aimed at automotive, manufacturing, and commercial real estate management. It replaces operational, control/quality, safety-and-permits, and maintenance/repair paper logs.

The handover model is task-based: the system generates a task for the incoming crew that carries the outgoing shift report, which should flag anything needing immediate resolution. A real-time dashboard shows the previous shift's results, open issues, and the current shift's plan.

3. Redlist

Price: not publicly advertised.

Redlist targets maintenance and repair of movable assets — mining, manufacturing, shipbuilding, construction, oil and gas.

Workflow: an employee enters indicator values into the chosen production log through checklists, can attach a photo and a voice message, then signs off with an electronic signature. At shift end the system compiles everything into a report the incoming employee reads in the web version.

4. Fiix

Price: ~$1,350/month for up to 30 users.

Fiix records data through hourly log sheets that operators fill in; any deviation from standard parameters is auto-highlighted. At shift end a report is generated for the next operator, and the system raises repair requests for equipment that failed during the shift.

It fits heavy industry and process manufacturing — oil and gas production, pulp and paper, metallurgy, energy, food — and replaces paper logs for process parameters, downtime/accidents (incident log), cleaning/sanitization, and work permits.

5. "Production Journal" Chrome extension

Price: free (Chrome Web Store).

A simplified app from logsheet.ai that lives in Google Chrome. Good for subcontractor work logs, issuing production orders, tracking construction/installation status, materials and equipment on-site, and recording changes/deviations. Handy when you're at a remote site, need mobile responsiveness, want a quick start, or are logging repetitive tasks. Handover: the outgoing employee fills in or updates the process parameters, the incoming one reviews the current register.

Side-by-side

Tool	Cost	What stands out	Where it fits
logsheet.ai	$99	Structured logs + checklists, voice input, auto report consolidation	Mechanical engineering, food, oil refining
MaintainX	$1,950	Task assignment, prioritization	Automotive assembly, petrochemicals, mining/metallurgy
Redlist	—	Photo + voice capture, e-signature, auto shift report	Mining, shipbuilding, oil & gas
Fiix	$1,350	Task handover with photos/comments, hourly logs with deviation alerts, auto reports	Metallurgy, energy, pulp & paper
Chrome extension	—	Fast entry, voice field recording	Construction sites, logistics terminals, remote sites

The common thread: once process data lives in a structured system instead of a paper stack, transferring a shift on a continuous line stops being a race against lost information.

Shift handover

I SOL — Fri, 24 Jul 2026 05:58:00 +0000

When one shift ends and another begins at a continuous-cycle enterprise — where production runs uninterrupted from the moment raw materials are fed in until finished goods come out — it is critical to transfer control of the process carefully, without overlooking any key details.

Typically, the shift handover period is set by the employer in consultation with the trade union (if one exists) and does not exceed 30 minutes.

The duration of this process is influenced by:

the volume of operational documentation,
the amount of equipment involved in the technological process,
and other factors.

Digital alternatives eliminate the need for specialists from both shifts to be physically present at the site at the same time, and they cut down on the time spent filling out logs and checklists. With such systems, the outgoing shift enters all necessary data into the database, which the incoming shift can instantly access.

One of these is the logsheet.ai system. It can be applied to most enterprises across various industries:

including discrete manufacturing, which, according to the International Association of Industrial Engineers, is used in more than 75% of industrial enterprises worldwide. From a management standpoint, any discrete manufacturing environment is inherently complex. Each process follows a specific sequence and has varying throughput rates, so its parameters must be recorded — especially during shift handovers;
and in continuous production, where a vast number of logs must be maintained — such as operational logs, mine air sample analysis logs, shaft inspection logs, work logs, and shift handover logs — for example, in mining operations (quarries, mines, and pits).

The specific information required depends on the company's focus. Moreover, the format can vary — logsheet.ai offers two options: a production log and a checklist.

The production log includes text and voice recordings, which are integrated with checklists, and generates reports for management based on those recordings. Reports can be compiled from multiple logs, providing a more comprehensive view of production progress. Logs are completed by each shift during handover, enabling incoming employees to quickly understand what was happening at the facility before their shift and what issues need attention during their work.

The checklist contains the items that the incoming shift most commonly needs to verify. For instance, it may include reviewing production log data upon arrival. Automation adds more visibility to routine tasks by allowing operators to mark items as completed once they are finished.

Electronic logs and checklists make it easy to quickly review any issues left by the previous shift, understand the tasks ahead for the incoming team, and thereby ensure process safety and the achievement of key performance targets. Learn more about the benefits of using electronic logs at logsheet.ai.