*
Concepts
*
Tasks
*
Settings

Reporting Downtime Incidents

This section explains how to create a downtime incident for a work order task.
Downtime incidents are usually created when you are reporting activity for work order tasks. You can create one or more downtime incidents for each task. In addition, you can create “ad-hoc” downtime incidents that do not reference any work order. You can also track downtime incidents on failure records.
For information about reporting downtime incidents from a failure, see Adding Downtime to Failure Records.

To Create a Downtime Incident

1.
Open the work order task.
2.
From the Task menu select Report Activity. The Activity Report dialog appears.
3.
Select the Asset Info tab and then the Downtime incidents tab. Click New. The New Downtime Incident dialog appears.
4.
Enter the following information:
Setting Name
Description
Failure
The failure against which this downtime incident is being reported.
Work order
The work order related to the downtime incident. If you are entering the incident from an activity report, the system automatically fills in this information.
Work order task
The work order task related to the downtime incident. If you are entering the incident from an activity report, the system automatically fills in this information.
Asset
The asset against which the downtime incident is reported. By default, this is the asset being worked on for the selected work order task. You must select an asset to save the downtime incident.
Related asset
If the incident involved another asset, you can identify the related asset here. The incident can then be included in comparative analyses for the related asset.
5.
On the Details tab, provide the following information:
Setting Name
Description
Incident title
Enter a short title for the incident. You can enter a more detailed description of the incident on the Description tab.
Reason
The reason for the downtime. Select the appropriate reason.
Downtime started
The date and time the downtime incident began. Select the correct date and the time when the asset stopped working.
Downtime ended
The date and time the downtime incident ended. Select the correct date and the time when the asset began to run again.
Production affected for
The length of time that production was affected. APM automatically enters the length of time from the start of the downtime incident until its end. You can change the duration if production was affected for longer or shorter than the length of time the asset was down.
Scheduled downtime
The length of time the asset was scheduled to be down, as planned on the PM job. APM enters this information automatically, but you can change it if necessary.
Operating level
The percentage of regular production that was achieved during this downtime incident. If the downtime incident did not require a full stop of production, but did slow down production, enter the actual operating level during the downtime incident as a percentage. For example, if the asset normally processes 100 units per hour, but was only able to process 60 units per hour during the downtime incident, enter 60.
6.
Select the Lost Production tab to view the lost production costs and amount incurred by the incident.
7.
Click Calculate value and amount of lost production. APM uses the Production was affected for and Operating level values from the Details tab in the calculation. For example:
Tip: You can select a different calculation for the asset from the Calculation to use list.
8.
Select the Description tab to enter a longer, more detailed description of the incident.
9.
Select the Attachments tab to attach external files to the downtime incident, and click New. Complete the information on the Attachment dialog and click OK. For more information on attachments see Adding Attachments to Objects.
10.
Select the Indicator Snapshots tab to view indicator values at downtime.
11.
When you have finished entering all of the downtime incident information, click OK.