If reports around a truck stop are missing, find the times in Plaspy when the device showed the vehicle stopped and the closest observations of movement. You can describe the observed moments and, under specific conditions, establish a possible duration range. A precise duration requires observations that identify both boundaries at the resolution your decision needs. The point of the calculation is to work out when the history is enough and when a different record could answer the question.
Consider an illustrative truck that has two jobs in the same morning and appears stopped in a pull-off between them. Dispatch wants to know whether the pause used more than ten minutes of the time allowed before the second job. The map shows observations at the pull-off, with gaps between those observations and the points where the truck was moving. The times, vehicle and allowance are fictional. The question matters because a rough estimate could leave the team attributing the whole morning's delay to one stop.
Identify the event the history describes
In the Plaspy map, open the truck device's route for the relevant period and consult its timeline . The view brings together vehicle activity and offers filters for driving, stopped, idling and alerts. Use the filters to locate the episode and then check which device information is available around it. If the time matters, preserve the date and working time zone alongside the window you used. A colleague should be able to reopen the same part of the journey.
The timeline can present an activity segment or a duration derived from available information. You can record the displayed figure as a value shown by Plaspy, along with its segment and activity type. If you need to determine the physical moment the truck stopped or resumed moving, check which observations define the boundaries. Finding a pause in the morning can be a straightforward timeline task. Testing it against a narrow operational limit may require information about the minutes around it.
Define what counts as the stop in this particular question. If a truck is waiting in a queue and moves forward a few metres, the driver may still be waiting for the same service while the vehicle alternates between moving and stationary. In the example, dispatch is interested in the time the truck spent stationary in the pull-off. If you need to know the entire wait for instructions, find out when the wait began and ended. The driver may have started waiting before the truck stopped or remained waiting while it moved slowly.
A Ruptela Eco5 Lite can provide tracking information to Plaspy when it is installed, configured and able to communicate over a mobile network. The history available for review depends on the device reports and the information available to the account. Installation and configuration affect what states and optional signals appear for a particular truck. For this review, begin with the fields you can actually see and identify what each observation represents.
Use four reported times to examine one episode
In the illustration, the truck reported movement at 7:10 a.m. It was recorded as stopped at the pull-off at 7:13 a.m. and again at 7:19 a.m. It next appeared moving at 7:25 a.m. Put those four moments in order. The 7:13 report is the first available observation of the truck stopped, so the physical stop could have begun earlier, after the movement observed at 7:10. It could have resumed before the 7:25 movement report and after it was observed stopped at 7:19.
If both stationary reports belong to one continuous stop, six minutes elapse between 7:13 and 7:19. The interval between the two movement reports, from 7:10 to 7:25, spans fifteen minutes. On those assumptions the duration falls between six and fifteen minutes. The longer interval contains the stop and may include part of the approach and departure. The shorter one lies inside the stop on the assumption that the truck remained still between those two observations.
Keep the continuity condition with the calculation. A truck can move inside a pull-off and stop again between reports. Two stationary readings at the same location leave room for that possibility. If you have no basis for treating the observations as one continuous stop, you can state that the truck was recorded stopped at 7:13 and 7:19, six minutes apart. That preserves both observations without assigning a duration to either individual stop.
The calculation also depends on the states being comparable observations of vehicle movement. If the evidence consists of two nearby locations or an ignition input state, describe it as such. Two nearby locations can appear when a truck moved a short distance. Ignition can remain active while the truck is stationary. Small coordinate differences may be visible at close zoom and still leave a brief move uncertain. Check the evidence supporting the activity label before repeating the calculation to greater precision.
Decide whether the uncertainty changes the work
Return to the illustrative ten-minute allowance. If the reports support one continuous stop bounded between six and fifteen minutes, its possible duration lies on both sides of ten. The available evidence leaves that decision open. If you needed to compare it with a twenty-minute allowance, the upper bound of fifteen would answer that narrower question as long as the assumptions remain valid. A range is useful because it shows whether the decision depends on a minute the tracking history cannot supply.
The example treats the stated times as exact to the minute. In a real review, record the resolution if a view rounds its times or displays minutes alone. If an apparent boundary matches the threshold that controls your decision, look for a more detailed record before claiming it fell above or below that threshold. Subtracting two shortened timestamps preserves the uncertainty in the original readings.
If dispatch is trying to explain why the second job was tight, check what decisions were made between the jobs. The second site's readiness, a change of instructions or the time it took to get back onto the road could also matter. Locate the stationary segment in the timeline and check the time agreed for the second job separately. Together those details suggest a question for the driver or site contact. A pause can be part of the explanation while other conditions still need to be checked.
If the remaining minutes have little bearing on the work, a precise statement about the observations may be enough. “The truck had stationary reports at the pull-off at 7:13 and 7:19, with movement recorded before and after.” If you need greater precision, ask which record can narrow the boundaries. The time dispatch sent permission to continue may help explain why the driver waited, while the moment the truck physically moved may need a different observation. Choose evidence for the fact you are trying to establish.
Use a job record to explain the stop
Suppose the driver says they pulled over to wait for an updated instruction before the second job. You can check whether they recall when the instruction came and whether they moved within the pull-off while waiting. Dispatch may have a record of when it sent the message, and the driver can explain when it was safe to read it. Keep both times. The instruction and the observed stop describe different parts of the episode. Their relationship matters when deciding what happened between the two jobs.
If the destination says it was still getting ready, ask for its usual availability record. That can help explain the sequence. A pull-off can serve several purposes, including a pause for instructions, a break or a stop dictated by road conditions. The position and time identify where to focus the conversation. The explanation comes from the people or records that can establish why the driver was there and what was happening at the destination.
Record how well the cause is established. For example, “Dispatch recorded an instruction at 7:18, and the driver confirms waiting for it at the pull-off. The GPS history shows stationary reports there at 7:13 and 7:19.” This lets a colleague check the timeline and the operating record independently. If a new detail becomes available, they can update the relevant part of the account and preserve the original observations.
Expand the time window when one boundary is missing
Sometimes a route view starts with the truck already stopped or ends while the truck is still in the same place. A view beginning at 7:13 cannot include the 7:10 movement report as a boundary. Widen the range if it is relevant and check for an earlier observation. If the boundary remains absent, state the limits of the view. You may be able to say the truck was already stationary when the available period began and was observed moving later, with the start time still unresolved.
The same issue appears on overnight journeys. A stop can start before midnight and end after it, so a single calendar day can cut out one of the reports you need. Include both dates when the question covers the whole episode and check that the job records use the same working time zone. If there is still a gap, record which part of the trip is covered and what remains to be established. The edges of a selected period belong to the review and can differ from the boundaries of the stop.
Check whether nearby observations belong to separate stops
Imagine that after the movement report at 7:25, the same truck reports stationary at another point on the road at 7:28. The movement observation can separate the first stop from the second if the activity readings are comparable. The gap between 7:19 and 7:25 helps bound the first episode. For the second, start from the movement at 7:25 and find the next useful observation after 7:28. Without an observation that establishes it resumed moving, the second pause is still missing a boundary.
If the truck instead reported stationary in two nearby places with no movement observation between them, record that the data leaves continuity uncertain. The time between the observations is a valid time difference. Adding stop durations requires evidence that the pauses are separate, with enough information about each boundary. Otherwise a total can count the same interval twice or attribute an entire gap to one reason.
Work may also continue through periods when the truck is moving. A driver waiting for an instruction could move a short distance to a safer waiting area. The time taken from the margin before the next job might include that move. If the aim is to understand the full interruption to the job, distinguish time spent waiting for the instruction from the stationary interval shown in the timeline. Use a name for each measure that another dispatcher will recognise.
Keep the same measure when comparing several trips with the same destination. If you use the stationary interval for one truck and the time from a request to the reply for another, the figures answer different questions. Look for the period and evidence that correspond to the same activity in each case, and record which values are partial. Then a later review can tell whether a difference reflects actual work or the limits of the information used in the calculation.
To make the calculation reproducible, write the observations in order and note which timestamps you used for each boundary. A colleague can then spot if a review time was taken for a reported time or if a record from another location was used as an endpoint. When the map offers several attributes, keep the one that supports calling a particular observation moving or stationary. It will also help the team correct the calculation if someone discovers a different activity category was selected.
Some episodes can be resolved without knowing the duration. If the relevant question is whether the truck was already stationary when dispatch called, compare the call time with the observations around it. A call that falls between two reports leaves the state at that instant open unless you have a basis for knowing what happened between them. That is enough to decide whether the matter should stay open for a specific follow-up with the driver.
Tell the next person which additional observation would help most. A record of departure from the site can narrow the end of the interval if it describes the same pause. An arrival message may instead narrow its beginning. If the report you need would come from a different event or location, preserve that distinction so the team can investigate the right episode.
When the team reviews this kind of episode regularly, save the route section, the observations around the stop, the duration displayed in Plaspy if available and the operational question that still needs confirmation. Record whether a supported range resolved the decision or whether someone needs another source. That is enough to prevent the episode from returning at a later meeting as a number whose meaning nobody remembers.
Before changing the time allowed between two jobs, try this review on a pause whose circumstances you know. Use the Plaspy route playback guide to return to the relevant observations. Record which minutes were observed, which depend on continuity and which additional evidence would change the decision. You can then discuss the pause with the people involved and decide what to adjust for the next trip.
