Recorder Clock Changes: Preserve Timestamp Evidence Before Adjusting the Time

1 day ago

4 min read

An industrial recorder trend can look continuous while its timestamps make an incident difficult to reconstruct. A clock correction, changed workstation time zone or wrongly interpreted export can shift the apparent timing. Before changing a clock, preserve the original records and document the time convention used by each part of the system. The aim is to make the change explainable, rather than simply make the front-panel clock look right.

Separate the measurement from its time label

Treat three questions separately: what value was measured, when the device recorded it, and how the viewing software displays that time. W3C’s guidance on time zones distinguishes an instant from local wall time and a time-zone offset. A local timestamp without an offset can be ambiguous when clocks move backwards. A display conversion can also change the visible hour without changing the underlying event.

For Australian sites, record a location-based zone such as Australia/Adelaide alongside the documented instrument settings. Do not assume every Australian site uses the same clock rules. If a recorder stores only local time, document that limitation. Do not describe an export as UTC merely because a spreadsheet can reformat its date column.

Catalogue photograph of the ProSight 1–8 Channels Premium Paperless Recorder — ProSight 1–8 Channels Premium Paperless Recorder. Catalogue photograph; not a customer installation.

The ProSight 1–8 Channels Premium Paperless Recorder pictured here is listed for electronic process-data recording and offline analysis. Confirm the exact unit’s clock behaviour, export format, firmware and synchronisation options before changing settings. This guide does not claim that this model automatically handles daylight saving or exports UTC timestamps.

Preserve evidence before changing settings

Obtain the site owner’s approval and identify who relies on the records. Ask whether the data supports batch release, a complaint investigation, maintenance diagnosis or another controlled process. Agree a change window and the evidence needed to explain the change later. A time correction during a critical run may be inappropriate even when the clock is visibly wrong.

Save an untouched export using the manufacturer’s supported method. Keep the native file where available, the viewer needed to interpret it, and a separate working copy. Record the device identity, channel names, engineering units, sampling interval, firmware version where accessible and export method. Check that the files open and contain the expected period; an empty folder is not a verified backup.

Record the instrument’s displayed time alongside a reference-time observation. Note the reference source, its time zone, the comparison method and whether the instrument appears ahead or behind. A photograph can help capture the displayed settings. This is a practical comparison, not a traceable clock calibration. Where precise timing matters, obtain a suitable measurement method and specialist advice.

Make the adjustment traceable

Create a change note containing the old displayed time, intended new time, reason, authorising person and actual change observation. Follow the exact device manual. Confirm whether a time adjustment affects logging, file names, scheduled actions or alarm records before proceeding. Refer uncertain behaviour to the supplier rather than assuming that the recorder fills gaps or prevents repeated timestamps.

Preserve the pre-change files. Identify the post-change recording period separately where the instrument supports that workflow. Do not edit historical timestamps in place to make a graph look continuous. If analysis needs corrected times, create a derived dataset with a documented conversion rule and retain the original timestamp in a separate column.

Worked example: an apparent 30-minute delay

Consider a hypothetical investigation. An operator records an inspection at 14:00 on a documented reference clock. At the same observation the recorder reads 13:30. Before concluding that a process response occurred 30 minutes late, check both clocks and the export’s interpretation. This observation suggests a possible offset; it does not prove that every historical sample should be shifted by 30 minutes.

A useful working sheet contains the original timestamp, device identifier, documented time convention, proposed interpreted time and the reason for any adjustment. Mark corrections as provisional until their validity over the recording period is established. One observation cannot establish whether earlier power interruptions, previous adjustments or changing drift affected older records.

Verify the next export

Compare a short post-change export with the instrument display and change note. Look for repeated local times, missing intervals, reversed ordering and unexpected date changes. Check several channels at the same recorded point. Distinguish a real loss of samples from a display or sorting problem before drawing conclusions.

Avoid overwriting originals, treating ambiguous local times as unique events, accepting automatic spreadsheet date interpretation and combining different sites’ files without their time conventions. Where records support regulated or contractual decisions, have the responsible quality or engineering team approve the interpretation. When requesting assistance, send ProSense the exact model, firmware, sample export and required timing accuracy, after removing unrelated production or customer information.