For the complete documentation index, see llms.txt. This page is also available as Markdown.

Downtime Table

Through an Order

Click on Details under the order's name, then the Details panel will open. Click on "Downtime Events", which will open the downtime table filtered by that order.

Downtime Events through an Order

Through an Asset

Click on Details under the asset's name, then the Details panel will open. Click on "Downtime Events", which will open the downtime table filtered by that asset.

Downtime Events through an Asset

Filtering

Filtering Downtime Events

By stop duration

If the stop duration filter isn't chosen, the events of that duration will not show

  • Active: a stop that is currently active. There should be one at any point in time if viewed through an Asset.

  • Short stop: Events that are under the "Short Stop Threshold" applied to the asset it occurs to. You can configure the short stop threshold by creating an Asset Profile and attaching it to the asset.

  • Long stop: Events that occur for longer than the short stop threshold.

Event type

Event types that were raised. It is important to note that only events with event types that have the System Event "Equipment Status Stopped" will show up on the table.

Basic Information highlighting 'Equipment Status Stopped' type

Managing Downtime

Assigning reasons

You can assign to one or multiple reasons, simply by selecting the rows.

You can also select all by clicking on the checkbox on the header row.

Selecting Downtime Table rows

Then, clicking on Assign, which also displays the total duration of downtime you had selected.

Clicking on the Assign button

Then either choose your Downtime Reason Group, which is a type of Option list. Or if you had configured a Machine Group for your Asset, then this list will automatically be used for assignment.

Assigning event reason

After choosing your reason, the events will now be marked as "Assigned".

Adding a comment to a downtime event

When assigning a reason, you can also add a comment to the event to provide additional context — for example, describing the cause of the stoppage.

This comment is shared with the operator through the activity form. When an operator opens an activity that was generated by the same downtime event, both the reason (Downtime Type option) and the comment are prefilled from the event.

If the operator edits the prefilled comment and submits the activity, their comment overwrites the event comment. If they leave the comment field unchanged, the existing event comment is preserved.

When an operator skips an activity with a comment, that skip comment is also written back to the downtime event, so it appears in the Downtime Table.

Split events

Select the event you want to split. Then click "Split".

It will automatically be set at the halfway point, then you can either choose the slider or the date picker to choose the split point.

Split event duration slider

After submitting, your one event should be split into two events.

Other features

Show/hide columns

Choose which columns you want to show or hide on the table.

Table column visibility settings dropdown

Last updated