Playbooki/ Nazadnje posodobljeno: 2026-10-29

Playbook: a supplier slips a week — what breaks?

The situation

A supplier emails: *your order will be a week late*. Is that a problem? It depends on what is waiting for it: which builds use the parts, which customer orders wait for those builds, and how much slack each one has. Answering by hand means walking through purchase orders, bills of materials and the production plan.

Otiox follows the chain for you, for one purchase order or for a whole supplier.

Before you start

The chain follows recorded links: PO lines → the manufacturing orders that consume them → the customer orders they serve.
Supplier-confirmed line dates are used when set; otherwise the PO's expected date.
Nothing is changed. Scenarios only calculate.

Step 1 — See what depends on one purchase order

Open the purchase order and choose Impact.

Impact: late now, late only if it slips, customer orders affected

What you see: the orders that are late already, the ones that turn late only if this PO slips, and the customer orders affected. Move the slider to test a slip of a few days.

Step 2 — Follow the chain to the customer

Choose Dependencies.

Dependencies: the PO, the build that waits for it, and the customer order behind it

What you see in the demo for PO-PRED-0001 (*if it slips another 0 days*): late now 3, late only if it slips 0, customer orders affected 1.

PO-PRED-0001 was due 30 October and is 37 days late.
MO-PRED-0001 (in progress, due 3 November) has a slack of −32 days: *supply is late*.
Customer order #6b8b1b1a for Falcon Robotics (confirmed, 3 November) has a slack of −31 days and is already late.

Solid red means late already; dashed amber means late only under the scenario. Production moves only by what exceeds its slack.

Step 3 — Ask what-if for the whole supplier

Open Command → What-if scenarios, choose A supplier is late, pick the supplier and the number of days, and Run.

What-if: the supplier a week late — which orders turn late

What you see: every purchase order from that supplier moved by the delay, and the manufacturing and customer orders that turn late because of it, with how late. Add more assumptions (a machine stops, demand changes, an extra shift) to see them together. Save the scenario to compare later.

Step 4 — Decide while there is time

For the orders that turn late: expedite with the supplier, move the build to another slot, take the parts from another order with more slack, or tell the customer the new date now. The scenario shows which of these is needed and for whom.

After: when the supplier confirms the new date on the PO line, the Impact view and the customer orders' promised dates update from it.

What you have at the end

The full chain from one late delivery to the customer who feels it.

What is late already, and what turns late only if it slips further.
A whole-supplier what-if, before the supplier's next email.

Screenshots come from the Otiox demo workspace. Choose Switch to demo in the sidebar to follow along; changes there never touch live data. Command reads your records and never changes them.