Shutdowns and turnarounds

Shutdowns and turnarounds planned as one piece of work

The jobs, the downtime windows, the parts and the crew in one initiative, with the budget beside them, so you can see before the window opens whether the work fits.

The situation

“The shutdown plan is a spreadsheet, three email threads and a whiteboard.”

Jobs, parts and contractors are planned in different places, the window cannot move, and nobody knows until the last day whether the work and the budget will fit.

In Ophelm

How a team does it in Ophelm

  1. 01 · Shutdowns

    One initiative for the whole shutdown

    Gather up to 250 work orders in one initiative, with a lead, start and end dates and a budget. Each work order stays an ordinary work order, planned and done as usual.

  2. 02 · Assets

    The window on every asset

    Plan downtime windows on the assets that stop, linked to the work orders that need them, and see them on the initiative’s timeline. A reminder goes out when a window starts, and again at its end if the asset is still offline.

  3. 03 · Spare parts

    Parts ready before the window opens

    Parts on open work orders are reserved at their location. Export the shutdown’s pick list as a CSV, with what is reserved, used and short.

  4. 04 · Planning

    A crew that fits the window

    Plan the work on the board against each person’s hours, absences and holidays, by week or by day.

  5. 05 · Shutdowns

    Progress and budget while it runs

    The initiative shows how many work orders are done, which are overdue, the hours logged and the costs against the budget.

Who takes part

  • Maintenance managers

    Gathers the jobs, windows and parts in one initiative, and plans the crew against their hours and absences.

  • Site managers

    Follows progress, overdue work, hours and costs against the budget, on the initiative itself.

  • Technicians

    Gets the shutdown’s jobs as ordinary work orders, each with its procedure and parts.

See it with your own site

Sign up free, add a site and a few machines, and try it with your team.