Solution/TOTO / Transportation Optimization

Complex transport requirements.
Actionable dispatch plans.

Based on orders, vehicles, facilities, and operational constraints, we construct dispatch and route plans for each Load, Stop, and Shipment. It can be used independently from TMS, and provides guidance on expanded application ranges such as vehicle configuration and rearrangement vehicles.

Concept image where transport orders are grouped into vehicle-specific plans, leading to different delivery routes and change routes.
Create a dispatch and route plan by linking orders and vehicle conditions, and review the scope of adjustment for changes in the field.Concept image for understanding functionality · This is not an actual product screen or calculation result.
TO / AVAILABILITY & INTEGRATION

Check the status of introduced features and experiences.

Based on the TO's provided functions, we discuss the scope of connection and advancement for each customer.

Features currently available

It provides vehicle-specific assignment of transport orders, route optimization, master-based load build, use of fixed route and dispatch history, and scenario storage and comparison.

Customer-specific linkage functions

Connects ERP/TMS orders, vehicles, freight, and distance with on-site progress. Optimization plan confirmed, mobile delivery of articles and real-time redistribution coverage are designed according to each customer's data and business procedures.

Advanced review function

Active vehicle matching, multi-dimensional compartment and specialized loading calculations, and AI-based initial planning and constraint verification are reviewed for application by checking separate data and support versions.

Experience public status

Sandbox in Preparation

Target: ready during November 2026

Currently, we provide scenarios for illustrative purposes only. The actual NO·TO engine experience will be released after connection and verification are completed.

TO Experience Information ↗

The provided modules, applicable versions, data/interfaces, and construction scope for each customer are confirmed during introduction consultation.

TO / WORKFLOW & SCOPE

What input does TO receive and what does it connect to?

The basis of TO is to organize orders into transport bundles (Load) and visit order (Stop) for each vehicle. Select the standard master, history, and fixed route methods presented in the introduction to suit your work and compare the results.

  1. 01input

    Transportation order, loading/unloading time window, weight/volume/quantity and unit, available vehicles, facility and distance/freight

  2. 02Constraint settings

    Objective function, vehicle capacity, stopping point/distance/operation time, entry/exit/return conditions

  3. 03Calculate and Review

    Plan, guidance, and result report by Load·Stop·Shipment, check non-assignment and restrictions

  4. 04run connection

    After confirming the plan, transfer it to operating systems such as TMS and mobile

Basis: G-TO Introduction (2026) pages 29-37, G-TO·TMS Introduction (2025.10) pages 29-37·42, POL-TMS-020 input reference policy. Individually provided functions and screens are checked according to the applicable version, contract, and scope of connection.

Construction screen included in the introduction material

Daily vehicle and dispatch simulation results screen on page 37 of the G-TO introduction (October 2025). Differentiate the data on the screen and vehicle configuration from the recommended values ​​in the example below.
Daily vehicle and dispatch simulation results screen on page 37 of the G-TO introduction (October 2025). Differentiate the data on the screen and vehicle configuration from the recommended values ​​in the example below. Click on the image to see it larger.

Original Korean source material. See the English explanation on this page.

UNDERSTAND TO

Can I use Transportation Optimization without implementing a TMS?

Yes. TO is a transportation optimization solution that can run independently of TMS. Dispatch and route plans are reviewed based on orders, vehicles, and operating conditions, and operational information such as execution status, driver acceptance, and fares together define the scope of connection with TMS or related systems.

Automatically optimized dispatchvehicle resourcesMatching and cultivation teafixed routestandalone execution
NO Network Optimization See also ↗
FUNCTIONS & APPLICATION

Six areas of connection and expansion to expand transportation operations.

Vehicle configuration simulation and dynamic rearrangement are customer-specific expansion and linkage functions that have implementation examples. Advanced items such as matching, compartments, and AI combination undergo separate verification to confirm the scope of application.

Customer-specific expansion
Fleet Resource Simulator

Simulator for the appropriate number of fixed and stationary vehicles

This is an analysis that compares the composition ratio of fixed and temporary vehicles, the number of vehicles required by tonne class, and cost based on the past 1 to 3 years' cargo volume.

