en de
View Categories

Time models

5 min read

Keypoints

  • In the Lobo, logistics and timing are interconnected, as evidenced by the detailed management of order times within the dispatch panels.
  • Each order has calculated time windows for pickup and drop-off, enhanced by a reference time indicating when the job was created and a display time that helps order the jobs strategically.
  • The system also allows for customization through time models that specify minimum and maximum scenarios for travel and handling times, ensuring adaptability to various delivery situations. 
  • The integration of these times is crucial for prioritizing jobs effectively, with the system automatically adjusting the display and reference times based on predefined conditions or manual adjustments by users.
  • This tutorial provides insights into how time models function within Lobo.

Transcript

Some people say logistics is all about time. So let’s have a look how the time is represented in Lobo. I switch to the dispatch panels and here we have a look on our orders. For each order we calculate time window for the pickup and the drop off. In this case 16:30 to 16:45 and 16:40 to 17:00. When I opened the job, I can also see this time in this here. And we have some more time components.

We have the reference time that is typically the order time, so the time the job was created, and we have something called display time. That’s actually the time that’s used for ordering the jobs in open orders. So where does all this information come from? To get an idea, I switch to view calculation time models. And here I’ve prepared a time model that I called express example.

So basically you will find two columns here. Column that’s called minimum. That’s actually the best case scenario and a column that’s called maximum. So that’s the worst case scenario. So how can we set the timings here? Actually, for both of them, we differentiate between the pickup, that’s the time to get to the point A, and the drop off, so that’s every next point, B, C, and D.

So we could also set a starting point but I disabled that for the moment. But what I did, I say, in the best case, I have a travel time to the pickup of zero minutes. That means, by chance I’m just in front of the pickup, so I’m there immediately. And I assume that I have a loading time of five minutes at the pickup.

And I say, in the best case, I have a routing factor of 0. 9. That means I just assumed that I’m 10 percent faster than the routing time that comes from the routing service. But I say between two stops, at least it takes me three minutes, even if they are very, very close. And for every loading time, I assume two minutes.

That’s the best case scenario. And then I have in the maximum column, let’s say that’s the worst case scenario of all the times that I guarantee my customers, I say the minimum to get to the pickup is 25 minutes. The loading time is five minutes. That’s makes 30 minutes to get there. And for the rest, for every next stop I probably increases a little bit. I say 20 percent buffer and I say at least 10 minutes between each stop. And let’s say 10 minutes handling loading time at each stop. And I also said minimum the total is 60 minutes. You can also, or you also need to set the availability. Maybe let’s add the weekend here.

And in the options, you can set the default lead time. So that’s the one that influences display time and rounding value. So we round everything to full five minutes. I click save here, and I’ve just created this time model. Actually you can switch between the time models anytime. So for example, could create a new direct delivery time model, set the values here.

And then how can you activate it for product? Then therefore I have to switch to calculation base. I choose the product bike and I say, I want to switch from the current time model to the express example. That’s the one we’ve just edited. I click save so all open orders are actually converted. So if we have a look at these orders now, we see, that these times changed.

So to pick up time is now to pick up is between 16:30 and 17:05 and 16:40 and 17:30. And you see the whole is exactly one hour. That’s the minimum we’ve set. Okay. But why is this so essential? Actually, it’s essential because we want to order these jobs so that the ones that need the most attention are on the top.

Well, I mean, that’s quite obvious, if you just enter a job after another, because then the time of entering defines the time of the order. But let’s have a closer look on this example here. I created two orders from Actris to Pro Velo. And let’s see this one has a reference time of 16:30. So we just assume that this was, It’s generated at 16:30 and has a lead time of two hours and that has exact, no, it hasn’t simply adapted.

So this has not the same reference time and same lead time. So actually they are displayed beside each other. And of course, as they are the same, they also have the same timeline. But now I want to manually set the time in this here. So initially it was this time. But let’s assume that the customer asked that this is that this is delivered between 16:30 and 17:00. So it’s a more restrictive time window. And what we see is that Lobo automatically adapts the reference time. So it’s from 16:30 it moves back to 16:03. And we can’t change the reference time anymore because we’ve already defined a time window. Why is that? Because what you’re gonna see is, if I save the job, it automatically moves to the top, because Lobo says to be there until 5 o’clock.

You need to go there. So as soon as you set any time window, Lobo calculates back from every time window to the start and calculates a virtual reference time when you should have started so that you can make this job. This leads that the order of all the jobs are like the most, the ones that need the most attention, are on top.

But if you’ve played around with global, you might have noticed that you can move jobs by drag and drop here. So actually what happens here, if I move them around because these times don’t change. So as soon as I move a job back and forth, I do nothing else. But changing the pre display time. At the moment it’s 1 hour and 45 minutes. And if I move this order down here, I will see it has now a small leading time. Or if I increase the lead time, I automatically decrease the display time, which will move this order up to the top because It gets somehow more important. So as soon as you move orders back and forth here by drag and drop, you do nothing else but changing the display time or actually the lead time but in the same time the time windows and the reference time stay the same so you don’t change the timing of a job. Well, that’s basically it.

Thanks for watching, Bye