Turning suspected interlock tampering logs into a fact-check request

5 min read

An interlock is an alcohol interlock that controls vehicle starting based on factors such as the result of a test in which the driver provides breath to the handset. DATECH's AF-i1 consists of a handset and a control box connected to the vehicle, and it is described as storing test results, vehicle starts, and tampering-related events along with date and time information. Fleet managers and drivers whose vehicles have the device installed may find unusual events when downloading records regularly or during inspections.

Tampering detection is a function that detects things such as whether a person provided breath directly, whether the vehicle was driven without an approved test, and whether the device was removed from the vehicle. However, the fact that the device detected and recorded a certain state is different from a judgment that someone deliberately broke the rules. It is more accurate to organize a suspicious log not as a document stating a conclusion, but as a fact-check request asking for the original records to be compared with the vehicle situation at the time.

Do not mix the device's records with people's judgments

In the first part of the request, write down the original text the device recorded exactly as it is. This covers the event name, the date and time recorded on the device, the test- and start-related records before and after it, and the time the log was downloaded. If the original text is in another language or uses abbreviations, keep the original and add an explanation in a separate field to aid understanding.

On the other hand, do not put sentences that conclude a cause, such as "someone else clearly took the test" or "the driver removed the device," in the observation record. The AF-i1 is described as detecting whether a test was taken directly using the temperature, humidity, speed, and strength of the breath, and as detecting vehicle operation without an approved test and removal of the device. However, which event the actual device recorded under which conditions can only be seen by looking at that device's user manual, the settings data at the time, and the exported original log together.

Store the original file and review documents separately

Keep the log file first downloaded from the dedicated software as an unmodified original. Noting the date and time it was downloaded, who downloaded it, and the start and end times of the records in the file makes it easier for later reviewers to understand the scope of the data. If you overwrite the original by saving it again, or keep only a file from which rows that seemed unnecessary were deleted, it becomes hard to explain whether the records were complete.

Make tables or event timelines that extract only the relevant time periods for easier reading as separate review copies. For example, if you extracted only the records from 30 minutes before and after a particular event, mark in the document the time range extracted and the range excluded. Data that can be linked to individuals, such as vehicle usage information, can be passed only to the people taking part in the fact check, and you can consider reducing personal information unrelated to the review in shared copies.

Put both the materials and the questions in the request

A request that only says "please check the suspicious event" tends to make the scope of review broad and the conclusion vague. Separate the device records, materials showing the device and vehicle condition at the time, and the explanation of the person who used the vehicle as different sources, and write down what you want to confirm with each. Maintenance records only show whether wiring, power, or vehicle maintenance work actually took place. They are not grounds that automatically explain the cause of an event.

What to organize What to put in the request Question to confirm
Original device records Original event text, recorded time, downloaded file information What state did the device store, and when?
Device and vehicle materials Device identification, settings data at the time, vehicle maintenance and power work history Do the recorded times overlap with installation or maintenance work times?
How the vehicle was used The vehicle user's explanation, when it was heard, verifiable schedules Are there differences between the explanation and the log that need further checking?
Review results Confirmed facts, items not confirmed, next items to review Which questions are settled and what remains?

Device settings data means documents or software screen records that show the settings in use at the time. The vehicle user's explanation is kept as a separate source, not as evidence that replaces the original log. Splitting them this way lets you examine separately an explanation that maintenance work took place and the fact that a device event exists at the same time.

Set everything from observation to completion criteria in a hypothetical case

Suppose, for example, that a manager downloading the monthly log finds an original event related to detection of vehicle operation without an approved test on a particular date. The observations here are the event's original text and recorded time, and the test- and start-related records just before and after it. The possible interpretation at this point is limited to the device having detected and stored that state. It is not the stage for concluding that a particular driver drove while bypassing the device.

A possible action is to preserve the original log and separately gather the vehicle maintenance and power work history and the account of vehicle use for the same time period to compare them. If the device's recorded time and the time on a maintenance document differ, do not change either one. Show the time recorded on the device and the time written on the document side by side. If needed, also include the device's clock status and the time the log was downloaded among the items to check.

The completion criterion in this case is not concluding a cause. The purpose of the fact-check request is achieved when the facts that agree among what remains in the device's original records, the work confirmed on the vehicle, and the account the user gave are distinguished from items not yet confirmed. If further review is needed, write the remaining questions specifically so the next person in charge does not have to search for the same materials again.

Separate confirmed and unconfirmed content in the review results too

After the review, record it in sentences that show the evidence, such as "confirmed the specific event and time in the original log," "confirmed the maintenance work history for that time period," and "the account of vehicle use needs further confirmation." If unconfirmed items are treated as normal, or something is written up as a deliberate act just because it is suspicious, the meaning of the record changes.

The AF-i1 is described as allowing log events to be managed and downloaded through dedicated software and as storing data related to interlock use. The point of this feature is not to interpret many events at once. Only by separating the original text the device recorded, the work actually done on the vehicle, and the situation the vehicle user described, and bundling them into questions a reviewer can answer, does a suspicious log become verifiable fact-check material.

References

#AF-i1
#interlock tampering
#log review
#fact-check
Considering our products?
We'll help you decide.