Based on transport orders and vehicle/facility information, we connect dispatch plans, transportation execution, and performance/settlement information. We design the scope of connection between optimization engine, control, mobile, and existing business systems.
Based on the functions provided by TMS, we discuss the scope of connection and advancement for each customer.
We build a transportation management system centered on order registration, transportation execution order management, dispatch planning and processing, operation logs, and freight billing. We design the range of connection with the optimized engine and field systems together.
It connects ERP/OMS orders, vehicle/driver/location information, on-site mobile, and freight/settlement systems. Processing responsibilities and interfaces are defined according to customer tasks.
Expansion tasks such as transportation and delivery division, real-time re-vehicle relocation, facility change, and vehicle configuration simulation are reviewed based on construction cases, application versions, and data and connection conditions.
Currently, we provide an illustrative workflow. The actual work system experience will be released after connection and verification in a separate environment.
TMS Experience Guide ↗The provided modules, applicable versions, data/interfaces, and construction scope for each customer are confirmed during introduction consultation.
TMS connects received orders to transportation execution orders and dispatch plans, and manages everything from dispatch processing to operation records and fare settlement. We introduce the flow with an actual work screen that retrieves data from November 2016 and March 2019 stored in the development environment.
Confirm center, shipper, origin and destination, order and product details.
Review undispatched orders and link dispatch plans with transportation request and approval procedures.
Check the transport order, dispatch number, status, return, hold, and POD information.
Check the delivery tally in the operation log and the cost and deadline items in the freight claim.
Basis: Direct confirmation of order registration, dispatch plan establishment, dispatch processing, transportation execution order management, operation log, and freight billing screen in the GLT TMS development environment on October 26, 2026, G-TO·TMS Introduction (October 2025), pages 4~5·22~26·29~41. The dispatch plan establishment, dispatch processing, and voucher processing screen that confirmed the inquiry data in November 2016 is used as a public example. Order registration and transportation execution order management looked up data from March 2019, and delivery order conditions were selected in transportation execution order management. Individually provided functions and screens are checked according to the applicable version, contract, and scope of connection.
There are four steps to receiving an order, reviewing dispatch, and checking transportation status, performance, and settlement. We have organized the role of each screen and the information leading to the next task.
Search data from November 2016 and March 2019; Personal and transaction identification information obscured
This is an actual work screen that searches the saved data of the development environment on October 26, 2026. Each screen describes the workflow with data stored at different times and does not represent the entire process of the same order or current operating performance. Screens and provided functions may vary depending on the applicable version and deployment scope.
What needs to be transported where and how much?
We organize the order information required for transportation, including center, shipper, origin and destination, and quantity, weight, and volume for each product. On the order registration screen, check the date, delivery type, and transportation status of the received order and the product details of the selected order.
View larger screen ↗Original Korean source material. See the English explanation on this page.
next stepsThe received order is subject to transportation execution order and dispatch review.
What orders are dispatched together and how do they get executed?
In the dispatch plan establishment, the undispatched order/plan ID and product details are confirmed, and in the dispatch processing, transportation requests/approval by dispatch number and management of execution orders and stops are performed.
View larger screen ↗Original Korean source material. See the English explanation on this page.
View larger screen ↗Original Korean source material. See the English explanation on this page.
next stepsCheck the transportation status by linking the confirmed dispatch and execution order.
To which dispatch is the order placed?
In Transportation Execution Order Management, check the transport order linked to the received order. We review follow-up work by dividing each order into dispatch number, POD number, processing status, and return, direct delivery, urgent, and pending items.
View larger screen ↗Original Korean source material. See the English explanation on this page.
next stepsWe then proceed to verify the information needed to review your driving record and transportation claim.
How do I check the results of my trip and how much transportation I will be charged?
Link your driving records and fare information to review the items required for settlement. On the voucher processing screen, you can check the status of the voucher and billed fare for each distribution, whether it is closed, and the fare account and cost calculation items.
View larger screen ↗Original Korean source material. See the English explanation on this page.
Work useOperation and costs are reviewed together and used as a basis for settlement and follow-up work.
From data preparation to existing system connection, result review and introduction procedures. This is a frequently asked question when determining the right coverage for your business.
TMS introduction consultation ↗The construction scope can be designed based on the premise of linking with the existing system. Determine the transmission/reception items of orders, standard information, performance, and freight, data management entity and processing time, and check the interface.
System connection and construction proceduresOrder, shipper, facility, vehicle, carrier, freight rate standards and current dispatch, transportation, and settlement procedures are summarized. Check the time of status change, responsible authority, and data to be exchanged and received from the existing system.
Check flow with actual work screenIt is possible. Review the dispatch plan and optimization results according to the task, and determine the confirmation, transportation request, and approval procedures for the person in charge. The supported version and linkage range of the optimization engine are checked at the construction stage.
Actual screen of dispatch plan and dispatch processingIt is checked based on the undispatched orders in dispatch plan establishment and the undispatched conditions in transportation execution order management. After checking order status, vehicle, and site constraints, the person in charge reviews dispatch or replan targets.
Transportation execution order and status confirmation screenFor control and mobile, the connection range is determined and applied for each customer. After confirming the location collection method, on-site status update method, and information and processing responsibilities to be delivered to the technician, the scope of construction is confirmed.
Scope of connection with field systemsOn the freight claim screen, check the basic transportation cost by dispatch, vehicle, and transportation company, the total billing fee, and whether it is closed. The actual settlement rules and items to be delivered to the ERP/accounting system are determined according to the customer's business.
Fare status/settlement preparation screenWe verify the flow from order reception to dispatch, transportation, and settlement using representative orders and exceptional situations. We check standard information, transfer data, connection error handling, and responsible authority, and discuss training, pilot, and operational transition standards.
Verification, training, and operation transition proceduresIt varies depending on applicable modules such as ordering, dispatch, control, and settlement, number and method of linked systems, data transfer, on-site mobile, and customer-specific business rules. After checking the data and confirming the scope, we will inform you of the schedule and cost.
TMS implementation scope consultationPlease let us know what parts of the system you would like to maintain and what tasks you would like to change. Review the scope of connection between order, dispatch, transportation status, performance, and settlement.
Please choose a situation that is close to our company.
Even if you don't have any data yet, you can tell us about your current situation. Information that is difficult to disclose may be reviewed as a sample with identifying information masked.
GLT contracted directly with the customer and independently delivered detailed design, development, testing and go-live for this DC-level CPFR and Reverse PO project. See how DC demand and inventory inform ordering and shipment plans, with targets and expected benefits clearly identified.
Learn More ↗A case combining fixed pickup territories and updating routes for additional orders. Distance and time are compared using the same stop count, alongside the replanning workflow.
Learn More ↗A fleet planning case comparing daily orders and vehicle costs to evaluate the mix of dedicated and hired vehicles. The source describes the 30-day simulation assumptions and recommended fleet size.
Learn More ↗A case from GLT’s solution materials comparing each facility’s volume, capacity, storage and transport costs while reallocating territories around a new CDC.
Learn More ↗Explore GLT’s participation in intelligent logistics for the Ministry of the Interior and Safety’s integrated disaster resource management system, including the scope of WMS, TMS and dispatch optimization.
Learn More ↗Five synthetic JSON examples and a reading guide for transport orders, vehicles, facilities, dispatch policies and reference master data.
Learn More ↗A 44-slide PowerPoint covering TMS project experience, optimization functions, transport and network simulation, and screenshots of earlier implementations.
Learn More ↗An 85-page PDF introducing G-TO’s TO, NO, Route and Load Build functions, application architecture and GLT project examples.
Learn More ↗The deliverables and factors that shape schedule and cost at each stage: data review, comparative validation, system integration and operational rollout.
Learn More ↗Based on POL-TMS-020, this guide distinguishes optimization order attributes, vehicle and facility master data, and dispatch policies, with practical data checks.
Learn More ↗Understand the roles of NO, TO and TMS, and how to prepare order, delivery point, vehicle and transport requirement data before implementing dispatch optimization.
Learn More ↗
