Automotive & Discrete Manufacturing Inbound Milk-Run Governance: Multi-Stop Supplier Time-Window Slotting, 1:1 Returnable KLT/Pallet-Cage Swap Ledgers, and Dynamic Backhaul Cube Utilization

Executive Summary: Why Inbound Milk Runs Break Under Static Spreadsheet Routing

In direct LTL/FTL purchasing (Point-to-Point Supplier Shipping), each Tier-1 supplier ships their own half-empty truck to the OEM assembly plant (resulting in dock congestion, high freight embedded in unit piece prices, and 7–10 days of buffer inventory). To eliminate that waste, lean manufacturers run Inbound Milk Runs: a single OEM-controlled 53-foot or 13.6-meter curtain-side mega-trailer departs the assembly plant loaded with empty returnable containers (VDA-KLT plastic totes, foldable pallet sleeves, steel stillages) and visits 4 to 6 suppliers in a timed sequence—dropping off empty bins and picking up full Kanban lots on the same stop.

However, without real-time milk run logistics software, static milk runs suffer from three operational breakdowns:

1. The "Empty-Full Collision" Inside the Trailer (LDM Overflow at Stop 3): Because the truck carries both remaining empty returnable bins for Stops 4 and 5 and newly loaded full component bins from Stops 1, 2, and 3, if Supplier 2 ships +4 extra pallets while Supplier 3 fails to accept its scheduled 6 empty stillages, the trailer runs out of physical floor space (Loading Meters) at Stop 3—forcing the driver to leave critical JIT parts behind on the supplier's dock.
2. Unreconciled Returnable Container (RTI) Shrinkage ($500–$2,400 per Custom Stillage): Custom automotive component racks (e.g., painted bumper racks, engine-block dunnage trays, Euro-Gitterboxes) cost between $180 and $2,400 each. When drivers exchange empty racks for full racks using unsigned paper tally slips, suppliers hoard empty bins as internal WIP storage or dispute month-end container balances, forcing the OEM to halt production or buy emergency corrugated packaging.
3. Rigid Static Loops Despite Daily MRP / e-Kanban Demand Swings: On Tuesdays Supplier A may have 8 Loading Meters (LDM) of parts while Supplier B has 2 LDM; on Thursdays Supplier A has 3 LDM and Supplier B has 7 LDM. Running fixed static truck assignments either leaves trucks 35% empty or triggers expensive ad-hoc expedited hot-shot vans.

Technical Architecture: Dynamic CVRPTW Solver, 1:1 RTI Swap Gate, and VDA 4987 ASN Engine

Mathematical Foundation: Simultaneous Pickup-and-Delivery LDM Constraints & RTI Balance

1. Simultaneous Pickup-and-Delivery Loading-Meter (LDM) Feasibility Constraint

Unlike standard delivery routing (where truck load decreases monotonically across stops) or pure collection routing (where load increases monotonically), an inbound milk run is a Vehicle Routing Problem with Simultaneous Pickup and Delivery and Time Windows (VRPSPDTW).

For a trailer of usable deck length $L_{\text{max}} = 13.60\text{ Loading Meters (LDM)}$ (where $1.0\text{ LDM} = 1.0\text{ m}$ of trailer length across the standard $2.44\text{ m}$ width; e.g., two standard $1200 \times 800\text{ mm}$ Euro-pallets or $1200 \times 1000\text{ mm}$ industrial cages side-by-side divided by their stackability factor $s_i \in {1, 2, 3, 4}$) visiting ordered supplier stops $k \in {1, 2, \dots, m}$:

• Let $E_{\text{drop}}(k)$ be the Loading Meters (LDM) of empty returnable containers dropped off at Supplier $k$.
• Let $F_{\text{pick}}(k)$ be the Loading Meters (LDM) of full component containers picked up at Supplier $k$.

The trailer departs the OEM plant ($k = 0$) carrying total empty container volume $Q_0 = \sum_{j=1}^{m} E_{\text{drop}}(j)$. After completing Stop $k$ (and while traveling on leg $k \to k+1$), the Simultaneous Occupied Floor-Space ($Q_k$ in LDM) and Gross Payload Weight ($W_k$ in kg) must satisfy at every intermediate leg $k \in {0, 1, \dots, m}$:

$$Q_k = \underbrace{\sum_{j=k+1}^{m} E_{\text{drop}}(j)}{\text{Remaining Empty RTIs}} + \underbrace{\sum{j=1}^{k} F_{\text{pick}}(j)}{\text{Picked-Up Full Goods}} \le L{\text{max}} \quad (13.60\text{ LDM})$$

$$W_k = \sum_{j=k+1}^{m} W_{\text{empty}}(j) + \sum_{j=1}^{k} W_{\text{full}}(j) \le W_{\text{max_payload}} \quad (24,000\text{ kg})$$

