Usage hour tracking

Running hours, per unit, without a paper logbook.

Every hour a unit runs is captured against that unit - not against a job code, a driver, or a shift. This is the base signal every other capability reads from.

Signal
Per unit hours
Source
Telematics + manual
Cadence
Continuous
Written to
Fleet board
How it is captured

Two inputs. One record. One number that matters.

Telematics streams where available. Manual close of day where not. Both converge on a single per unit hour count that everything else reads.

01
Ingest

Telematics or ECU streams read directly when supported. Manual close of day where the machine is not instrumented.

02
Reconcile

Duplicate entries, gaps and drift are reconciled against known service intervals and prior usage.

03
Attribute

Every hour is attributed to a unit and its current site - not to a shift or a person.

04
Publish

The board is updated. Predictive maintenance, allocation and consumables all read the new number.

05
Audit

The full trail is preserved - who added the manual close of day entry, when, and what was reconciled.

06
Alert

A missed close of day for an active unit is surfaced the next morning, not the next month.

Worked example

One unit, one week.

Excavator EX-11 across a full working week. Notice the shift from ok to watch as running hours cross the 82 percent threshold of the service interval.

Board fragment
Excavator EX-11 - week view
Live board
Monday- Sector 1
Cumulative 198.4h of 400h
8.4h
Healthy
Tuesday- Sector 1
Cumulative 207.5h
9.1h
Healthy
Wednesday- Sector 1
Cumulative 215.1h
7.6h
Healthy
Thursday- Sector 2 - moved
Cumulative 225.3h - watch triggered at 82 percent
10.2h
Watch
Friday- Sector 2
Cumulative 235.1h
9.8h
Watch
Saturday- Sector 2
Cumulative 241.1h
6.0h
Watch
Board wrote 51.1 hours to EX-11 this week. Service window projected at end of next week, not by calendar rule.
What the record looks like

A row per unit, not per driver.

The unit is the primary key. A driver rotation, a shift handover or a subcontractor switch does not fragment the record. Hours belong to the machine.

Primary key
Unit ID
Foreign keys
Site, shift, service history
Honest coverage note

What is captured automatically and what is not.

Telematics coverage varies by manufacturer and vintage. We are direct about which fleet we can auto capture today and which cases fall back to a supervised close of day entry.

Auto captured today
  • Late model machines with a supported telematics port
  • Generators with a controller that exposes running hours
  • Fixed sensor installs on older machines that support a retrofit
Falls back to supervised entry
  • Machines with sealed controllers that do not expose a data port
  • Rental units on short deployments where retrofit is not economical
  • Sites without connectivity - logs sync on the next connected shift
Build your board

Tell us the shape of your fleet. Watch the board light up.

Pick the equipment you actually run. Set a rough count. The board rebuilds live at your scale, with an illustrative mix of healthy, watch and service due units - and a sample reallocation suggestion.

Equipment types
Rough count
24units
650100150

An illustrative view based on typical patterns - not a live read of your actual fleet. Real data appears once your equipment is connected.

Illustrative board at 24 units
Simulated
Crane #01
Sector 1 - active
Healthy
Hours this month
60/ 500h
12%
Crane #02
Sector 2 - active
Healthy
Hours this month
270/ 500h
54%
Crane #03
Sector 3 - active
Healthy
Hours this month
60/ 500h
12%
Crane #04
Sector 4 - active
Healthy
Hours this month
270/ 500h
54%
Crane #05
Yard - active
Healthy
Hours this month
60/ 500h
12%
Crane #06
Sector 1 - active
Healthy
Hours this month
270/ 500h
54%
Board rebuilds as you change the mixBoard scale 1 : 4