CSV Import downtime causes

Prerequisites

Administration: Admin role
The Downtime Causes tab opens. Downtime Causes tab
Any existing duplicate downtime causes have been removed. Edit non-unique downtime causes.

Procedure

Click CSV import.

The CSV import dialog opens.

The dialog gives you the option to download an example CSV file to check the file format.
Drag and drop the CSV file into the designated area or click to open the file selection dialog of the operating system.
Select the CSV file to be imported in the file system.

Only one file may be selected.
Click Open.
Click Import.

The CSV file is imported (uploaded).

The CSV import dialog opens and informs you about the result.

The downtime causes defined in the CSV file have been imported.

CSV file format

GUID

(Optionally) unique ID to assign a new ID (number) to an existing cause, for example. The unique ID can be obtained from a previous CSV export if the Include unique identification feature? option has been activated.
ID

Cause number that is also used/displayed when the cause is used.
LOCATION_ID

Facility from which the cause can be used. Empty = globally valid
PARENT_ID

Higher-level cause number for hierarchical causes. Empty = no hierarchy
ADMIN

The downtime cause can only be selected by users with special privileges. (True|False)
HIDDEN

Cause can no longer be used for new downtimes. (True|False)
APPLICABLE_FROM

Restricted by facility selection. (Global|FromPlant|FromProduct|FromArea|FromLine|…)
CATEGORY

Category (Technical|Organizational|Changeover|Quality)
CLASS

Type (Planned|Unplanned|Both)
ASSISTANCE_TYPE

Assistance type (None|Ripcord|MilkRun|Userdefined)
ADDITIONAL_INFO_REQUIRED

Additional information required (True|False)
PROD_RELEVANT

Productivity-relevant (True|False)
REL_UTIL_RELEVANT

Degree of utilization (relative) relevant (True|False)
4M

4M event with further properties (True|False)
CHECK_DESCRIPTION
LANG :xx

Cause text in the respective national language, e.g. LANG:DE , LANG:EN ,..

The first line of the file must contain the corresponding column names.
Columns are separated by a semicolon (;).
Empty lines are not allowed.
Every line must contain a value for all columns defined in the first line (if optional columns are not used, they must be left empty, use trailing semicolon (;)).
The cause texts must not contain a semi-colon because it is a separator.
In the case of hierarchical downtime causes, the parent element must appear first or already exist. *The GUID column may only be used if the cause number is to be changed for an existing cause