Construction & fleet field method

Don't Treat a Change of Hours Source as One Continuous Record

A practical office and field method for construction and fleet teams when the hours source changes — keep the old series, the change point and the new series distinct, and do not splice or convert them into one continuous utilisation trend.

Four steps when the hours source changes
01NAMERecord the old series, the dated change point, and the new series, including source, field and first new reading.
02HOLDDo not splice, convert, or rebase the two series into one continuous record or trend.
03KEEPKeep the old series, the change point, and the new series as three distinct records.
04PAUSEStop utilisation comparisons that treat pre-change and post-change hours as one series.
Illustration of a powered construction machine service area where hours may be read from more than one source after a change of record

Illustration for this article; it does not show a customer deployment, measured result or certified installation.

On this page
Key takeaways
  • A change of hours source is a break in the record, not a licence to treat the old totals and the new feed as one continuous measurement.
  • Name the old series, the dated change point, and the new series before anyone joins or ranks the figures.
  • Do not invent a conversion, offset or rebase that makes the two series look continuous.
  • Pause utilisation comparisons that cross the change point as if the definition had not changed.

Imagine a plant or fleet lead opening a utilisation file after the office changed how hours are recorded. The cab meter was the reference; a telematics field is now the business record. Or the feed used to be treated as engine hours and is now powered-on time. The temptation is to splice the old totals and the new readings into one continuous column, or to invent a conversion so the chart does not show a break. This article is a practical office and field method for treating that change as a break: keep the old series, the change point and the new series distinct, and decide what you can and cannot conclude before you compare utilisation. It reports no customer result, measured accuracy or inventory claim. Naming the hours label — engine hours, powered-on time, or a proxy — is a separate first step; start with Engine Hours vs Powered-On Time. This article covers the next decision: once the office changes the source it will use, the two series must not be joined as if they were one continuous measurement. For a tracker that looks online while a sensor field is blank, the diagnostic path is in GPS tracker online but sensor data missing — this article is about hours series after a source change, not about whether to order more devices.

A source change is a break, not a continuous record

When the office changes the hours source — from the cab meter to a telematics field, from engine hours to powered-on time, from one platform field to another, or after a firmware or mapping change that alters how the value is produced — the later readings are a new series. They are not, by themselves, a continuation of the earlier totals.

A smooth-looking lifetime curve can hide that the definition changed. A step up or down at the change point can look like a busy week, an idle week, or a fault, even though the record may only show that the source changed. Treat the moment as a record problem. The job is to name the old series, the change point and the new series, keep the two definitions separate, and stop silent splicing. Hardware that supports tracking, sensors and operational visibility can supply a candidate feed; it does not decide, by itself, that a new field may be appended to an old total. A CAN / J1939 gateway such as A300 only enters scope when the project has a powered machine and a machine field to validate.

Name the old series, the change point, and the new series

Before anyone argues about utilisation across the change, write down three records for that machine. Do not rely on a shared UI label such as “hours,” and do not collapse the earlier totals, the change itself and the new readings into one lifetime column.

RecordWhat to write downWhat it does not mean
Old seriesThe source, field name, unit, cumulative versus interval, last named value and timestamp, the workflow it served, and who used it.That those totals can be added to the new field, or that the old source was wrong and should be rewritten.
Change pointThe date and time the office changed the source, the reason, who approved it, and whether wiring, firmware, configuration or field mapping also changed that day.That the change can be hidden, back-dated, or treated as a routine increment in the same series.
New seriesThe new source, field name, unit, first value and timestamp after the change, and a note that this is a new series. Record that first reading as the start of the new series, not as work already accumulated under the old definition.That the first new reading continues the old lifetime total, or that a conversion already exists between the two sources.

Add the hours source when it is known — a verified machine interface, an agreed ignition or supply signal, a motion or vibration proxy, or UNAVAILABLE. If the source or the change point cannot be named, write UNKNOWN with an owner and a date. Keep the same separation described in engine hours vs powered-on time: powered-on time is not automatically work time, and a motion proxy is not a system of record for engine hours.

Do not splice, convert, or rebase the two series into one trend

Do not concatenate the old cumulative totals and the new readings into one column so a utilisation chart looks continuous. Do not invent a conversion factor — a ratio, an offset, or a “typical” adjustment — that makes the two series look like one measurement. Do not silently rebase the new feed so it continues the old lifetime total. Do not draw one trend line across the change point as if the definition had not changed.

Splicing and converting invent a third series that neither the cab meter nor the receiving platform produced as a single record. Rebasing hides the break. A trend that crosses the change point can make later weeks look busier or quieter than earlier ones, even though the office is no longer comparing the same kind of hours. If the first reading after the change arrives as a jump or a drop, treat that step as a change-of-source artefact until it is evidenced as something else — not as one period's measured work, and not as proof that the old series should be rewritten.

If a closed file still uses the old source, record the change separately rather than quietly rewriting history so the lifetime total looks unbroken. Keep event time, receipt time and the change-point time apart — the same discipline already used for rental-period checks on excavator and equipment rental records.

This article does not publish a universal conversion, a rebase rule, or a measured LEXUNYU field result. Agree, in writing, how the office will label a source change, and who can open a new series. Until that rule is written, treat utilisation that would join the two series as incomplete.

Keep the old series, the change point, and the new series distinct

