Equipment Log Maintenance: Keep the Clock Context Visible

An equipment support log may appear to run backwards when entries from different components are placed in one table. Before calling this an impossible event sequence, the maintainer should ask what the displayed times represent. A clock reading, a relative logging value and the order of rows in an export can answer different questions. This article uses a hypothetical support extract and reports no actual equipment timing fault.

Preserve the order in which the extract was received

Imagine that an investigator receives two extracts and sorts them by a column labelled time. An entry that seemed later in one extract now appears earlier in the combined table. The maintenance record should retain both original extracts and the transformation used to create the table. Sorting is an editorial or analytical action, not a new observation of the original events.

Identify the source component, the field name and any explanation accompanying the timestamp. If an extract lacks that context, mark it unknown. Do not replace its times with values from another component merely to make the sequence look plausible. A note that preserves an unexplained discrepancy is more useful than a tidy timeline whose assumptions have disappeared.

Different time abstractions need an explicit relationship

The historical ROS 2 Clock and Time design document distinguishes SystemTime, SteadyTime and ROSTime abstractions. It explains why a robotics program can need different notions of time. This conceptual document does not identify the clock used by any particular equipment log, and it should not be presented as a guarantee about every current implementation.

For the fictional extract, ask the supplier or responsible developer which field was recorded and how it relates to the component's other time values. An unfamiliar label should not be automatically interpreted as system time. Equally, an apparent reversal should not be attributed to simulated time merely because the equipment software uses ROS. The record needs evidence for that specific relationship.

The maintainer can keep several explanations open while the field definitions are requested. The extracts might have different origins, a transformed display might omit context, or a clock relationship might need explanation. These are investigation questions, not findings. Nothing in this article changes a clock, starts a replay or modifies the behaviour of a connected controller.

Read a logging field according to its own definition

The Python logging documentation separately describes the LogRecord creation time and a relative creation-time value measured from when the logging module was loaded. This is a concrete example of fields with different reference points. It does not mean that a supplier's column called elapsed uses either of those fields.

If the supplier identifies a field as such a relative value, preserve its stated reference and scope. A relative value from one process should not be placed on another process's timeline without an explained relationship. If the original reference is missing, document that gap instead of assigning an assumed start time from a convenient nearby entry.

The same care applies to a human-readable date added during export. Ask whether the export formatted an existing value or introduced a separate observation. Keep the raw field and the displayed text distinguishable. A changed presentation can explain why two views look different without establishing that the equipment experienced a time reversal.

Record a comparison that another maintainer can follow

An authorized follow-up can identify the exact extracts being compared, their field definitions and any transformation applied. Keep its findings alongside the original discrepancy. If the new information explains the display but leaves the relation between source clocks unknown, close only the display question. Do not manufacture a complete sequence simply because the report expects a single ordered list.

In the imagined handover, a useful outcome might be a clarified column description rather than a software change. Another investigation might require a controlled observation arranged by the responsible team. The maintenance record should distinguish those outcomes and identify work that has not occurred. A documentation correction is valuable without being described as a repaired controller.

The record can also explain whether the disputed order came from the original export or from a later spreadsheet operation. This small distinction prevents an analytical presentation choice from being remembered as something the equipment itself recorded. Preserve the transformation description next to the combined table so that a later reader can reconstruct the question.

When preparing a summary for other staff, state which time relation has been established and which remains uncertain. Avoid calculating an event duration from unlike reference points. If a duration is later supplied by a responsible investigator, retain the calculation's inputs and scope instead of retroactively making the original extracts appear self explanatory.

The original diagrams illustrate field relationships rather than a measured timing trace. Related material is available in the equipment information section and the article directory. Keeping clock context visible lets a maintenance team investigate an apparent reversal while preserving the difference between a recorded field, an interpreted timeline and actual equipment behaviour.