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.
In EAM-BC, a separate license is required for working with Downtime Registration.
Use Downtime Priorities to define the severity level of downtime that can be registered on Assets. Specify Priorities as codes e.g. Critical or Low and further enter a number to show the severity of the priority code. An example could be a Priority Code called 'Critical' with a severity number '1'.
In Asset Management Setup, you select which date fields should be shown when you register downtime 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 Categories allow you to organize downtime entries by category such as 'Breakdown', 'Planned Downtime', etc. You can use Downtime Categories to be able to track why an Asset was out of service, and you can use this information to create reports about Downtime by Asset Category, Downtime Category, Problem Code, and Asset Location.
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:
Downtime Category - Example 2 that details why an asset was down:
Downtime differ from Failure Reporting such as "Machine failure, Incident, Human error, Unavailable Spare Parts, Human Error".
Copyright Dynaway A/S