Planned Downtime and Integration-Created Line Stop Dispatches
Last updated: November 19, 2026
In the current Studio app, when an external integration creates a dispatch as a downtime dispatch type such as Line Stop Fault, selecting a planned reason code later does not automatically change the dispatch type.
This can cause events such as CIP, label changes, or film changes to continue counting as downtime until they are handled another way.
Why this happens
The integration controls the dispatch type at the time the dispatch is created.
If the integration opens the event as a downtime dispatch type, changing the reason code afterward does not reclassify that dispatch to a planned dispatch type automatically.
What this affects
If the dispatch remains a down-impact dispatch type:
the event continues to count against downtime-based production metrics such as OA and OEE
planned events may still appear as line faults
demand and related production metrics may not reflect the planned event the way users expect
Recommended setup for planned downtime
If you want planned events to be excluded from downtime-driven production metrics, use a dispatch type configured for planned downtime rather than a down-impact dispatch type.
Review these settings on the dispatch type:
Impact to Production should not be Down
enable Planned Downtime: Exclude from Availability Production Metric when you want those minutes excluded from OA
enable Planned Downtime: Exclude from LMPU Production Metric when you want those minutes excluded from LMPU
Recommended workaround for schedule and demand corrections
If planned time was already created as production time and needs to be moved to planned non-production time, use the Non Production Time Reallocation Tool.
This tool:
creates a closed dispatch
moves planned production time to planned non-production time
adjusts LMPU and other production-minute-based calculations
Important notes:
the reallocation tool cannot use a down dispatch type
it is intended for correcting planned non-production events that were not scheduled correctly in advance
support can enable the site setting if your site does not already have access to it
Best practice
For integration-driven environments, decide which events should remain true downtime and which should be treated as planned downtime.
Then:
configure the correct planned dispatch types in L2L
make sure the integration launches the intended dispatch type whenever possible
use the reallocation tool when planned time must be moved out of planned production after the fact