What is Blue Yonder Enterprise Supply Planning - Deployment?

Blue Yonder Enterprise Supply Planning - Deployment is the short-term distribution execution engine within the ESP suite that converts the long-range "Master Plan" into immediate, executable shipment orders (Stock Transfer Orders), optimizing the movement of inventory between internal nodes (Factories, Hubs, DCs) based on real-time availability, transportation constraints (e.g., full truckloads), and fair-share allocation rules.

While the Master Plan looks months into the future to answer "What should we build?", Deployment looks at the next 3–14 days to answer "What should we move right now?" It is the operational handshake between Planning and Logistics. It takes the "Planned Orders" (which are just theoretical placeholders) and hardens them into "Recommended Shipments" (RecShips) that are chemically pure—meaning they fit perfectly into a truck, respect the receiving dock's capacity, and account for the actual inventory sitting on the shipping dock today.

Why It Matters: The "Last Mile" of Planning

A Master Plan assumes infinite transportation capacity and perfect lead times. Deployment deals with reality.

• The "Push" Decision: In a supply-constrained world (e.g., only 80% of stock produced), Deployment decides who gets the inventory. It switches from "Pull" (shipping what was asked for) to "Push" (forcing inventory out to the network based on priority), ensuring that the limited stock goes to the locations with the highest risk of stock-out.
• Transportation Efficiency (TLB): It stops "Air Shipping Air." Shipping a half-empty truck is a crime against margin. Deployment uses Transportation Load Building (TLB) logic to delay or pull-forward orders by a few days to build a perfect Full Truckload (FTL), minimizing freight spend.
• WMS/TMS Integration: It speaks the language of execution. It creates orders that the Warehouse Management System (WMS) can actually pick and the Transportation Management System (TMS) can actually tender, preventing the "Phantom Order" problem where Planning sends orders that Execution cannot fulfill.

Key Capabilities

1. Fair Share Allocation: The Scarcity Engine. When demand exceeds supply, Deployment uses hierarchy-based logic to ration inventory. It can prioritize a "National Hub" over a "Regional Spoke," or ensure that every DC gets at least 3 days of cover (Equal Days of Supply) before anyone gets 5 days.
2. Transportation Load Building (TLB): 3D Optimization. It does not just count pallets. It looks at Weight and Cube. It mixes heavy items (e.g., Water) with bulky items (e.g., Chips) to "Weigh Out" and "Cube Out" the trailer simultaneously. It creates a shipment that is physically optimized for the carrier.
3. RecShip (Recommended Shipment) Logic: The Daily Pulse. Every morning, the Deployment run calculates the exact Net Requirements for every DC. It subtracts On-Hand Inventory and In-Transit Stock from the Forecast to determine the exact quantity needed to maintain the target service level.
4. Surplus Handling: The "Burn Down" Strategy. If a DC has too much stock, Deployment prevents new shipments. It forces the network to bleed off the excess locally before sending more, or it triggers a Lateral Transfer to move the excess to a neighbor DC that is running low.

The Blue Yonder Difference

Blue Yonder differentiates ESP Deployment through its Solver Integration. In many legacy systems, "Deployment" is a dumb calculator that simply rounds numbers. In Blue Yonder, Deployment is powered by the same Linear Programming (LP) and Deep Tree solvers used in the Master Plan. This means it can make complex trade-off decisions—like "Skip the Regional DC and ship direct to customer to save time"—mathematically proving that the decision yields the lowest Total Landed Cost.