Streamline delivery with Leafio Rinkai TMS – an efficient route planning system

let's get a quintant with the functionality and capabilities of Bai TMS system to do this let's build the test routs and then analyze their implementation first you need to download all your orders applications can be uploaded to the system using CSV files web service or excel in our case applications are already automatically uploaded to rinkai from the accountant system with the help of API integration each application has a number date name of the client weight and a third parameter in this case this is the quantity of pallets this is for orders moving from Warehouse to customer it is also possible to take into account orders that move in the opposite direction which we call returns return way and return third parameter are indicated for them one order can contain both parts as well or they can

be downloaded separately sequently according to orders we have a Time window which is characterized by either a whole range as in this example from 600 to 800 a.m. or a range which consist of two time windows in the case if the client has lunchtime for instance Suppose there is a break from 4 to 1430 visually we see that the windows are different it's like a gun chart it shows how many different windows are taken into account and the system is obliged to take this into account as a limitation while planning for each order the time required for loading a given volume and weight in the warehouse as well as unloading at the client is automatically calculated the larger the weight and size characteristics of the order the more time the system takes as administrative time all estimations depend on the Ed

statistics let's take a look into a type of vehicles that will deliver orders by editing one vehicle we can see all parameters that are taken into account while the system chooses the cheapest vehicle to deliver your orders in the basic parameter we can see a code and state number code is necessary for synchronization with the accounting system so that it also understands what kind of car it is you can select a carea directory in this case two are entered but there might be more note that this car belongs to the own Fleet select a driver from the directory you can also set the GPS data source for the car from where we will receive actual data on how the car completed the route this can be our rense app or it could be a stationary tracking system like stationary GPS trackers or those

that plug into the cigarette lighter also you can see here the vehicle's availability parameters that is available or unavailable from what time and until what time we can use this card in addition there are various parameters character horiz in which L of roads this car can drive there are different car profiles light medium heavy in this case the car belongs to the pedium group this determines the roads that are available to it taken into account the weight and the size characteristics and restrictions on the map so the vehicle will not go where it cannot pass according to the road signs then there is the gross weight of the car that is the total curb weight the carrying capacity itself the volume and various limitations for loading the car by weight volume and the third parameter let's say we want to let the system know that loading a vehicle by

110% is fine the system will use this information as a gap to load this car more than others if necessary let's move on to another parameter such as time availability in the KTMs system it is possible to limit or set Brakes in the use of the vehicle drivein and also set certain speed indicators for the speed of movement Depot loading and customer unloading time which are specific to the particular vehicle therefore for this the current tab with the settings is used one of the main tabs on the profile of the vehicle is the costs for each car this is the cost metrix associated with the use of this car for instance there is a daily expense a mileage cost and an hour charge for each driver summarizing these indicators according to the parameters of the route

we can calculate the total cost of all logistic expenses moreover the system takes into account all entered parameters at the same time it can also be cost for a visit to a point cost for delivery of one unit of weight volume possibly some third parameter similarly the opportunity cost of weight volume and third parameter of return orders depending on how the cost Matrix is configured for each car the system with the same parameters of load capacity Etc chooses the cheapest the vehicle to deliver all your chosen orders the last but not least parameter of the vehicle is the driver's contact information this includes contact information which can then be transmitted to customers in messages indicating the contact details of the driver of the car and so on in particular it may be taken into account

that the car doesn't start from the warehouse but starts from a certain site visits or doesn't visit the warehouse before going on the road similarly returning to the parking lot with the visit or not visiting the warehouse before parking we have delivery points that are characterized by a code we synchronize with the accounting system the client's name address geo coordinates Standard Time window as well as waiting time if this is expected also it is necessary to take into account the capabilities of the Depots this is the productivity scale schedule that the warehouse can provide us with over a period of time simply it just shows what is the maximum number of cars that can be loaded or unloaded at the same time in this example we see that the warehouse works from 12: a.m. to 10:30

a.m. from 12 a.m. to 4:30 a.m. 3 Vehicles can be loaded in the Depot at the same time this is a specified maximum then the productivity decreases to two vehicles an important task is to take into account specifically this decrease in productivity and not to plan more routs during this period than the warehouse can release and finally we are moving onto the magic of planning to begin with we need to select all orders and press the apply button we get to the planning tab the interface of the planning window contains the following objects this is a map with delivery points on it the list of vehicles available for planning with different load capacities and volumes schedule of composition capabilities a list of unplaned stops click

optimize the system begins to select a list of roots a combination of delivery points which on the one hand ensures that we comply with all previously introduced restrictions and on the other hand shows the amount of costs required for the delivery of orders with the available resources in the form of Transport all costs are taken into account that correspond to this machine and as soon as the system finds a more profitable solution from the point of view of saving money we immediately see a decrease in the total cost of logistic expenses for each of the routs we see the selected vehicle the total number of steps the start and end time of the route the time of use of the given car as well as the driving time that the driver must spend below we can see the sequence of points that must be visited in order to deliver all orders within

this route as you can see for each delivery points the time of arrival at it the duration of unloading is taken into account and the time of departure is also known visually here we see time windows and a red line which visualizes the time at which the car will be in the delivery point The Wider this red line is the more time the car spends at the delivery point in this example we said that when shipping and order weit in 21 kg the vehicle spends about 6 minutes at the client's location we can see the same route on the map you should just click view as you can see now we can visually see the roads along which the delivery is carried out within the framework of this route and the sequence Roots can be switched and viewed without returning to the main interface at the same time as part of

the rout and road construction the system takes into account the road Network the speed map which is collected from the statistic iCal data the faster this road is the more likely it is that the system will route along it also K takes into account the restrictions placed on the map for example in this case we can see how many restrictions are used these include weight restrictions road closures for certain types of transport Manu closures and so on that is a very large list of cargraphic data that must be taken into account when building a route so the warehouse capacity is filled behind the Cars on the gun chart we can see how many routs are expected for each vehicle when they start when they end the map is interactive and we can go to one or another route we are interested in by double clicking also the system has filled the productivity of the warehouse

and their disposal that is we have read areas that visualize how many cars will be loaded in the warehouse at a particular moment in time here it's necessary to pay attention to the fact that the schedule of possibilities is exactly followed as we said that is when the warehouse has resources the system plans a car for loading but there are no resources the system doesn't put them there after the roots are planned we export them to the accounted system using the same CSV protocols or web service in this case we will use CSV it is necessary to enter the name of the root plan for example test indicate the delivery date in our case March 8th and click okay the roof plan is saved blocked and it briefly reflects all those characteristics that correspond to it