Industry — earthmoving & heavy plant

Your fleet is telling you something. Nobody’s listening.

Every excavator on your sites emits telemetry. It arrives in four incompatible OEM portals, in three unit systems, and nobody reconciles it against what you actually billed. We build the layer that does.

Softrear builds fleet software for earthmoving and heavy plant operators: mixed-OEM telematics ingest on the ISO 15143-3 standard, utilisation and idle analytics, predictive service scheduling, and offline-first operator apps for sites with no signal.

idle

engine hours you burn fuel on and cannot bill

4

OEM portals your team logs into every morning

days

from breakdown to the right part on site

paper

still how prestarts leave the gate

What actually breaks

Mixed fleet

Four OEMs, four schemas, four truths.

Cat, Komatsu, Volvo and Hitachi each expose hours, fuel and location differently — and none of them agree on what an engine hour is. Normalising that is the whole job, and it is the part every dashboard vendor skips.

Connectivity

There is no signal at the bottom of a quarry.

Anything an operator touches has to work with no network for a full shift, then reconcile without creating duplicate records. Offline-first is an architecture decision, not a feature you bolt on later.

Idle burn

You find out from the fuel invoice.

A machine running at idle bills nothing and costs fuel, hours and warranty life. Nobody sees the pattern until month end, by which point the site has moved on and the crew has changed.

Paper

Prestart checks that nobody can find.

Inspections, defect reports and timesheets still leave the gate on paper. When an incident is investigated the evidence is in a ute glovebox — and the defect that caused it was reported three weeks ago on a form nobody keyed in.

What we build

From the sensor to the invoice.

01

Mixed-OEM telematics ingest

One normalised machine record across every OEM feed, on the ISO 15143-3 standard where it exists and adapters where it does not.

02

Utilisation & idle analytics

Working hours against idle hours against billed hours, by machine, crew and site — daily, not at month end.

03

Predictive service scheduling

Component hours and fault-code history against your parts lead times, so the service lands before the breakdown does.

04

Offline-first operator app

Gloves-on targets, sunlight-legible contrast, a full shift with no network, and conflict-free sync when the truck reaches the gate.

05

Digital prestart & defect flow

Inspection to defect to work order to sign-off, with photos, timestamps and an audit trail a regulator can follow.

06

Fuel, carbon & billing reconciliation

Burn against hours against what you invoiced, plus the emissions reporting your tier-one clients now ask for in tender.

Case study — A civil earthmoving contractor

Four OEM portals and a spreadsheet, replaced by one fleet record.

Four OEM portals and a spreadsheet, replaced by a single normalised fleet record and an offline-first app in every cab.

Read the build →
Duration
20 weeks + run
Team
2 senior · 2 mid · 1 data · 1 SRE
Stack
Flutter · Go · Postgres · Timescale · GCP
Engagement
Dedicated team

Start with a fleet data audit.

Two weeks, fixed scope. We connect to every OEM feed you have, tell you what the data can and cannot support, and hand you the integration architecture — whether or not you build it with us.

Book the audit

Standards we work to

  • ISO 15143-3 (AEMP 2.0) telematics interchange
  • SAE J1939 CAN bus decoding
  • WCAG 2.2 AA — including sunlight-legible contrast
  • Plant safety and prestart record-keeping, to your jurisdiction’s rules

Tell us what’s stuck.

A senior engineer reads every one of these. If we’re not the right fit we’ll say so, and point you at someone who is.

Start the conversation

No spam, no drip sequence. A senior engineer replies within one business day.