Disruptions — machine down, supplier late, and what it does to the plan
Section 01
Assess first, then decide
1 minute
A bench breaks down on Tuesday. A supplier e-mails that the steel is a fortnight late. The question is never whether the plan is affected but how much, for whom, and what to do. Brytebuild answers the first two automatically and leaves the third to you. When something changes, the scheduler is run on a copy of the plan with the new facts and the difference is recorded as a disruption: which works orders would move, which would go late against their due date, and which customers' orders sit behind them. You are told at once; the live schedule is not rewritten on its own.
That last part is deliberate and comes straight from the planning literature: a schedule that reshuffles itself on every event suffers “nervousness” — it changes so often that the floor stops trusting it. SAP, D365 and Odoo all raise exception messages and let a planner decide; so does this. Started work never moves in any case.
Section 02
A work centre goes down
2 minutes
Press Downtime on the centre and record when it cannot work: from, until (your best estimate), the reason — breakdown, planned maintenance, operator absence, other — and a note. This is a dated absence on the centre's calendar, exactly as Business Central records one: the interval is non-working time for that centre only. An operation runs up to the block and resumes after it; other centres are untouched. Saving assesses the impact and shows it in the panel — “Assembly Bench A down (breakdown, 12 Sep 23:19 to 15 Sep 23:19): 8 job(s) move, 0 newly late — review and apply” — and raises a notification.
| Action | What it does |
|---|---|
| Record | Adds the downtime and assesses it. The centre shows a red Down now button while the interval is current. |
| Extend | The repair overran: move the estimated end later. Reassessed. |
| Back now | The centre came back early: the interval ends now and a disruption records what can move earlier. |
Operations are scheduled onto work centres, not people, so an absence is recorded as downtime on the centre the person runs (reason Operator absence) — which is exactly how a one-person cell is affected. Per-person calendars are not modelled.
Section 03
A supplier slips
2 minutes
Two triggers, both automatic. When a purchase order's expected arrival date is moved later (Edit purchase order), and once a day for any order past its expected date and not delivered. Each traces the delay to the work waiting on it in two ways — D365 calls the result a calculated delay and Odoo late availability:
| Trace | How |
|---|---|
| Material | For each product on the order: the open works orders (materials not yet issued) that start before the new date and use it, their total need, what is on hand now, and the shortfall. Enough stock on hand means no disruption — the slip does not reach the floor. |
| Pegging | The works order or sales order the purchase order was raised for (MRP recommendations converted to it, and the order's linked sales orders) — counted even when stock would cover it, because that order was promised on this supply. |
The purchase order page then carries a red banner — “… slipped 07 Sep → 25 Sep: 1 job(s) waiting on it. Waiting on this order: WO-2026-0008 — for Halcyon Construction Ltd.” — and the disruption appears on the page below with the material table (needed 180, on hand 68, short 112). Supplier slips are never applied as a reschedule: the fix is expediting or a second source (see Sourcing risk), and the planner decides.
Section 04
The Disruptions page
2 minutes
Open disruptions, worst first (most jobs newly late, then most moved). Expand a row for the impact: for downtime, each works order with was due to finish → would finish, its due date and Newly late / Later still / On time, plus the customer and sales order behind it; for a supplier slip, the material table above. Then:
| Button | Effect |
|---|---|
| Apply reschedule | Runs the scheduler for real with the new facts — unstarted operations only, started work never moves — and marks the disruption Reschedule applied. Downtime disruptions only. Needs the works-order edit right. |
| Acknowledge | Parks it while you act (call the supplier, move the job by hand). |
| Resolve | Closes it. The Applied and Resolved filters keep the history. |
Section 05
Automatic rescheduling
1 minute
Off by default. Turn it on and a downtime is still assessed and listed, but the reschedule of unstarted operations is applied immediately rather than waiting for a planner — the choice for a shop that prefers a live schedule to a stable one. Supplier slips are never applied automatically whatever the setting.
Per-person absence calendars; a frozen / slushy time fence beyond “started work never moves”; alternative-routing suggestions; expediting the purchase order automatically; a fractional capacity reduction (Business Central's efficiency %); shading downtime on the Gantt; a recomputed due date for the demand (D365 propagates the delay into a new date — this reports the shortfall and the jobs).