Use scheduled stops to complete work that protects future uptime.
Planned downtime is production time intentionally reserved for maintenance, cleaning, calibration, inspection, changeover, installation, or equipment improvement. The goal is to complete necessary work with a known scope and controlled restart.
Plan maintenance around production consequence and execution risk.
Critical assets, outage windows, work scope, parts, labor, restart requirements, and documentation should be considered as one operating system.
Reduce the chance that planned work creates unplanned loss.
Clear scope, prioritization, work sequencing, documentation, spare parts, and restart criteria make maintenance events more predictable.
CRIT-ABundle Compatible Work
A planned stop can combine maintenance, calibration, cleaning, and minor upgrades when access and sequencing allow it.
Related Guide →CRIT-BProtect the Production Schedule
Downtime timing should account for demand, WIP, product mix, downstream inventory, and constraint availability.
Related Guide →CRIT-CPrepare Before the Stop
Parts, tools, permits, drawings, labor, and procedures should be ready before the downtime window begins.
Related Guide →CRIT-DVerify the Restart
A successful planned stop ends with controlled testing, quality verification, and stable production—not merely power-on.
Related Guide →Visualize priority, timing, and execution before the work begins.
These technical views provide a second perspective on the planning decision rather than repeating the hero graphic.
Planning view.
Use a structured view to compare priority, timing, and operating impact.
Execution view.
Separate major work elements so the production impact is visible before shutdown.
Relevant maintenance and plant resources.
References use approved URLs from the TempoJS industrial link inventory.