Skip to content
  • There are no suggestions because the search field is empty.

How to allocate downtime in OFS?

Setting a downtime reason on the Console while the line is stopped, and catching up on stoppages that were missed once the line is running again.

Step 1 — Wait for the reason panel

The reason panel appears in the right column as soon as the line changes state. It stays on screen only while that state is current — once the line is running again, use the unallocated events route further down this article.

image10-2

You can set a reason against any of these machine states:

  • Planned
  • Unplanned
  • Setup
  • Run Slow

Each state offers its own list of reasons, set up in Fusion Manager. If the reason you expect isn't in the list, it is almost always because it lacks the matching group. A reason set up for downtime only will not appear while the line is in setup, even if it is assigned to the line.

Step 2 — Select the category and the reason

image7

Step 3 — Press Set Reason

image3

Nothing is recorded until you press Set Reason — selecting a reason only highlights it. The panel then returns to the category list, and Current Downtime Reason shows the reason in red.

Step 4 — Add a comment

Type in the feedback box in the bottom-right corner. A reason code tells you what type of stoppage it was; a comment tells you what actually happened.

Comments can be left at any time, not only during a stoppage.

image4-3

If the line is running again

Once the line comes back, the reason panel is gone — but the stoppage is still owed a reason. Unexplained stoppages collect in the unallocated events list.

  1. Press View Unallocated Events.
    image13
  2. Select the event you want to explain.

    image1-3
  3. Press Add Reason.

    image6-4
  4. Select the category.

    image2-4

  5. Select the reason.

    image9-2

  6. Press Set Reason.

image14

Find the explanation video here.