Applicable conditionsIn addition to dispatch calculations, operation history, fixed costs, unit price for rental vehicles, and repetitive simulation are required.

Upgrade review
Active Matching

Active vehicle matching

By reviewing cargo characteristics, vehicle location, past transportation performance, and preferred/return routes, we compare vehicle candidates with empty/return utilization opportunities.

Applicable conditionsLocation and transportation performance and driver acceptance history must be linked in operating systems such as TMS and information networks.

Customer-specific linkage
Re-planning

dynamic replanting

We review transportation plans to reflect changes such as new orders, cancellations, and delays in loading and unloading, and design ways to reduce the impact of changes to existing routes.

Applicable conditionsCollects the execution status and delay information of orders and vehicles and defines the allowable range of changes to confirmed and in-progress work.

Upgrade review
Compartment Optimization

Multidimensional compartment optimization

We review the scope of application that takes into account loading conditions such as temperature range, overall loading, compartment capacity, unloading sequence, and thermal expansion and axial load.

Applicable conditionsFor the scope where loading location, physical properties, and load calculations are required, consider combining them with specialized loading calculations.

Upgrade review
Route Master Optimization

Hapjim/route redesign based on fixed routes

We distinguish between optimizing the combination, dispatch, and time of designated routes and stopping patterns and redesigning areas, vehicle types, and vehicles based on past history.

Applicable conditionsDetermine the scope of analysis for regional design by comparing daily dispatch calculations with multi-day operation history.

Upgrade review
AI Based Optimization

AI-based pharmaceutical verification dispatch

We create an initial plan using past dispatch patterns and review a combination method that verifies the feasibility of executing constraints defined by Rule/Solver.

Applicable conditionsLearnable dispatch history, rules/masters, and verification standards are required, and decisions are made based on conditions defined in the data.

DATA & OUTPUT

What to prepare,
What results should we see?

These are the data and result items to prepare when negotiating the scope of analysis. Detailed fields, units, API specifications and support conditions are provided for each applicable version. We check customer-specific expansion and linkage conditions for vehicle configuration and rearrangement, and upgrade review conditions for matching, compartments, and AI combination.

Review data and result items by TO analysis area
analysis areareview dataResults to check
Basic transportation/dispatch planTransportation order, loading and unloading, vehicle information, operating conditionsReview criteria for order/vehicle allocation and route planning
Review of fixed and commercial vehicle composition1 to 3 years of cargo volume and dispatch history, vehicles by tonnage class, fixed costs and vehicle unit priceComparison of required number and cost by vehicle composition ratio and tonne class
Vehicle matching reviewCargo characteristics, vehicle location/transportation performance, preferred/return routes and acceptance historyComparison of vehicle candidates and possibility of use of empty and double trains
Review of re-car scopeRules for adding/cancelling orders, delays/vehicle status, confirming operations and allowing changesPlans/route subject to change and impact on existing transportation
Review of compartment and loading conditionsCompartment/vehicle specifications, product properties/temperature range, loading/unloading sequence and load conditionsCombined range of compartment/item allocation and specialized load calculations
Fixed route/area reviewDesignated route/stop pattern, order/operation history, vehicle type/vehicle informationHaengjim, dispatch, time alternatives and area, vehicle type, and number of redesign scope
Review of AI/Solver combinationHistorical dispatch data, initial plan, rule/constraint master and verification criteriaScope of use of initial planning and constraint verification results
Specifications to check upon introduction
  • Provided version of basic engine and advanced features
  • Linkage scope of TMS, information network, field app, and load calculation
  • Data/API specifications and processing scale/computation time
APPLICATION SCENARIOS

This is used for decision making.

Distributors/manufacturers with large volume fluctuations, 3PL/4PL/freight information network operators, same-day delivery/milk run/fixed circuit transport companies, and multi-temperature/compartment transport companies.

Example usage scenario

What if you look at the vehicle composition differently in peak season and off-season?

We review an analysis comparing the configuration alternatives of fixed and commercial vehicles in tasks with large volume fluctuations such as beverages, ice cream, and distribution.

