Quick answer: Not necessarily. When measurements from different devices are combined, clock offsets, communication delays and differences in what each timestamp represents can make events appear to occur in the wrong sequence. Before interpreting a technical relationship, researchers need to establish whether the observations refer to comparable moments. Routine clock synchronisation is established engineering practice; a separate research question may arise only where the underlying technical behaviour cannot be determined from existing knowledge and requires systematic experimentation.
A Timing Error Can Look Like a Technical Discovery
A manufacturer is developing an adaptive mixing process for materials whose resistance to movement changes during production.
The proposed system adjusts the mixer motor's operation in response to changing material conditions.
The engineering team wants to investigate whether its new control approach can respond to changes in material load before they cause unacceptable variations in processing performance.
The experimental setup collects information from several devices.
A load sensor monitors the material's mechanical response.
The motor controller records adjustments to its operating settings.
A separate data-acquisition system combines those observations for analysis.
After reviewing the results, the engineers notice something unexpected.
The recorded motor adjustments appear to occur before the corresponding changes in material load.
That could suggest that the proposed control mechanism is responding to an earlier physical indicator that the team has not fully understood.
But another explanation is possible.
The load sensor and motor controller may not have recorded their observations against the same time reference.
If their clocks are offset, or if their timestamps represent different stages in the measurement process, events that occurred in one sequence could appear in another.
Australia's National Measurement Institute maintains national standards for time and frequency and provides official time and frequency dissemination services traceable to Coordinated Universal Time (UTC) Australia. Its services include GPS-based time transfer and Network Time Protocol servers.
National Measurement Institute — Time and Frequency Services
Accurate time measurement is therefore an established technical discipline.
But a timestamp alone does not establish that two devices observed the same physical moment.
The research team still needs to distinguish the behaviour of the system being tested from the behaviour of the measurement chain.
Otherwise, an apparent technical discovery may be an artefact of how the observations were timed and recorded.
Identify What Each Timestamp Actually Represents
A timestamp can describe different stages of an event.
It might represent:
• when a sensor physically sampled a signal;
• when the device processed the measurement;
• when software created a data record;
• when a message was transmitted; or
• when a central system received or stored the data.
These events do not necessarily occur at the same time.
For a slowly changing process, the difference may be negligible.
For an experiment investigating short-duration or rapidly changing behaviour, it may materially change the interpretation.
Separate clock offset from measurement and communication delay
Clock offset occurs when two devices maintain different estimates of time.
A controller might record an event using its internal clock while an external sensor uses another clock.
If the difference between those clocks is not understood, their recorded events may appear incorrectly ordered.
Communication delay is a different problem.
A sensor may capture a measurement at the correct moment but transmit it later because of buffering, network congestion or processing requirements.
If the receiving system timestamps the data when it arrives rather than when the measurement occurred, the recorded time includes that delay.
Sensor response and data-acquisition latency can introduce further differences.
For example, the physical sensing element may take time to respond to a change before the device generates the recorded value.
Correcting clock offset alone does not correct these effects.
The Australian Signals Directorate's Best Practices for Event Logging and Threat Detection recommends the use of accurate and trustworthy time sources across systems, consistent timestamp formats and synchronised time servers to improve event correlation. It identifies UTC as the preferred time standard for this purpose.
Australian Signals Directorate — Best Practices for Event Logging and Threat Detection
That guidance is directed at cybersecurity event logging rather than experimental measurement.
However, the underlying timing principle is relevant: records from different systems cannot be reliably compared merely because each contains a timestamp.
Researchers need to understand what each timestamp represents and how those timestamps relate to a common timeline.
Check Whether the Timing Relationship Changes During the Trial
Not every timing discrepancy remains constant.
A fixed clock offset may sometimes be identified and corrected.
Other differences may change over time.
A device's internal oscillator may drift relative to another clock.
Communication latency may vary.
Buffering behaviour may change as system load changes.
A correction that appears suitable at the beginning of an experiment may therefore become inaccurate later.
The research team should determine whether the timing relationship remains sufficiently stable over the period being analysed.
This is particularly important where devices operate independently or observations are collected over long periods.
Simply shifting one signal until it visually aligns with another is not a defensible solution.
The adjustment needs a technical basis.
If different plausible alignment methods produce materially different interpretations of the experiment, that uncertainty should remain visible in the conclusion.
Establish a Common Timing Reference Where Needed
Where timing is important to the research question, the experiment may benefit from a reference event observable across the relevant measurement systems.
For example, a controlled physical trigger might create a detectable response in both the motor-control system and the external data-acquisition system.
The recorded timing of that event could help investigators assess the relationship between the two timestamp streams.
Depending on the equipment and required timing accuracy, hardware triggers, common acquisition clocks or other established synchronisation methods may provide a more appropriate reference.
The method should match the technical resolution required by the experiment.
A process changing over several minutes does not require the same timing capability as a mechanical event occurring over milliseconds.
NMI's time and frequency services support calibration and traceability of time measurements to national and international standards.
National Measurement Institute — Time and Frequency Services
But traceable clocks do not automatically establish that the recorded timestamp corresponds exactly to the underlying physical event.
Sensor response time, acquisition behaviour, software processing and data transmission may still need to be considered.
Design the Experiment Around the Timing Relationship That Matters
The experimental plan should identify which conclusions actually depend on event sequence or timing.
For the adaptive mixing example, the company may be investigating whether a proposed control mechanism responds quickly enough to changing material conditions to influence the process.
If that conclusion depends on the interval between a physical load change and a motor response, uncertainty in that interval becomes part of the evidence problem.
Define the events before interpreting the interval
The research team should define what each relevant event means.
For example:
Material event: the point at which a defined change in material resistance occurs.
Observed sensor event: the point at which the measurement system detects that change.
Control event: the point at which the algorithm determines that an adjustment is required.
Actuation event: the point at which the motor controller actually changes the relevant operating condition.
Those events may not occur simultaneously.
The experiment should therefore avoid treating a timestamp recorded at one stage as though it automatically represents another.
The researchers should identify which interval matters to the hypothesis and whether the measurement arrangement can resolve that interval.
If the timing uncertainty is large relative to the response being investigated, the experiment may remain inconclusive even when each device accurately measures its own variable.
Preserve the Original Timing Evidence
Where timestamp corrections or alignment procedures are applied, the original observations should remain available.
The corrected dataset should be traceable to the source records and to the method used to align them.
Practical records may include:
• device identifiers;
• clock sources and configuration;
• synchronisation status;
• software or firmware versions;
• the meaning of each timestamp field;
• data-acquisition and recording methods;
• relevant known latencies;
• reference events used for alignment; and
• corrections applied during analysis.
This is a practical experimental-record framework rather than a prescribed R&DTI checklist.
If the correction method changes during the project, that change should also remain visible.
The team should distinguish timing differences that were actually measured from timing adjustments inferred during analysis.
This allows another technically competent person to determine whether the final interpretation depends materially on the selected alignment method.
Do Not Confuse Time Synchronisation With R&D
Establishing a common time reference, correcting a known clock offset or implementing an established synchronisation method does not automatically constitute core R&D under Australia's R&D Tax Incentive.
These may simply be necessary steps for competent engineering and reliable measurement.
A different research question may arise where the underlying technical behaviour itself cannot be determined from existing knowledge.
For example, the adaptive mixing system may exhibit dynamic behaviour that available control models cannot adequately predict under particular material conditions.
The engineering team may have competing explanations for the relationship between changes in material resistance and the resulting control response.
Accurate timing would then be necessary to test those explanations.
But improving timestamp alignment would support the experiment rather than, by itself, establish that core R&D is occurring.
Under current Australian Government guidance, a core R&D activity must be conducted for the purpose of generating new knowledge.
Its outcome must be unable to be known or determined in advance by a competent professional on the basis of current knowledge, information or experience.
The outcome must then be determined through a systematic progression of work based on principles of established science, involving hypothesis, experiment, observation, evaluation and logical conclusions.
Australian Government — Conducting Core R&D Activities
The use of sophisticated sensors, synchronised clocks or high-resolution timing does not itself establish those requirements.
The company must assess the actual technical uncertainty and experimental activity.
Make the Limits of the Evidence Visible
Current Australian Government R&DTI guidance states that records should be created at the time the activity is conducted.
Examples of relevant records include experimental plans, trial-run records and test reports showing results and evaluation.
Australian Government — Record Keeping for the R&D Tax Incentive
For experiments involving multiple measurement systems, preserving the timing context serves an additional technical purpose.
Suppose the initial analysis suggests that the motor responded before the load change.
After the devices are aligned against an independently established reference, the apparent sequence disappears.
The corrected interpretation should not simply replace the original record without explanation.
The research file should make it possible to understand:
• what the original observations appeared to show;
• why the timing relationship was questioned;
• how the alignment was evaluated;
• what correction was justified; and
• how the corrected timeline changed the technical conclusion.
For CTOs and engineering leads, that evidence helps distinguish an actual system response from a measurement artefact.
For founders and CFOs, it helps determine whether further investment should investigate an unresolved technical mechanism or first improve the reliability of the measurement process.
Conclusion
A timestamp is not automatically the time at which the physical event occurred.
Different devices may use different clocks.
They may timestamp different stages of the measurement process.
Communication, processing and sensor response can introduce delays even when the clocks themselves are correctly synchronised.
When a technical conclusion depends on the sequence of events, those distinctions matter.
Before concluding that one variable changed before another, the research team should ask:
What moment does each timestamp actually represent?
Are the devices operating against a defensible common timeline?
And is the remaining timing uncertainty small enough to distinguish the technical relationship being investigated?
A surprising sequence may reveal an important physical mechanism.
It may also reveal a timing problem in the measurement system.
The experiment needs enough evidence to tell the difference.
Sources & Further Reading
National Measurement Institute — Time and Frequency Services
Australian Signals Directorate — Best Practices for Event Logging and Threat Detection
Australian Government — Record Keeping for the R&D Tax Incentive
Talk to Ignition Research if your engineering investigation relies on measurements from several devices to establish the sequence of physical events and you need to determine whether an unexpected relationship reflects the technology or the timing of the measurement system. As a Registered Research Service Provider, Ignition Research assists businesses with research question definition, experimental design, technical investigations and contemporaneous supporting records within its registered research fields.
RSP registration confirms that the provider has met the relevant registration requirements for its registered research fields. It does not constitute government endorsement of a project or guarantee R&DTI eligibility.
We do not determine R&DTI eligibility or provide tax advice. The R&D Tax Incentive is a self-assessment program, and companies remain responsible for assessing their activities, expenditure and circumstances and obtaining appropriate tax advice.
This article provides general information only and is not tax, legal or financial advice.
Working on a project like this?
Tell us what you're building and the part you're not sure will work. A researcher from our Adelaide team (registered Research Service Provider RSP000047) reads every enquiry and replies within two business days. No documents needed.