Notice that even if $E_{\text{drop}}(k) = F_{\text{pick}}(k)$ in container units (1:1 swap), if the empty containers are collapsible/foldable sleeve packs (4:1 folded nesting ratio) while the full containers are rigid stackable 2-high cages, $Q_k$ increases at every stop ($F_{\text{pick}}(k) > E_{\text{drop}}(k)$ in LDM). Conversely, if non-collapsible rigid racks are dropped off at Stop 1 while compact KLT boxes are picked up, $Q_k$ peaks at $k = 0$. Checking $Q_k \le 13.60\text{ LDM}$ at every stop $k$ is mandatory to prevent mid-route trailer overflow.

2. Supplier Time-Window & Line-Side Stockout Risk Function

Each supplier stop $k$ has a contracted dock window $[a_k, b_k]$ (e.g., 09:30 to 10:00) and handling duration $\tau_k = \tau_{\text{dock}} + \alpha_{\text{scan}} \left(N_{\text{empty},k} + N_{\text{full},k}\right)$. Arrival time $T_k$ at stop $k$ follows:

$$T_{k} = \max\left(T_{k-1} + \tau_{k-1} + t_{\text{travel}}(k-1, k), ; a_k\right), \quad \text{subject to } T_k \le b_k$$

3. Perpetual Returnable Transport Item (RTI) Custodial Ledger (VDA 4927)

For each supplier $s$ and container type $c$ (e.g., VDA-RL-KLT-6429, GITTERBOX-DB-UIC, RACK-ENG-B48), the perpetual custodial balance $B_{\text{RTI}}(s, c, t)$ held at the supplier's premises at time $t$ is updated atomically upon dual driver-and-supplier mobile sign-off:

$$B_{\text{RTI}}(s, c, t) = B_{\text{RTI}}(s, c, t_0) + \sum_{\tau \in (t_0, t]} N_{\text{empty_dropped}}(s, c, \tau) - \sum_{\tau \in (t_0, t]} N_{\text{full_picked}}(s, c, \tau) - N_{\text{damaged_scrap}}(s, c, t)$$

If $B_{\text{RTI}}(s, c, t)$ falls below the supplier's Minimum 48-Hour Packaging Float ($F_{\min}(s, c)$), the plant depot automatically adds supplemental empty bins to the next milk run; if physical cycle count at the supplier reveals $B_{\text{physical}}(s, c) < B_{\text{RTI}}(s, c, t)$, the deficit is invoiced to the supplier at replacement cost.

Worked Numerical Example: 4-Supplier Powertrain Milk-Run Loop (Route MR-NORTH-04)

Consider Route MR-NORTH-04, a daily morning milk run using a 13.60 LDM (24,000 kg payload) mega-curtainsider trailer serving 4 Tier-1 suppliers over a 185 km loop back to the OEM Assembly Plant (PLANT-PUNE-01):

• Container Stackability Rules:
  • Rigid Steel Gitterboxes (1240 x 835 x 970 mm): Stacked 3-high inside the 3.0m internal-height mega-trailer (both empty and full) $\implies 6\text{ Gitterboxes occupy } 0.80\text{ LDM}$ ($0.1333\text{ LDM/box}$).
  • Foldable Pallet Sleeve-Packs (1200 x 1000 mm): Folded 5-high when empty ($10\text{ empty sleeve-packs} = 1.00\text{ LDM}$); stacked 2-high when full ($4\text{ full sleeve-packs} = 1.00\text{ LDM}$, i.e., $0.25\text{ LDM/full pack}$).

Stop-by-Stop Simultaneous LDM & Weight Evolution (Table 1)

VDA 4987 / Milk-Run Stop Manifest & 1:1 RTI Swap Ledger JSON

{
  "milkRunStopExecutionRecord": {
    "milkRunTripId": "MR-NORTH-04-20261020-AM",
    "trailerId": "MEGA-TRL-136-09",
    "maxLoadingMeters": 13.60,
    "maxPayloadKg": 24000,
    "stopSequenceNumber": 2,
    "supplierId": "SUP-HARNESS-B02",
    "contractedWindow": {
      "earliestArrivalLocal": "2026-10-20T08:30:00+05:30",
      "latestDepartureLocal": "2026-10-20T09:00:00+05:30",
      "actualArrivalGeofenceLocal": "2026-10-20T08:28:14+05:30",
      "actualDepartureGeofenceLocal": "2026-10-20T08:54:40+05:30",
      "windowComplianceStatus": "ON_TIME_PASS"
    },
    "rtiEmptyDropTransaction": {
      "rtiContainerCode": "SLEEVE-PACK-1210-FOLD",
      "scheduledDropQty": 20,
      "actualScannedDropQty": 20,
      "freedTrailerLdm": 2.00,
      "supplierOpeningRtiBalance": 44,
      "supplierPostDropRtiBalance": 64
    },
    "fullGoodsPickupTransaction": {
      "vda4987DesadvNumber": "ASN-B02-2026-99104",
      "handlingUnitsScannedQty": 16,
      "occupiedTrailerLdm": 4.00,
      "grossPickupWeightKg": 3520,
      "supplierClosingRtiBalance": 48,
      "departingTrailerState": {
        "remainingEmptyRtiLdm": 3.80,
        "cumulativeFullGoodsLdm": 7.20,
        "totalOccupiedLdm": 11.00,
        "remainingAvailableLdm": 2.60,
        "totalPayloadKg": 12760
      }
    }
  }
}