A new feed does not erase the old series. Leave both series and the change point visible in the shared note or export, rather than overwriting the earlier totals so the lifetime record looks finished. Record, at least:

  • the machine identity and the workflows that use the hours field;
  • the old series — source, unit, field name, last value and timestamp, and who used it;
  • the change point — date and time, reason, approver, and whether wiring, firmware, configuration or field mapping also changed;
  • the new series — source, unit, field name, first value and timestamp, with a note that the series starts here, and both event time and server receipt time, or UNKNOWN where a clock is missing;
  • open hypotheses for any step at the change point, not conclusions: a different cumulative baseline, a different source type (engine hours, powered-on time, or a proxy), a unit or mapping change, a firmware or configuration change, mixed clocks, or UNKNOWN.

A listed hypothesis is a prompt for the next check, not a reason to invent a conversion or to rewrite the old totals. Do not invent a substitute continuous series from a map pin, a motion event, or the fact that the machine stayed on the same site. Location and movement can support a separate question; they are not a bridge between two hours definitions. For installation issues that appear before any platform review, see five heavy-equipment installation mistakes. Use the blank machinery installation data record (CSV) to keep the observations together.

What you can and cannot conclude

A useful source-change record can support statements such as:

  • this machine had a named old series, a dated change point, and a named new series, with these receiving fields;
  • wiring, firmware, configuration or field mapping did, or did not, change on the same day;
  • the office kept the three records distinct, and did not splice, convert or rebase them into one continuous trend;
  • utilisation that would join pre-change and post-change hours as one series is incomplete, and should not be ranked against windows that used a single named source.

The same record does not prove:

  • a universal conversion, offset, rebase rule or pass/fail threshold between the two sources;
  • that the old source was wrong, or that the new source is automatically the same kind of hours;
  • that a step at the change point is one period's work, a hardware fault, or a catch-up of unreported time under the old definition;
  • fleet-wide utilisation, hire or maintenance decisions that need one continuous lifetime total across the change;
  • destination-market marks, batch consistency, or any customer case study, inventory level or traffic metric (those remain UNKNOWN unless separately evidenced).

A source change is also a different problem from two complete, contemporaneous readings that disagree, and from a jump that follows a reporting gap under the same named source. This article deals with a break between two series, not with choosing between two totals in the same window, and not with dating a catch-up increment. For device-class context on powered plant, see how plant machinery trackers work and how to choose a heavy-equipment tracking device. Confirm the current A300 configuration path on the A300 product page before any sample discussion.

Pause rules before utilisation comparisons

Pause a utilisation comparison, a weekly ranking, or a hire-hours difference when any of these are true:

  • any machine in the comparison has a source change inside the window, or the comparison crosses a change point;
  • someone has spliced, converted, rebased, or drawn one trend across the break;
  • the change point is undated, the new source is UNKNOWN, or the first reading of the new series was treated as a continuation of the old total;
  • event time, receipt time and change-point time are mixed, or freshness is still UNKNOWN;
  • the hours source is still UNKNOWN, or the UI still merges engine hours, powered-on time and proxies under one label;
  • the asset has no fixed power (trailers, containers and many attachments need a different device class — see no-fixed-power guidance);
  • the project only needs a basic location record with no machine field to validate;
  • a closed file was quietly rewritten so the lifetime total looks unbroken.

A source change on one machine is a reason to split that machine's record at the change point, or to mark a comparison that crosses the break as incomplete — not a reason to smooth the join. For rental handover and off-hire windows, investigate resets or source changes before using a difference; see telematics for excavator and equipment rental. For site-level questions beyond hours, see choosing GPS tracking for construction sites and the construction-site GPS accuracy method. For the wider China-sample workflow, use how to validate a China GPS tracker sample before a bulk order. Platform connection depends on the selected protocol, fields and receiving system and is confirmed per project — see keep your existing system and adding GPS hardware to an existing fleet platform.

Frequently asked questions

Can we join cab-meter history and the new telematics field into one utilisation chart?

No. Treat the change as a break. Keep the old series, the change point and the new series distinct. A single chart that hides the break presents two definitions as one measurement.

Can we apply a conversion factor so the two series look continuous?

No. A conversion, offset or rebase invents a third series that neither source produced as a single record. If a relationship is later evidenced, record it as a separate note — do not silently replace the two series with a stitched total.

If the total jumps or drops when the source changes, is that one period's work?

Not automatically. A step at the change point may be a change-of-source artefact — a different baseline, a different kind of hours, or a mapping change. Do not assign it as the current period's measured work, and do not rewrite the old series to remove the step.

Is a source change the same as two readings that disagree on the same day?

No. Two complete readings in the same window are a same-time disagreement: name both, and lock the source the office will use for that workflow. A source change is a later decision to use a different source from a dated point forward. That decision still requires a written change point; it does not licence joining the earlier series to the later one. For the label distinction between engine hours and powered-on time, see Engine Hours vs Powered-On Time.

Who wrote this

Ziyi Wang — LEXUNYU, Shenzhen. Independent sourcing and integration support for fleet and industrial telematics hardware. LEXUNYU does not manufacture devices and does not operate a SaaS fleet platform. This article is a practical field method, not a field test report.

Manufacturer documents and field results vary by model, configuration, site and market. Share the intended use case and evidence requirements for a written review.