What Is This Spreadsheet For?
This spreadsheet lets you manage failure events in TRACTIAN. Use it to register new failure events, update existing ones, track downtime and repair periods, record economic impact, and associate failure analysis data (FMEA) with each event. Each row represents one failure event linked to a specific asset.
Can I Import, Export, or Both?
Import (upload data into TRACTIAN): Yes
Export (download data from TRACTIAN): Yes
Column Reference
# | Column Name | What to Fill In | Required? | Accepted Values | Used In |
1 | ID (Fill only for update) | The unique identifier of the failure event | No (only for updates) | Text | Import / Export |
2 | Status | Whether the failure has been fixed | No | Dropdown: Fixed, Not Fixed | Import / Export |
3 | Event Type | The classification of the failure | No | Dropdown: Potential Failure, Functional Failure, Total Failure | Import / Export |
4 | Asset ID | The identifier of the asset where the failure occurred | Yes | Text | Import / Export |
5 | Start Date | When the failure started | Yes | Date (RFC3339) | Import / Export |
6 | End Date | When the failure ended | Yes | Date (RFC3339) | Import / Export |
7 | Downtime Start | When the asset became unavailable | No | Date (RFC3339) | Import / Export |
8 | Downtime End | When the asset became available again | No | Date (RFC3339) | Import / Export |
9 | Repair Time Start | When repair activities began | No | Date (RFC3339) | Import / Export |
10 | Repair Time End | When repair activities finished | No | Date (RFC3339) | Import / Export |
11 | Unavailability Time - Avoided Incidences | Hours of downtime avoided through preventive measures | No | Number | Import / Export |
12 | Unavailability Time - Avoided Incidences Cost | Monetary cost of avoided downtime | No | Number | Import / Export |
13 | Repair Time - Avoided Milliseconds | Repair time avoided in milliseconds | No | Number | Import / Export |
14 | Repair Time - Hourly Cost | Hourly cost of repair activities | No | Number | Import / Export |
15 | Description | Detailed description of the failure event | No | Text | Import / Export |
16 | Work Order/Request Code | External CMMS reference code | No | Text | Import / Export |
17 | Failure 1 | Name of the first failure | No | Text | Import / Export |
18 | Failure Cause 1 | Root cause of the first failure | No | Text | Import / Export |
19 | Failure Effect 1 | Effect or consequence of the first failure | No | Text | Import / Export |
20 | Failure Action 1 | Corrective action for the first failure | No | Text | Import / Export |
21 | Failure Component 1 | Component affected by the first failure | No | Text | Import / Export |
22 | Failure 2 | Name of the second failure | No | Text | Import / Export |
23 | Failure Cause 2 | Root cause of the second failure | No | Text | Import / Export |
24 | Failure Effect 2 | Effect or consequence of the second failure | No | Text | Import / Export |
25 | Failure Action 2 | Corrective action for the second failure | No | Text | Import / Export |
26 | Failure Component 2 | Component affected by the second failure | No | Text | Import / Export |
27 | Failure 3 | Name of the third failure | No | Text | Import / Export |
28 | Failure Cause 3 | Root cause of the third failure | No | Text | Import / Export |
29 | Failure Effect 3 | Effect or consequence of the third failure | No | Text | Import / Export |
30 | Failure Action 3 | Corrective action for the third failure | No | Text | Import / Export |
31 | Failure Component 3 | Component affected by the third failure | No | Text | Import / Export |
Columns in Detail
ID (Fill only for update)
This is the unique identifier assigned by TRACTIAN to each failure event. When you export, this column is filled automatically. Only fill it in when you want to update an existing failure event. Leave it blank to create a new one.
Status
Indicates whether the failure has been resolved. Select from the dropdown: "Fixed" or "Not Fixed". The internal values sent to the system are "fixed" and "notFixed".
Event Type
Classifies the severity of the failure. Select from the dropdown: "Potential Failure", "Functional Failure", or "Total Failure". The internal values sent to the system are "potentialFailure", "functionalFailure", and "totalFailure".
Asset ID
The identifier of the asset where the failure occurred. This field is required. You can find Asset IDs by exporting the asset tree data from the system. The asset must already exist in TRACTIAN.
Start Date
The date and time when the failure started. Must be in RFC3339 format (e.g., "2024-06-15T08:00:00Z"). This field is required.
End Date
The date and time when the failure ended. Must be in RFC3339 format (e.g., "2024-06-15T10:30:00Z"). This field is required.
Downtime Start
The date and time when the asset became unavailable due to the failure. Must be in RFC3339 format. This can differ from the failure start date if the asset continued operating in a degraded state before going offline.
Downtime End
The date and time when the asset became available again. Must be in RFC3339 format.
Repair Time Start
The date and time when repair activities began. Must be in RFC3339 format.
Repair Time End
The date and time when repair activities finished. Must be in RFC3339 format.
Unavailability Time - Avoided Incidences
The number of hours of downtime avoided through preventive measures. Must be a positive number.
Unavailability Time - Avoided Incidences Cost
The monetary cost associated with the avoided downtime incidences. Must be a positive number.
Repair Time - Avoided Milliseconds
The amount of repair time avoided, in milliseconds. Must be a positive number.
Repair Time - Hourly Cost
The hourly cost of repair activities. Must be a positive number.
Description
A free-text field for a detailed description of the failure event.
Work Order/Request Code
An external reference code to link this failure event with a work order or service request in a CMMS system.
Failure 1, Failure 2, Failure 3
The name of each failure associated with this event. You can register up to three failures per event. If the failure name does not exist in the system, it will be created automatically.
Failure Cause 1, Failure Cause 2, Failure Cause 3
The root cause of each failure. If the cause name does not exist in the system, it will be created automatically.
Failure Effect 1, Failure Effect 2, Failure Effect 3
The effect or consequence of each failure. If the effect name does not exist in the system, it will be created automatically.
Failure Action 1, Failure Action 2, Failure Action 3
The corrective action taken for each failure. If the action name does not exist in the system, it will be created automatically.
Failure Component 1, Failure Component 2, Failure Component 3
The asset component affected by each failure. If the component name does not exist in the system, it will be created automatically.
Custom Fields
This spreadsheet does not include custom fields.
Tips for a Successful Import
Every row must have a value in the Asset ID, Start Date, and End Date columns — they are required.
To update an existing failure event, include its ID. To create a new one, leave the ID blank.
All dates must be in RFC3339 format (e.g., "2024-06-15T08:00:00Z"). Invalid date formats will cause the import to fail for that row.
The Status and Event Type columns are dropdowns with fixed values. Only the accepted values will be processed.
Economic impact fields (Avoided Incidences, Costs, Hourly Cost) must be positive numbers.
Failure analysis fields (Failure, Cause, Effect, Action, Component) that reference names not yet in the system will be created automatically. A warning message will inform you which entities were created.
Make sure all referenced Asset IDs already exist in TRACTIAN before importing.
You can associate up to 3 failure analyses per event. If you only need one, leave the Failure 2 and Failure 3 groups blank.
Example Rows
ID (Fill only for update) | Status | Event Type | Asset ID | Start Date | End Date | Description | Failure 1 | Failure Cause 1 | Failure Component 1 |
Fixed | Functional Failure | ASSET001 | 2024-06-15T08:00:00Z | 2024-06-15T10:30:00Z | Motor bearing failure | Bearing Wear | Lack of Lubrication | Motor Bearing | |
507f1f77bcf86cd799439011 | Not Fixed | Total Failure | ASSET002 | 2024-06-16T14:00:00Z | 2024-06-16T18:00:00Z | Compressor shutdown | Valve Failure | Corrosion | Discharge Valve |
Fixed | Potential Failure | ASSET003 | 2024-06-17T09:00:00Z | 2024-06-17T11:00:00Z | Vibration anomaly detected | Misalignment | Installation Error | Shaft |
Frequently Asked Questions
What happens if I leave the ID blank?
A new failure event will be created. If you want to update an existing event, you must include its ID.
What date format should I use?
All dates must be in RFC3339 format, for example: "2024-06-15T08:00:00Z". The "Z" at the end indicates UTC. You can also use timezone offsets like "2024-06-15T08:00:00-03:00".
What happens if I enter a failure name that does not exist in the system?
The system will create it automatically. This applies to failures, failure causes, failure effects, failure actions, and failure components. After the import, a warning message will show which entities were created so you can review them.
Can I register more than 3 failures per event?
No. The spreadsheet supports up to 3 failure analyses per event (Failure 1 through 3). If you need more, consider splitting the event or consolidating related failures.
What is the difference between Start Date and Downtime Start?
The Start Date is when the failure was first identified. The Downtime Start is when the asset actually stopped operating. These can differ, for example, when a potential failure is detected but the asset continues running until a planned shutdown.
Do I need to fill in all economic impact columns?
No. All economic impact fields are optional. Fill them in only if you want to track the financial impact of the failure.
How do I find the Asset ID for my assets?
You can export the asset tree from TRACTIAN to get a list of all assets and their IDs. The Asset ID must match exactly.