Setup required for working with Downtime Registrations


Before you start to create Downtime Registrations, you must first set up the Downtime Priorities you want to use and the date fields to be shown.


Downtime Registration requires a separate EAM-BC license. The license fee is included in some paid license plans for EAM-BC.

Maintenance Manager

License Requirements

In EAM-BC, a separate license is required for working with Downtime Registration.

Set Up Downtime Priorities

  1. Select "Alt+Q" on your keyboard to open the search field.
  2. Enter "downtime" in the search field.
  3. Select Downtime Priorities.
  4. Select New.
  5. Enter a Code for the Priority, for example, "Low" or "High".
  6. In the Severity field, enter a number to show the severity of the priority code.
  7. Enter a Description.
  8. Select the Default check box for the priority that should be shown when you create a new Downtime Registration.

Set Up Date Fields

In Asset Management Setup, you select which date fields should be shown when you register downtime on an Asset.

  1. On your role center, select Assets Setup > Asset Management Setup.
  2. In the Show Downtime Dates When Register field, select "Starting Date" or "Ending Date" or "Both Dates", depending on which fields should be available when you create a Downtime Registration on an Asset.

If you select "Starting Date" or "Ending Date", a Duration field is also shown in the Register Downtime pop-up when you create a Downtime Registration.

Downtime Category

Downtime Categories allows you to organize downtime entries by category such as "Breakdown", "Planned Downtime", etc.

Downtime Category can be used during the Downtime registration, as well as directly on the Downtime Card.
It is not mandatory to use Downtime Category.

Create Downtime Category

The steps to create Downtime Category are:

1. In Tell Me, search for Downtime Category.
2. Add your categories (examples: Planned, Unplanned) .

Sample Downtime Categories

Downtime Category explain why an Asset was out of service at a high level ("Planned", "Unplanned").

Downtime Category - Example 1 that only has two mutually exclusive categories:

  • Planned
  • Unplanned

Downtime Category - Example 2 that details why an asset was down:

  • Cleaning
  • Idle
  • Planned
  • Shift ended
  • Tool Change
  • Unplanned

Downtime differ from Failure Reporting such as "Machine failure, Incident, Human error, Unavailable Spare Parts, Human Error".

Downtime Categories list
Downtime Categories list
Downtime Category is shown on the Downtime card
Downtime Category is shown on the Downtime card
Copyright Dynaway A/S