Sometimes the time a vehicle was serviced is given not as one exact moment but as a range, such as "started around 9 a.m. and finished around 9:20 to 9:30." To compare the vehicle's alcohol interlock records with the service time in such cases, it is important not to replace the uncertain times with an arbitrary single time.
An interlock is a device that controls vehicle starting based on factors such as the result of the driver's breath test. For example, the ALCOFIND AF-i1 stores test results and operating events such as vehicle ACC, engine start, and tampering detection along with date and time information. When checking whether service times and event times overlap, you need to separate "the full range in which the work could have taken place" from "the common range in which the work can be considered to have definitely been under way."
Fixing a single time changes the information
The issue time on a service receipt, the approximate time a technician remembers, and the time the vehicle was checked in do not mean the same thing. A receipt issued at 9:20 does not mean the actual work started or ended exactly then. First write down what each record's time actually marks.
Suppose, for example, that the service start was confirmed as 09:00 to 09:05 and the end as 09:20 to 09:30. On the premise that work continued between start and end, the full range in which work could have taken place runs from the earliest start time to the latest end time, 09:00 to 09:30. By contrast, the common range in which work was under way whichever start and end combination you choose runs from the latest start time to the earliest end time, 09:05 to 09:20.
Read events in four positions
Being within the full range does not confirm that an event occurred during service. Distinguishing whether it is within the common range, only at the edges of the full range, or entirely outside lets you avoid going beyond what the time data tells you.
| Hypothetical event time | Position relative to the service time range | What the time data can tell you |
|---|---|---|
| 09:03 | Inside the full range, outside the common range | It may have been during service, but inclusion cannot be confirmed |
| 09:10 | Inside the common range | Included in the service time under every assumed start and end combination |
| 09:25 | Inside the full range, outside the common range | Whether it is included depends on when the work actually ended |
| 09:40 | Outside the full range | Does not overlap in time with the stated service time |
For example, if a start-related event was recorded at 09:10, under the assumptions above it falls within the time when service was under way. However, the fact that service and the event occurred in the same time period does not by itself let you judge that the service work caused the event. You need separate information to check, such as the type of event, whether the vehicle was actually in use, and the parts being serviced and the order of work.
If the device time is also a range, compare range with range
If it has not been confirmed that the time shown in the log matches the actual time exactly, it is better not to treat the event as a single point either. For example, if a time review suggests that an event may actually have occurred between 09:04 and 09:06, this event only partly overlaps the common range of 09:05 to 09:20. Turning it into a single point of 09:05 and writing that it falls entirely within the common range makes the conclusion stronger than the original data.
In this case, it is appropriate to mark whether the whole event range falls within the common range, whether part of it overlaps the full service range, or whether it does not overlap at all. Without grounds for correcting the time, do not add an arbitrary margin of error for convenience. When comparing different records, such as vehicle logs, service documents, and photos, also check whether the date, time zone, and clock settings are on the same basis.
When there is no common range, leave the conclusion blank too
If the latest candidate start time is later than the earliest candidate end time, there is no service time that is included in every case. For example, if the start is written as 09:20 to 09:30 and the end as 09:10 to 09:25, the records alone make it hard to describe the work as a single continuous period.
In such cases, it is more accurate to record "no service time confirmed in common" than to create a tidy time period and insert it. If the work may have been paused and resumed, do not calculate it as one block. You can consider obtaining and recording each time period in which the vehicle was actually handled separately. Check-in, waiting, work, and release times must also be distinguished so that you do not overstate the period in which service actually took place.
Keep the original records and calculation results separately
In the comparison memo, it is useful to record separately the original time shown in the interlock log, the start and end ranges given by the service documents, and the reason you interpreted the ranges that way. For example, writing "09:20 is the receipt issue time" or "09:00 to 09:05 is the technician's statement of the start time" lets you recheck the nature of the data later.
For a device like the AF-i1, whose log events can be downloaded and managed, it is best to keep the original log separately rather than overwriting it with a midpoint time for ease of calculation. The purpose of comparing time ranges is not to rush to a conclusion about the cause. It is to distinguish, within the confirmed ranges, whether an event definitely overlaps, may only possibly overlap, or does not overlap, and to decide what to check next.