Shutdowns
A shutdown with its window, its work and its budget
An initiative groups up to 250 work orders with a lead, dates and a budget, and shows progress, overdue work, hours and costs as the work gets done.
The problem
“The shutdown plan is a spreadsheet, and nobody knows if we are over budget.”
Turnarounds are planned in one tool, done in another and costed months later. By then the window is long closed.
In Ophelm
The whole shutdown in one place
Downtime planned on the asset
Put planned downtime windows on assets, link each to up to 50 work orders and initiatives, and see them on the initiative’s timeline next to its work orders.
Budget against actual costs
With Costs on, the initiative’s budget sits beside what its work orders have cost so far: labour from logged time, parts and other costs, spent and remaining.
A reminder when the window opens
A downtime window can remind its people when it starts, and again at its end if the asset is still offline.
Questions
How large can an initiative be?
Up to 250 work orders, with a lead, start and end dates and a budget.
Does closing an initiative close its work orders?
No. Its work orders stay records of their own; completing, cancelling or reopening the initiative never changes them.
Can we follow costs against the budget?
Yes. The initiative adds up its work orders’ costs and hours and sets them against its budget, beside its progress and overdue work.
Can we see the spare parts a shutdown needs?
Yes. The initiative’s Spare parts tab lists the parts of its work orders, with a pick list you can export as CSV.
Can one downtime window cover several jobs?
Yes. A window belongs to one asset and can be linked to up to 50 work orders and initiatives.
Is the downtime on an initiative measured or planned?
Planned. The initiative shows its assets’ planned windows within its dates; measured downtime is on each asset and in reporting.
See it with your own site
Sign up free, add a site and a few machines, and try it with your team.