93% US DCs ≤2d; hero regions 100%; cross-border 3-5d
In-Transit
🏢
3PL Warehouse
DSV / DBS Cherry Valley IL Venlo NL
6
Receive & Inspect
Verify RSN, condition, qty vs STO
GR Confirm
7
Store (FIFO)
US: 2,160/3,300 EMEA: 2,260 pos On SI books; non-valuated
WMS
8
Inventory Mgmt
Cycle counts, adjustments, state transfers, holds
Adj/Count
24 HRS
9
Pick, Prep & Stage
DC calls → DSV picks per Ship PO; stages for load
OBD ≥1d prior
↩
Returns to SI
Rework/damage → blocked stock → STO back
🏗
Data Center
CO+I · DC Ops 150+ Global DCs End customer
12
Dock & Receive
GR at DC; FG → MS books; asset settlement
GRInvoice
13
Install & Go Live
Rack install → W2L live; RSN lifecycle complete
W2L Live
🎯 Purpose & Business Case
Reduce DC delivery transit from 5-7 days → 1-2 days
Enable Warehouse to Live (W2L) build-to-stock model
Support +25% YoY cloud demand with improved predictability
Deliver CapEx savings by reducing in-transit inventory
Reduce carbon emissions ~60% via consolidated distribution
📈 Key Performance Metrics
FSL → DC Transit1-2 days (93% US)
Hero Regions100% ≤ 2 days
Prior Baseline5-7 biz days
Volume via FSL~30%
CapEx Savings~$30M
Transport Savings$4M-$8M/yr
CO2 Reduction60%
🏛 Governance
US Ops: Horacio Ochoa Gomez
EMEA Ops: Altani Blakos
3PL: DSV/DBS (both sites)
Freight: MMF via RMS/TMC (all legs)
Inventory: SI books until DC GR
Trade: SI is IOR/EOR at FSL
US Go-Live: Feb 2024 (Cherry Valley)
EMEA Go-Live: Sep 2024 (Venlo)
Scope
In Scope
L11 Storage, Compute, GPU racks
All 5 SIs (19 factories, 7 countries)
US FSL — Cherry Valley, IL
EMEA FSL — Venlo, NL
STO + Ship PO flows
Returns & rework
Serialization tracking (RSN)
Out of Scope
T2 component hubs (Arrow/DSV VMI)
India / Brazil / Australia FSLs
SI-managed freight (WWT)
Build order execution
Key Abbreviations
FSL — Forward Stocking Location STO — Stock Transfer Order Ship PO — Ship Purchase Order ASN — Adv. Shipment Notice OBD — Outbound Delivery GR — Goods Receipt PGI — Post Goods Issue RSN — Rack Serial Number MMF — MS Managed Freight W2L — Warehouse to Live BTS — Build to Stock BTO — Build to Order IOR/EOR — Importer/Exporter of Record IBP — Integrated Biz Planning IFS — Intelligent Fulfillment Sys RDD — Requested Delivery Date
42% of ICMs generated in Mar–May 2025 were opened to clean up LP / OBD / ASN milestones.
9
Change types driving LP cancellations
9 change types in the documented current-state matrix trigger load plan cancel, change, or cancel → new handling.
Manual
Cleanup path in use today
OBD / ASN cleanup is a manual process handled through email and ICM after post-OBD cancel / change events.
5–15
OBD / ASNs manually deleted per day
Cloud Logistics Ops is asked to manually delete 5–15 OBD / ASNs per day via email or ICM in the documented current state.
📊 E2E Process Flows (Visio Architecture)
Current-state only. These flows are taken directly from the FSL Architecture Design Review / Book of Diagrams Visio source and show the full documented signal chains with no future-state inference.
Step
Action
Actor
System
Signal
Direction
🔄 Normal LP Lifecycle
Current-state signal chain from the FSL Architecture Design Review. The LP lifecycle above is a simplified view. See the full E2E Process Flows section for the complete Visio-documented signal chains. Selecting a cancellation scenario highlights the steps touched by the documented reservation, Ship PO, and load plan actions.
1
IBP STRIBP generates the replenishment trigger.
→
2
SAP ECC STOSTR becomes a blocked STO and is sent to TMC.
→
3
SI STO AckSI creates the STO in their system and returns STO Ack.
→
4
SI ConfirmSI confirms the STO is ready to ship from factory.
→
5
TMC Load PlanCarrier is assigned and route is planned from the confirmed STO.
→
Point of No Change
6
LP Distributed to SIMS sends the LP to SI, unblocks the STO, and OBD creation starts.
→
7
RSN AssignmentSI assigns RSNs; current-state rule is 1 OBD per LP and 1 line per RSN.
→
8
PGI + Loaded ASNSI picks, packs, ships, and sends PGI plus loaded ASN.
→
9
In-Transit MilestonesTMC tracks the shipment while it moves to the receiving location.
→
10
GR with RSNDBS receives at FSL and posts goods receipt with RSN.
→
11
GR Sent to SIMicrosoft sends GR to SI and SI posts GR in their system.
Documented point of no change: once the load plan is distributed, downstream OBD / SN documents already exist. Cancel / change activity after this point drives the manual cleanup process documented in the Architecture Review and JCAB playbook.
🏭 SI Response Behavior
Current-state response from Architecture Review slides 58–59. The dividing line is whether OBD already exists at the SI. Use the E2E Process Flows above to see where the load plan distribution / OBD boundary sits in each documented chain.
Before OBD exists
Positive FACK
Ingrasys
Always positive if STO FACK was positive
Lenovo
Positive only
ZT
Positive only
Automatic LP cancel / change prior to OBD is documented as Yes for all three SIs.
After OBD exists
Negative FACK
Ingrasys
Negative — OBD already exists
Lenovo
Negative — OBD already exists
ZT
Negative — OBD already exists
Post-OBD LP cancel / change moves into manual cleanup because the SI cannot auto-process the request after OBD creation.
Document relationships supported today: 1:1 (STO → LP → OBD → ASN) and 1:N delivery splits are supported. N:1 consolidation and partial / short ship are not in scope, and multiple ASNs sharing one LP fail in DBS because DBS cannot change an existing LP.
🧭 Cancellation Scenario Matrix
Documented current-state change triggers from the BRD current-state section. Click a row to highlight the lifecycle steps touched by that scenario, then use the E2E Process Flows above to trace the full current-state signal chain.
Change Type
DC Reservation Action
Ship PO Action
Load Plan Action
MSF / MSPN Change
Cancel → New
Change
Cancel → New
Quantity Change
Cancel → New
Change
Cancel → New
Ship-from Change
Cancel → New
Change
Cancel → New
Destination / DC Change
Cancel → New
Same country: Change Diff country: Cancel → New
Cancel → New
Supplier ID Change
Cancel → New
Cancel → New
Cancel → New
PO Cancellation
None
Cancel
Cancel
DC ETA Date Change
Change
None
Threshold: GT X → Cancel → New (if not picked up); LT X → Change
Price Change
None
Threshold: GT X → Cancel → New; LT X → Change
None
Carrier Change
None
None
Change
Select a current-state scenario to highlight the lifecycle steps touched by the documented reservation, Ship PO, and load plan actions.
Featured
In-Transit DC Reroute — Current-State Process
This swim lane shows the documented current-state reroute path when an in-transit MDM shipment receives a leadership-approved DC change exception.
Documented current-state pain 42% of ICMs in Mar–May 2025 were opened to clean up LP / OBD / ASN milestones, and Logistics Ops manually deletes 5–15 OBD / ASNs per day through email or ICM.
📝 JCAB Decision Rules
Racks in transit → Reject
Within TMC SLA → Reject
Racks aged 6 months or more → Reject
Super-geo change → verify no lock is causing the cross-geo issue
More than 4 weeks from JCAB creation → Accept
4 weeks or less → Reject unless SCOM Leadership + CP approve the exception
⏳ DC ETA Push-Out Rules
Racks in transit → Reject
Ship date within TMC SLA (ground = 2d, air = 7d) → Reject
When leadership override is granted, Cloud Logistics Ops sends the reroute instruction to RMS / TMC manually.
If OBD already exists, the SI response is negative FACK and cleanup moves to email / ICM handling.
SCOM / OFMJCAB intake and exception approval
1 · Intake
JCAB submitted
SCOM / OFM receives the in-transit DC change request on the MDM shipment.
2 · Standard Rule
Default answer = reject
Per SOP, racks already in transit are rejected unless leadership authorizes the exception.
3 · Override
Leadership override required
SCOM Leadership + CP approval is the gate for proceeding inside the 4-week window.
Cloud Logistics OpsManual coordination bridge
4 · Manual Notify
Reroute instruction sent to RMS
Cloud Logistics Ops manually sends the new destination and reroute instruction to RMS / TMC.
RMS / TMCCancel original LP, then create replacement LP
5 · Cancel LP
Original LP cancelled
RMS cancels the original load plan and sends the cancel signal to Microsoft and SI.
9 · Create New LP
Replacement LP created
RMS creates the new load plan using the approved destination DC.
SAP ECC / SINegative FACK and manual cleanup zone
6 · SI Response
Negative FACK
SI rejects the cancel / change because OBD already exists.
7 · Manual Cleanup
OBD / ASN deletion via ICM
Engineering teams and Logistics Ops clean up the old documents through email or ICM.
8 · Status Gap
RSN status limbo
RSN and shipment state remain misaligned until the cleanup work finishes.
10 · Recreate Docs
New OBD / ASN created
The new LP is distributed to SI and SI creates the replacement OBD / ASN.
CarrierPhysical move
11 · Redirect
Truck physically diverted
The carrier redirects the in-transit truck to the newly approved DC.
Destination DCReceipt and close
12 · Receive
GR at new destination
The new DC receives the racks and goods receipt is posted at the new destination.
🔍 Current-State Gaps & Open Questions
“Need to confirm ALL STO change management scenarios from BOTH MS and SI perspectives.”
“Visio update now anchors the point of no change at the documented load-plan commitment step for each primary flow; remaining work is to confirm how every SI exception maps to that boundary.”
“TBD – today the SI can reject the change (initiated via POA) – need to understand the scenarios where they would reject.”
“If we split a single order into 2 load plans – how does that get represented back to MSFT.”
Source: FSL Architecture Design Review (Anjali Rajurkar/JP Hadjiandreou, 2024) · FSL Architecture — Book of Diagrams (Visio, converted May 2026) · JCAB Process Playbook (SCOM/OFM) · FSL Load Plan Change Management BRD — Current-State Section (Charlotte Byers/SCOM, June 2025) | MICROSOFT CONFIDENTIAL