Event files

Event files record failure events and asset operating data. Event data must be in a continuous time series that is recorded at a second, minute, hourly, daily, weekly or monthly level.

Important:
  • The file must not contain duplicate column names.
  • Column names cannot contain spaces.
  • Column names cannot contain the following special characters: ' " < > + # . % * ; : \ -.
  • The file must contain an asset_id column. The asset_id column cannot contain empty or null values.
  • The file must record failure events.
  • The failure event, maintenance event, and repair event column values must be 0 or 1.
  • The file must contain a timestamp column. The timestamp column cannot contain empty or null values.
  • The file must contain an is_fail column. is_fail is a keyword for a failure event field in an event file. If you use is_fail as a column name for another field, the column will be renamed as is_fail_renamed. In the analysis results, the failure event field will be renamed as is_fail. The values in the is_fail column must be 0 or 1.
  • The nextMaintenance and manufacturedDate columns must use one of the following date formats consistently within each file:
    • yyyy-MM-dd hh:mm:ss
    • dd/MM/yyyy HH:mm:ss
    • yyyy/MM/dd H:mm:ss
    • yyyy/M/d H:mm:ss
    • d/M/yyyy H:mm:ss
    • dd.MM.yyyy HH:mm:ss
    • MM-dd-yyyy HH:mm:ss tt, where tt = AM or PM
  • When multiple event files are uploaded, when there are potential conflicts, the column values from the newer file will overwrite the column values from the older file.
Parent topic: Using data files