Example usage scenario

How much will I have to change if there are additional orders or delays?

Considering ongoing work in same-day delivery, pickup, milk run, etc., determine the scope of need for redeployment and plan to maintain it.

Example usage scenario

What if the transport area and loading conditions are complex?

We design application plans by classifying constraints on combination of fixed circuit routes, area redesign, and multi-temperature/compartmental transportation by task.

NEXT STEP

It specifies the scope of application of our work.

  1. Check current assignmentsSummarize current operations, decisions to be made for improvement, and comparison criteria.
  2. Review data and support coverageCheck available data, product versions, and associated/extended functions.
  3. Establishment of verification and introduction planSpecify comparison conditions, result verification methods, and integration/construction scope.
TO introduction consultation ↗
TO / BEFORE YOU START

Before introducing TO
Please check any questions you may have.

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.

TO introduction consultation ↗
Can I just use TO without replacing my existing TMS?

Yes. TO can be used independently of TMS. In the existing system, orders, vehicles, and operating conditions are communicated, and who will confirm the calculation results and reflect them in the execution system is determined.

View existing systems and the role of optimization
What data do I need to start automatic dispatch?

Order loading and unloading locations, time window, quantity, weight, volume and units, and available vehicles and capacity are required. Site conditions such as entry restrictions, registration, and return are also organized, and required input values ​​are confirmed according to the application version and scope of work.

Information on order, master, and dispatch restrictions
Can we consider introducing it even if some of the data is lacking?

It is possible. We start by looking at the order, vehicle, and delivery address data we have, and determine the order of supplementing missing items that affect the results, such as address, loading unit, and time window. Set initial verification conditions based on data quality and availability.

Input data preparation example and checklist
What do I do with orders that are not assigned due to vehicle or time requirements?

Unassigned orders are separately checked and vehicle capacity, time window, entry, and loading conditions are checked. After reviewing the feasibility of adding additional vehicles or adjusting operating conditions, the representative compares alternatives as long as they remain within the required constraints.

Results comparison criteria including non-assignment and restrictions
Can you reschedule if there are additional orders or delays?

You can review the application of redistribution within the scope of each customer. First determine the progress status of orders and vehicles, the rules for allowing changes to confirmed work, and the scope of mobile delivery, and check the delivery version and on-site connection conditions.

Example of order addition and re-carry construction
How do you verify effectiveness before introduction?

Compare current plans and alternatives based on the same orders, available vehicles, constraints and costs. It checks not only distance, transportation cost, and number of vehicles, but also non-assignment and constraint fulfillment, and distinguishes between simulation results and actual operational performance.

Optimization comparison verification method
In what order is the introduction carried out, and what does the period and cost depend on?

The scope is determined in the following order: task definition → data check → comparative verification → necessary system connection → operation conversion. Schedule and cost are calculated based on order/vehicle size, complexity of constraints, and number of connections.

Introduction procedure and factors determining period and cost
Do I need to send the customer's actual order data from the first consultation?

Initially, please let us know the type of work, order/vehicle size, improvement tasks, and data items you possess. Verification using actual data is conducted after first discussing the scope of provision and use and delivery method.

TO introduction consultation
YOUR OPERATIONS / NEXT STEP

How do we apply dispatch and replanning to our work?

Please tell us about the most difficult situation in dispatch right now. We review the required data, site constraints, and scope of connection with existing systems.

Please choose a situation that is close to our company.

Having these materials will be helpful in your review.

  • Representative order/vehicle items
  • Operational restrictions such as delivery time and vehicle type
  • Current dispatch method and examples of changes

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.

In consultation, the scope is set as follows.

  1. Check current work and improvement goals
  2. Summary of data/constraints and comparative verification scope
  3. Link to existing systems and discuss scope of construction
Consult on our company’s assignments Apply without registering and select system/size input
STAY CONNECTED

Stay up to date with logistics.

Cases, product news and implementation guides for your interests. Subscribe with email verification and your consent.

Subscribe to GLT →
LET’S SOLVE IT TOGETHER

What logistics challenge
are you facing?

Talk to GLT ↗