Verification & Acceptance Playbook (ACT-L162)

1. ACT-L162-01 — Mid-Route Simultaneous Empty + Full LDM Overflow Prevention:
   • Scenario: At T-12h call-off confirmation on Route MR-NORTH-04, Supplier B (Stop 2) attempts to book 28 full non-collapsible sleeve-packs (7.00 LDM instead of 4.00 LDM), which would push total occupied deck space at Stop 2 (3.80 LDM remaining empties for Stops 3–4 + 3.20 LDM Stop 1 fulls + 7.00 LDM Stop 2 fulls) to 14.00 LDM > 13.60 LDM.
   • Expected System Behavior: The milk run logistics software CVRPTW optimizer must catch the intermediate Stop-2 14.00 LDM violation during route building (even though end-of-route full LDM or weight might look feasible in isolation), automatically shifting 1.50 LDM (6 units) to an adjacent milk-run loop (MR-NORTH-05) so Stop 2 departs at 12.50 LDM <= 13.60 LDM.
2. ACT-L162-02 — Unscanned Empty RTI Drop / Supplier Refusal Escalation:
   • Scenario: At Stop 1 (Supplier A), the driver is scheduled to drop 18 empty Gitterboxes (2.40 LDM) and pick up 24 full Gitterboxes (3.20 LDM). Supplier A's dock clerk attempts to refuse 12 of the empty Gitterboxes (leaving 1.60 LDM of unscheduled empties on the trailer, which would cause an LDM overflow at Stop 4).
   • Expected System Behavior: When the driver enters actualScannedDropQty = 6 < 18 in the mobile app, the app calculates that keeping 1.60 LDM of refused empties onboard will breach 13.60 LDM at Stop 4 (13.10 + 1.60 = 14.70 LDM), blocks departure sign-off (ERR_REFUSED_EMPTIES_CAUSE_DOWNSTREAM_OVERFLOW), and requires either supplier acceptance of the 12 empties or a corresponding -1.60 LDM reduction in Supplier A's non-critical outbound pickup.
3. ACT-L162-03 — Automated VDA 4927 Monthly Returnable Packaging Account Reconciliation:
   • Scenario: Supplier C begins the month with 120 Gitterboxes in custody, receives 360 empty Gitterboxes across 20 milk-run drops, ships back 352 full Gitterboxes, and reports 118 Gitterboxes in its month-end physical cycle count (vs. book balance = 120 + 360 - 352 = 128).
   • Expected System Behavior: The RTI ledger automatically generates a VDA 4927 Packaging Account Statement highlighting the 10-unit unaccounted shortage, triggers a 5-day supplier dispute/audit window, and—if unresolved—posts a self-billing debit memo for 10 * $240 = $2,400.

Frequently Asked Questions (FAQ)

How should empty returnable containers be sequenced inside the trailer at the OEM plant depot?

Empty containers must be loaded at the OEM plant in Strict Reverse Stop Sequence (LIFO for rear-unloading box trailers, or zoned bay allocation for Dual-Side Curtain-Siders): Stop 1's empty containers go at the rear tail (or Bay 1), Stop 2's empties in Bay 2, and Stop 4's empties at the nose. For side-loading curtain-sider mega-trailers, the milk run logistics software prints a Visual Bay Plan (Bays 1 to 17) so forklift drivers at each supplier stop open only the specific curtain bay assigned to their drop/pickup without disturbing adjacent stops' pallets.

What happens if a supplier delays a milk-run truck at Stop 2 by 45 minutes?

A milk-run truck operates like a passenger commuter train: it cannot wait indefinitely at one station without derailing every downstream supplier window and the OEM plant assembly slot. The milk run logistics software enforces a hard Detention Cut-Off Timer (e.g., 30 minutes max dock dwell): if Supplier 2's pallets are not staged at the dock by T_arrival + 20 min, the Control Tower receives an alert, logs a SUPPLIER_NOT_READY_DETENTION KPI penalty, and authorizes the driver to depart at T_arrival + 30 min with whatever pallets are loaded so Stops 3 and 4 remain on schedule.

How does milk-run software handle mixed stackability (e.g., fragile top-load cartons vs. heavy steel bins)?

Every packaging instruction (POP — Packing Instruction in SAP / ERP) defines max_stack_layers, max_top_load_kg, and footprint_mm. The 3D Loading-Meter engine ensures heavy steel Gitterboxes or engine racks are placed on the trailer floor (Layer 1), while lighter KLT pallet loads with flat plywood/plastic lids are stacked on Layer 2, never placing a steel cage on top of a cardboard or plastic tote load.

Can inbound milk runs be combined with outbound customer or inter-plant transfers (Backhauls)?

Yes. In Triangular / Backhaul Milk Runs, instead of departing the OEM plant with a trailer carrying only folded empty bins (which may occupy only 4.5 LDM of a 13.6 LDM trailer), the truck carries 8.0 LDM of finished service parts to a Regional Aftermarket Parts Distribution Center (Stop 1) located near the supplier cluster, unloads the service parts, and uses the freed 8.0 LDM to collect inbound Tier-1 production components on the return leg.