2. Materials and Methods
A logistics company was interviewed to validate the pain points identified in the previous chapter in the context of dispatch management and to get insights about the proposed framework to be discussed further in section 2.2. A dispatch management software application was then developed using Android Studio as an Integrated Development Environment (IDE), Flutter as the UI Software Development Kit (SDK), Dart as the primary programming language, and powered by Google APIs such as Maps, Places, Directions, and Firebase Cloud Messaging. The final prototype was tested, and its performance results were compared with the traditional approach of the identified logistics company in dispatch management. Shown in
Figure 1 is the visualization of each user role in the software application.
2.1. Current Method Used by the Partner Logistics Company
The traditional return trip and last-mile delivery transactions of most logistics companies like 5RJS Lanuza Logistics Corp. are made through calls, Short Message Service (SMS), and/or emails from customers. First, the customer directly contacts a 3PL via phone to schedule a delivery of their goods. The dispatcher from the 3PL then schedules a vehicle and driver to send off the product/s by batch to the respective end customer’s location. After successful delivery of all the assigned orders, the vehicle usually returns to its origin point with empty or unused space. In the case of return trips, the customer contacts the dispatcher again, requesting a new schedule for the transportation of goods from the destination back to the sending vehicle’s origin. The current method has its limitations and challenges in establishing effective communication, coordination, and scheduling resulting to inefficiencies and missed opportunities especially in terms of optimizing delivery routes and use of carrier space. Additionally, transactions made via phone calls, SMS and emails are difficult to track, posing further issues in managing logistics processes.
The old framework shown in
Figure 2 yields higher turnaround time and lower concurrent order processing. Using phone calls limits single customer transaction at a time usually ranging few minutes to an hour duration, depending on the concern of the customer. The existing setup of the corporation is as follows:
For the customer, the only way to get a delivery order is to inquire to the company through phone calls or SMS. High call waiting time is a common problem when there are simultaneous requests from multiple customers. If an inbound call gets through, a CSR is assigned to interact and maintain a good relationship with the customers. They answer customer concerns, relay messages to and from the management, provide service information, and monitor the capacity of trucks to handle a given number of deliveries. All these are crucial in maintaining a good business image to customers. Next, the dispatchers are designated to interact with the drivers by assigning the delivery requests to the available drivers, monitoring the progress of deliveries, and relaying the routes/paths that should be taken by the drivers. Fleet tracking is done using a whiteboard only. This is prone to inconsistencies and is difficult to sustain especially when the business is expanding. On the driver’s side, they get a call from the dispatcher when there is an accepted delivery order whether it is a last-mile or a return trip delivery.
2.2. Proposed GIS Framework
There are a total of four roles (see
Table 1) in the software level, namely, administrator, dispatcher, customer, and driver. The customer is the one who requests the trips and monitors the progress of their delivery requests. Next, the dispatcher will either accept or decline the delivery requests, depending on the availability of vehicles and drivers. After that, the dispatcher will also be responsible for accepting and assigning the requests to the available drivers which he/she will also monitor. Then, the driver will either accept or decline the delivery requests depending on their condition and update their progress while delivering the goods. Lastly, the administrator has the same responsibilities as the dispatcher but has additional ones, specifically retrieving, updating, and deleting user accounts existing in the application software.
The proposed improvement on the framework of the 5RJSL Lanuza Logistics Corp. is shown in
Figure 3. It utilizes mobile application and GIS-driven algorithms at the back end to improve their business response times and increase the number of concurrent customers they can handle. With the new framework, customers will be able to keep on sending their orders through the application software and just wait for an acceptance notification instead of dialing in numerous times. While still having the option to use SMS/call/email to inquire about concerns, special deliveries, etc. Next, the customer service representative may answer special concerns through SMS, calls, and e-mails. Then, the dispatcher can handle multiple orders at the same time as long as there are available trucks for delivery. The dispatcher is also responsible for assigning driver trips, including return trips through the application software, managing the truck fleet using the dashboard, and real-time monitoring of the trucks and customer orders. Lastly, the truck driver can also update the dispatcher regarding its delivery and availability status much more quickly instead of calling back to the dispatcher. They can also accept/reject customer orders just in case the driver needs to go home early or has health problems that he needs to attend to.
To optimize the trip of a driver, the application software suggests a route plan based on various input parameters such as vehicle type, shipment locations, defined constraints, and vehicle cost parameters. The constraints include driver working hours, vehicle capacity, and window hour. This is done through the waypoint order optimization algorithm wherein a vehicle is assigned with cost per hour, per kilometer, and per traveled hour parameters. The pseudocode representation of the algorithm is as follows:
request.truck[0].startLocation -> transitions[0] -> visits[0] ->
transitions[1] -> visits[1] -> transitions[2] -> ... -> visits[n] ->
transitions[n] -> request.truck[0].endLocation.
The startLocation and endLocation represent the origin and return point of a truck respectively after all orders have been shipped to the corresponding end customer location. Based on the GPS locations of pickup/delivery points, the order of waypoint is arranged to achieve minimum travel hour and distance costs. These costs are extracted using the Distance Matrix and Directions API of Google. Transition is tagged between the truck’s current location and the next location to visit. Upon completion of a pickup or delivery, it is tagged as visit. This represents as an assigned work that a truck needs to complete at the requested place and time. To aid the driver in visualizing the path per visit, the interactive polyline encoder utility of Google was used.
Utilizing the GIS framework can sustain logistics operations with its combined workload management tool and shipment route optimization to increase time efficiency, cost savings, customer/driver satisfaction, and environmental friendliness through the reduced carbon emission despite being in the transportation sector as well.
2.3. Roles and User Access in the Application Software
The roles and capabilities of the application software are shown in
Table 1. The admin has the capability of a dispatcher plus the capability to view, update, block/unblock, and delete the details of the users in the database.
2.4. Dataflow in the GIS Framework
Figure 4 shows the data flow diagram of the application software. In this figure, the interaction between the database, APIs, different variables, and user data is illustrated. The data starts from the creation of users and drivers in the application. At first, the user will input their details such as email address, username, phone number, and password, and the driver will input the details mentioned earlier in addition to car details such as plate number, model, and their own picture so that the admin and dispatcher can further validate the legitimacy and identify more easily in the system once recorded in the database. The Mapping and Database module houses the algorithms and core GIS which is the key contribution and difference of the proposed study as compared to existing dispatch management applications.
2.5. Data Collection Methods
The researchers decided to replicate a normal trip of a 4-wheeler vehicle of the partner logistics company. The scenario is that there are six different customers, each booked a distinct pick-up location while Mega Pacific Freight Logistics, Inc. is the only starting and drop-off location. The order of then accepted customer requests and pick-up locations of the said requests are: 1) University Pad Residences Taft, 2) Vista GL Taft by Vista Residences, 3) Robinsons Place Manila, 4) Adamson University Main Building, 5) SM Mall of Asia, and 6) SM City Bicutan.
Data gathering is divided into three parts. In the first part, the researchers followed the order of the customer requests and did not use the application software or any navigation applications. They only followed the traditional approach which only relied on spatial awareness and following the signages. The second part is where the researchers used the software application, which organizes the route for the driver. This modifies the order of pick-up locations. The elapsed time, distance traveled, and fuel expenses were recorded, and the corresponding carbon footprint and projected profits were measured for the first two parts. It should be noted that due to time constraints, the researchers started outside the Br. Andrew Gonzales Hall in the actual testing for both the traditional and the proposed GIS framework, instead of Mega Pacific Logistics, Inc. The deviation in time and distance projected by Google Maps were added in the final results. In the last part of the data gathering, the researchers demonstrated the software application to several employees of the partner logistics company and distributed a survey about user acceptance to them.
2.6. Freight Rate Matrix Provided by the Partner Logistics Company
The rate matrix provided by the partner logistics company is summarized in
Table 2. This was used by the researchers to generate the projected profits for testing using the current dispatch method. Another factor measured was the fuel costs per trip. To compute the fuel costs incurred in the traditional method, the researchers followed the values of fuel efficiency and fuel price set by the partner logistics company. According to R.J. Lanuza in a personal interview on February 19, 2024, the company currently follows the fuel efficiency set to 8 km/L and the fuel price set to ₱65.00/L in computing the fuel costs which is necessary for generating the rates.
2.7. Freight Rate Matrix Provided by the Researchers
Table 3 shows rate matrix proposed by the researchers. This was used to generate the projected profits for testing the dispatch performance using the proposed framework. The rate matrix provided by the partner logistics company caters for regular trips, which makes the rates significantly higher since it is based on two-way trips (origin to destination and vice versa). Because of this, the drivers and helpers might also earn more for a minimal effort because they can earn a minimum of Php 550.00 and Php 405, respectively each trip even if one pick-up location is very near to the next one. More established logistics companies implement a base fare on every trip and add a fee for every kilometer traveled on the way to the destination [
39]. This makes it fair not only for the customers but also for the admin and other employees of the company. Because of this, the rate for drivers and helpers was adjusted accordingly.
First, the rate matrix still follows the fuel efficiency rate of 8 km/L and the fuel price of Php 65.00/L in calculating the fuel consumption. The formula for the fuel consumption cost is:
Next, the calculation of maintenance cost, along with driver and helper rate was based on the advice of the consultant. For maintenance costs, it was set at 5% of the final rate. As for driver and helper rates, according to R.J. Lanuza in a personal interview on March 7, 2024, the usual practice in these kinds of trips is that drivers receive 10% of the final rate while helpers receive 5% of the final rate for their respective compensations.
As mentioned above, the implementation of the base fare and additional fee for every kilometer traveled is beneficial for all of the stakeholders, especially in the context of the return trips. For 4-wheeler vehicles, the researchers set the base fare to Php 650.00 while the fee for every kilometer traveled is set to Php 55.00. Lastly, the final rate is the sum of the base fare and additional fee for every kilometer traveled while the profit is the difference between the final rate and expenses.