MIXMOVE DINetwork Design & OptimisationModule 04 of 07

Test every change to your hubs and lanes before it reaches the floor.

A digital model of hubs, lanes and capacity, used to test decisions before they reach execution. Compare scenarios, find unused capacity and review rebalancing proposals with cost and carbon impact side by side.

Network Design & Optimisation

What it does

Capacity is contracted for one picture of the flows and used for another, and the gap only shows up in the invoice.

<div class="pf-rule-wrap" aria-hidden="true"><div class="pf-rule-line pf-cut"><div class="pf-rule pf-cut"><div class="pf-fh"><span class="pf-fi pf-fi--di"><svg class="ph"><use href="#ph-git-fork"/></svg></span>Scenario test · Lyon → Graz corridor<span class="pf-tag pf-tag--di">MIXMOVE&nbsp;DI</span></div><ul class="pf-rule__in"><li>Contracted capacity</li><li>Actual flows</li><li>Lanes</li><li>Hubs</li><li>Cost</li><li>CO₂</li></ul><div class="pf-rule__node"><span class="pf-ptile pf-ptile--di pf-cut"><svg class="ph"><use href="#ph-git-fork"/></svg></span><div><b>Scenario tested</b><span>before it reaches the floor</span></div></div><ul class="pf-rule__out"><li class="pf-rule__o"><b>A · keep</b><span>6 linehauls · Graz 92%</span></li><li class="pf-rule__o pf-is-on"><b>B · rebalance</b><span>5 linehauls · Graz 71%</span></li></ul></div></div></div>

In the module

Key capabilities

    1. Hub and capacity model

      • Hubs, lanes, corridors and services in one model, with operational, strategic and customer-specific views
      • Capacity per lane, hub and service: volume, weight, stops and time windows
      • Configurable SLAs, cut-offs and operating constraints
    2. Scenario planning

      • Alternative designs kept as scenarios and time-bound versions
      • Contracted capacity and prices compared with actual shipment and consignment flows
      • Ghost capacity, underutilisation and over-usage identified
      • Routing, mode mix and consolidation strategies tested, with financial and carbon impact shown together
    3. Balancing and replenishment

      • Inventory heatmaps of stock and asset levels across hubs and channels
      • Overstock, stockouts and critical thresholds highlighted
      • Proposed moves between hubs, weighing cost, lead time and service impact
      • Rebalancing moves monitored to completion, with expected and actual outcomes compared
    4. Fulfilment and routing policies

      • Policies that steer order fulfilment across all hubs, so that no single site optimises at the expense of the rest
      • Routes and consolidation optimised for cost and emissions
      • Policies tested as scenarios before roll-out to execution

    graph, git-fork, swap, tree-structure

    Roles

    Who uses it

    • Design and optimisation teams

    • Strategy and portfolio management

    • Commercial and solution design teams

    git-fork, target, handshake

    Outcomes

    Business value

    What changes when every design decision is tested before it is applied.

    1. Decisions on hubs and lanes based on data

      Where to open, close or repurpose a hub or a lane is answered with scenarios built on actual flows.

    2. Capacity that matches how it is used

      Comparing contracted capacity with real usage shows unused space, so fill rates can rise without adding vehicles.

    3. Flows, inventory and service aligned with financial and sustainability goals

      Cost, lead time, service and carbon impact are weighed together before a change reaches execution.

    See Network Design & Optimisation on your own flows.