Playbook: one sub-assembly runs late, the finished product slips
The situation
The board sub-assembly MO-DEMO-PCBA-1 was supposed to finish before the final assembly MO-DEMO-S100P-1 needed its boards for operation one. It didn't: the reflow step is still running. The final assembly still shows its original dates. Nobody has worked out the new finish date — and that is the date the customer will eventually ask for.
The screenshots come from the Otiox demo workspace. To follow along, choose Switch to demo in the sidebar — changes there never touch your live data.
Step 1 — See the cascade
Go to Inventory → Stock Integrity and open Child MO delays parent.

The finding links the two orders: the sub-assembly finishes on 2 October, but the final assembly needs it for operation one on 29 September. The parent slips about three days unless it is re-planned or the sub-assembly is expedited.
Step 2 — See how late the parent will be
Open MO not released on time for MO-DEMO-S100P-1.

The parent was planned to start on 29 September and is still scheduled. Started now, it ends four and a half days after its planned end. What to do: release it now, or re-plan its end.
Step 3 — Re-plan the parent
Choose Move MO finish date under Fix.

Set a start and finish the boards can support — in the demo, 5 to 7 October — and choose Schedule Order. The final assembly now carries the date it can actually meet, and that is the date to give the customer. On the next scan the findings close by themselves.
If the date matters more than the plan, work the other way: open the sub-assembly and finish its remaining operation first. See the Stuck Orders playbook.
What you have at the end
- Every sub-assembly that will make its parent late, found automatically.
- The slip in days, before the assembly station stands still.
- A re-planned parent with a date you can promise.
Related
- Use case: Late Sub-Assembly — /use-cases/late-sub-assembly
- Use case: Stuck Orders — /use-cases/stuck-orders