What Is This Spreadsheet For?
This spreadsheet lets you manage maintenance plans in TRACTIAN. Use it to create new plans, update existing ones, and configure scheduling, recurrence, and assignment rules. Each plan defines how and when maintenance work orders are generated for a given asset, including calendar-based or metric-based recurrence, team assignments, and eligible execution days.
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 | Number | The plan number assigned by the system | No (only for updates) | Integer | Export only |
2 | Status | The current status of the plan | No | Dropdown: active, paused, finished | Import / Export |
3 | Title | The name of the maintenance plan | Yes | Text | Import / Export |
4 | Description | A detailed description of the plan | No | Text | Import / Export |
5 | Asset Path | The full hierarchical path to the target asset | Yes | Text (path separated by /) | Import / Export |
6 | Assigned Emails | Email addresses of responsible users | No | Email addresses (comma-separated) | Import / Export |
7 | Assigned Teams | Names of teams assigned to the plan | No | Team names (comma-separated) | Import / Export |
8 | Categories | Work order categories for the plan | No | Dropdown, dynamic (comma-separated) | Import / Export |
9 | Priority Name | The priority level for generated work orders | No | Dropdown, dynamic | Import / Export |
10 | Recurrence Title | A name for the recurrence pattern | No | Text | Import / Export |
11 | Calendar Frequency Unit | The time unit for calendar-based scheduling | No | Dropdown: daily, weekly, monthly, yearly | Import / Export |
12 | Calendar Interval | The interval value for calendar recurrence | No | Positive integer | Import / Export |
13 | Metric Name | The metric used for metric-based scheduling | No | Text (must exist in system) | Import / Export |
14 | Metric Interval | The interval value for metric-based recurrence | No | Non-negative integer | Import / Export |
15 | Additional Recurrence Intervals | Extra recurrence multipliers | No | Positive integers (comma-separated) | Import / Export |
16 | Work Order Template Names | Templates to generate for this plan | No | Text (comma-separated, must exist in system) | Import / Export |
17 | Start At | The plan start date and time | No | ISO 8601 with timezone | Import / Export |
18 | End After Occurrences | Number of executions before the plan ends | No | Non-negative integer | Import / Export |
19 | End At | The plan end date and time | No | ISO 8601 with timezone | Import / Export |
20 | Schedule New Work Order | Whether to automatically schedule new work orders | No | Yes or No | Import / Export |
21 | Eligible Days | Days of the week when the plan can run | No | Full day names (comma-separated) | Import / Export |
Columns in Detail
Number
The unique plan number assigned by the system. This column appears only in exports. When importing, leave it empty to create a new plan. To update an existing plan, provide the plan number so the system knows which plan to modify.
Status
The current status of the plan. Choose one of the allowed values: active, paused, or finished. If left blank during creation, the system applies the default status.
Title
The name of the maintenance plan as it will appear throughout TRACTIAN. This field is required. For example: "Monthly Motor Inspection", "Weekly Safety Check", "Quarterly Pump Overhaul".
Description
A detailed description of the plan. Use this field to document the purpose, scope, or any special instructions for the maintenance plan.
Asset Path
The full hierarchical path to the target asset in the asset tree, using / as a separator. For example: "Factory/Line 1/Motor A". The path must match exactly what is shown in the platform, including spelling and hierarchy. This field is required.
Assigned Emails
The email addresses of users responsible for the plan. Separate multiple emails with commas. Each email must correspond to an existing user in the system. For example: "[email protected], [email protected]".
Assigned Teams
The names of teams assigned to execute the plan. Separate multiple teams with commas. Each team must already exist in the system. For example: "Maintenance Team, Electrical Team".
Categories
The work order categories associated with this plan. Choose from the categories configured in your company. Separate multiple categories with commas. For example: "Preventive, Inspection".
Priority Name
The priority level applied to work orders generated by this plan. Choose from the priorities configured in your company. For example: "High", "Medium", "Low".
Recurrence Title
A descriptive name for the recurrence pattern. This is free text and helps identify the scheduling rule. For example: "Every 2 weeks" or "Monthly cycle".
Calendar Frequency Unit
The time unit for calendar-based scheduling. Choose one of the allowed values: daily, weekly, monthly, or yearly. If you set this column, you must also set Calendar Interval.
Calendar Interval
The numeric interval for calendar-based recurrence. For example, if Calendar Frequency Unit is "weekly" and Calendar Interval is 2, the plan runs every 2 weeks. Must be a positive integer. Required when Calendar Frequency Unit is set.
Metric Name
The metric used for metric-based scheduling. The metric must already exist in the system. For example: "Operating Hours", "Kilometers", "Production Cycles". Use this for plans triggered by equipment usage rather than calendar time.
Metric Interval
The interval value for metric-based recurrence. For example, if Metric Name is "Operating Hours" and Metric Interval is 500, the plan triggers every 500 operating hours. Must be a non-negative integer.
Additional Recurrence Intervals
Extra recurrence multipliers applied to the base recurrence. Enter positive integers separated by commas. For example: "2, 4, 6" means additional work orders are generated at 2x, 4x, and 6x the base interval.
Work Order Template Names
The names of work order templates to generate when the plan triggers. Separate multiple templates with commas. Each template must already exist in the system. For example: "Inspection Template, Lubrication Template".
Start At
The date and time when the plan begins. Use ISO 8601 format with timezone. For example: "2024-01-15T09:00:00Z". The timezone is required.
End After Occurrences
The number of executions after which the plan stops. Must be a non-negative integer. For example, entering 10 means the plan ends after 10 work order generations.
End At
The date and time when the plan ends. Use ISO 8601 format with timezone. For example: "2024-12-31T23:59:00Z". The timezone is required.
Schedule New Work Order
Whether the system should automatically schedule new work orders when the plan triggers. Enter "Yes" or "No".
Eligible Days
The days of the week when the plan is allowed to run. Enter full day names separated by commas. English names are accepted: monday, tuesday, wednesday, thursday, friday, saturday, sunday. Portuguese and Spanish names are also accepted (e.g., segunda, quarta, sexta or lunes, miercoles, viernes). For example: "monday, wednesday, friday".
Custom Fields
This spreadsheet does not include custom fields.
Tips for a Successful Import
The Title and Asset Path columns are required for every plan.
To create a new plan, leave the Number column empty. To update an existing plan, provide the plan number.
The Number column is export only. The system assigns it automatically when a plan is created.
All Asset Paths must match exactly the hierarchy shown in the asset tree. Verify paths in the platform before importing.
All Assigned Emails must correspond to existing users, and all Assigned Teams must correspond to existing teams.
All Categories, Priority Name, Work Order Template Names, and Metric Name values must already exist in your company before importing.
If you set Calendar Frequency Unit, you must also set Calendar Interval.
Use ISO 8601 format with timezone for Start At and End At (e.g., "2024-01-15T09:00:00Z").
For Eligible Days, use full day names. Abbreviations are not accepted.
If you leave an optional column blank, no value will be set for that field on a new plan, or the existing value will remain unchanged during updates.
Example Rows
Number | Status | Title | Asset Path | Calendar Frequency Unit | Calendar Interval | Eligible Days |
active | Weekly Safety Check | Factory/Line 2 | weekly | 1 | monday, wednesday, friday | |
Monthly Motor Inspection | Factory/Line 1/Motor A | monthly | 1 | |||
1001 | paused | Quarterly Pump Overhaul | Factory/Pump Station/Pump 1 |
Frequently Asked Questions
What happens if I leave the Number column empty?
A new plan will be created. The Number column is only needed when you want to update an existing plan. When exporting, the number is filled automatically for every plan.
Can I set both calendar-based and metric-based scheduling on the same plan?
Yes. Fill in both the Calendar Frequency Unit / Calendar Interval fields and the Metric Name / Metric Interval fields. The plan will use both scheduling methods.
What happens if the asset path does not exist?
The import will fail for that row. Verify the exact path in the asset tree on the platform before importing. The path is case-sensitive and must match the full hierarchy.
What day names can I use for Eligible Days?
You can use full day names in English (monday, tuesday, wednesday, thursday, friday, saturday, sunday), Portuguese (segunda, terca, quarta, quinta, sexta, sabado, domingo), or Spanish (lunes, martes, miercoles, jueves, viernes, sabado, domingo). Abbreviations are not accepted.
What happens if I leave optional columns blank when updating?
The existing values in TRACTIAN will not be changed. Only columns with values will be updated.
How do I attach work order templates to an existing plan in bulk?
Use the separate Plans V2 Work Order Template spreadsheet to manage which work order templates are linked to which plans and which recurrence cycles each template applies to. See Plans V2 Work Order Template.
Where can I find related documentation?
Plans V2 Work Order Template — Attach or manage work order templates on existing plans.
Plans V2 Work Order Operation Template — Add or change operations inside plan-linked work order templates.
Plans V2 Triggers and Tolerances — Advanced trigger conditions, tolerances, and reminders for existing plans.