Transcrito
A Machine Goes Down. How Should Your Production Plan React?
15 de sep. de 2026 ·
1h 41m 42s
Descarga y escucha en cualquier lugar
Descarga tus episodios favoritos y disfrútalos, ¡dondequiera que estés! Regístrate o inicia sesión ahora para acceder a la escucha sin conexión.
A Machine Goes Down. How Should Your Production Plan React?
Descripción
When a critical machine goes down, ERP may still show capacity that no longer exists while the shop floor improvises. This episode guides production planners, plant managers and IT/OT architects...
mostra más
When a critical machine goes down, ERP may still show capacity that no longer exists while the shop floor improvises. This episode guides production planners, plant managers and IT/OT architects from disruption detection and impact tracing to finite-capacity rescheduling, so the factory gets a revised plan it can actually execute.
In this episode
Key takeaways
Explore more on M365.FM
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
mostra menos
In this episode
- 00:00 – Intro: a machine outage is a planning event
- 01:07 – Separating real disruption from shop floor noise
- 06:57 – How long is the capacity gone?
- 13:03 – Production context and affected orders
- 25:51 – Bottlenecks, priorities and constraints
- 45:16 – Response options and finite capacity rescheduling
- 75:27 – Information flow from machine to planner
- 88:00 – Microsoft Fabric, Power BI and automation boundaries
Key takeaways
- Only a confirmed loss of capacity, judged by expected loss, recovery window and exposed orders, should trigger re-planning, not every PLC signal.
- Planners need a repair range with a confidence level, an impact list that explains dependencies, and a small set of response options tested with finite capacity.
- Fabric and Power BI provide governed facts and visibility, while scheduling logic proposes options and people approve the changes that reach the shop floor.
Explore more on M365.FM
- Episode page: the full episode with chapters and FAQ on machine outages and re-planning
- Microsoft Fabric – a governed shared data foundation for disruption facts, but not the scheduling engine itself
- Power BI – shows planners current outages, affected orders and scenario results, but does not issue a plan
- Microsoft Excel – useful for testing a planning idea, risky when it becomes the uncontrolled live schedule
- Related episode: Why AI Can't Optimize a Factory It Doesn't Understand
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
Información
| Autor | Mirko Peters M365, Azure & AI |
| Organización | m365 FM |
| Página web | www.m365.fm |
| Etiquetas |
Copyright 2026 - Spreaker Inc. an iHeartMedia Company
Comentarios