Skip to content
English
  • There are no suggestions because the search field is empty.

Uploading Scheduled and Corrective Maintenance Tasks on Assets

Support Article: Uploading Scheduled and Corrective Maintenance Tasks on Assets

Overview

This article explains how to upload scheduled maintenance and corrective maintenance tasks to assets in the system. The platform supports bulk upload via CSV or Excel import, letting you configure many maintenance activities for wind farm assets in one go.

What are maintenance tasks?

Scheduled maintenance

Scheduled maintenance tasks are planned, recurring activities performed at defined intervals (for example annual inspections or preventative maintenance). These tasks follow a start date and a recurrence pattern.

Corrective maintenance

Corrective maintenance tasks (also called component failures) are unplanned repairs that occur when a component fails. These are characterized by failure rates, failure distributions, and severity levels.


Prerequisites

Before uploading maintenance tasks, confirm you have:

  1. An existing asset configuration (for example Wind Turbine Generator (WTG)) in your experiment/case

  2. Access permissions to edit the asset

  3. A properly formatted CSV or Excel file containing your maintenance data

  4. Bookkeeping categories configured (used to categorize cost types for tasks)


File format requirements

Required column: Item identifier

Your file must include a column named Item identifier, which defines the task type for each row:

  • Scheduled or Scheduled Maintenance (scheduled tasks)

  • Corrective or Corrective Maintenance (corrective tasks)

File structure

  • Row 1: Column headers

  • Row 2+: Task rows

  • Formats supported: CSV, Excel (.xlsx, .xls)

  • Encoding: UTF-8 recommended


Scheduled maintenance task columns

When uploading scheduled maintenance tasks, include the fields below.

Required fields

Column name Description Example
Item identifier Task type Scheduled
Task name Maintenance task description Annual inspection
Book keeping Bookkeeping category for cost tracking Preventive maintenance
Start date Date the maintenance campaign begins 2024-01-15
Recurrence Frequency in days 365
Repair time Duration (hours) 8
Spare part cost Spare parts cost 5000
Consumables and other costs Additional costs 1000

Personnel fields

The system supports multiple technician types. Columns typically capture:

  • Number of technicians per type required

  • Personnel can be provided via separate columns (depending on your template/setup)

Optional fields

You may also include:

  • Production impact: impact on production while work is performed (0–1)

  • Time series data: for varying repair times across years


Corrective maintenance task columns

For corrective maintenance tasks (component failures), include the following.

Required fields

Column name Description Example
Item identifier Task type Corrective
Task name Component/failure description Gearbox failure
Book keeping Bookkeeping category Major corrective
Annual failure rate Failures per year 0.05
Failure severity Severity level Critical / Major / Minor
Probability distribution Distribution type Weibull / Exponential
Beta Weibull shape parameter 1.5

Operational parameters

Column name Description Example
Repair time Repair duration (hours) 48
Lead time Waiting time for parts (hours) 720
Impact on failure Production loss 1.0
Impact on failure while working Production during repair 1.0

Phase-based repair time (optional)

For a more detailed work breakdown, include:

  • Inspection time (hours)

  • Preparation time (hours)

  • Preparation crew size

  • Replacement time (hours)

  • Replacement crew size

  • Finalization time (hours)

  • Finalization crew size

Advanced settings (optional)

  • Cable end: for cable-related tasks (for example END)

  • Disconnect power impact: whether the task requires power shutdown (true/false)

  • Allow scheduled work while waiting: whether other tasks can proceed during lead time have to be set in the UI.


Upload process

Step 1: Navigate to asset configuration

  1. Open your Experiment/Case

  2. Go to Infrastructure or Assets

  3. Select the target asset

Step 2: Access task import

  1. Click Import Tasks / Upload Maintenance Tasks

Step 3: Map your columns

  1. Upload the CSV/Excel file

  2. Use the column mapping interface to match your columns to the system fields:

    • Map Task name → your task description column

    • Map Item identifier → your task type column

    • Map Book keeping → your bookkeeping/category column

    • Map the remaining required fields

Step 4: Review and import

  1. Click Import / Upload

  2. The system will:

    • Delete existing tasks on the asset (overwrite)

    • Validate each row

    • Create scheduled maintenance services

    • Create corrective maintenance components and failure data

    • Create default technician roles if needed

Step 5: Review import results

After import you’ll see:

  • Total rows processed

  • Number of scheduled tasks imported

  • Number of corrective tasks imported

  • Row-level error messages (with row numbers)


Important notes

Data overwrite warning

Importing tasks for an asset will:

  1. Delete all existing tasks for that asset first

  2. Perform a full replacement, not an additive merge

  3. Require your file to contain every task you want to keep

Task types supported

The system supports O&M maintenance tasks for:

  • Turbines (WTG)

  • Substations

  • Monopiles

  • Transition pieces

  • Jackets

  • Mooring lines and anchors

  • Export and inter-array cables

Bookkeeping categories

  • Must exist before import

  • Contact an administrator if categories are missing

  • Used to group and report costs in simulations and reporting

Technicians

The system automatically creates five default technician roles:

  • Service technician

  • Service technician 2

  • Service technician 3

  • Service technician 4

  • Service technician 5


Troubleshooting

Common errors

Invalid value for “Item identifier”

  • Fix: Ensure each row contains Scheduled or Corrective (or the longer supported variants).

Failed to process row X: Missing required field

  • Fix: Confirm all required columns exist and are mapped correctly.

Unable to insert Scheduled Maintenance into the database

  • Fix: Validate date formats and numeric fields.

Bookkeeping category not found

  • Fix: Ensure bookkeeping category names match exactly (including capitalization, if your system treats it as case-sensitive).

Import failed completely

If the import fails:

  1. Confirm file type (CSV/Excel)

  2. Ensure headers are in the first row

  3. Remove empty required fields

  4. Check for problematic special characters

  5. Retry with a smaller subset first


Example template (minimal)

Item identifier,Task name,Book keeping,Start date,Recurrence,Repair time,Spare part cost,Consumables and other costs
Scheduled,Annual inspection,Preventive maintenance,2024-01-15,365,8,5000,1000
Scheduled,Blade cleaning,Minor maintenance,2024-03-01,180,4,0,500
Corrective,Gearbox failure,Major corrective,,0.05,48,150000,10000
Corrective,Generator fault,Major corrective,,0.08,24,80000,5000

Note (corrective maintenance):

  • Leave Start date and Recurrence empty (or omit them)

  • Include Annual failure rate plus distribution parameters instead



Need help?

If you run into issues:

  1. Review import feedback error messages

  2. Verify column mappings

  3. Validate data types and formats

  4. Contact support with:

    • The first few rows of your import file

    • The error messages

    • The asset and experiment/case details


Advanced: Understanding the data flow

What happens during import

  1. Authentication and permission checks

  2. CSV/Excel parsing into internal format

  3. Column mapping

  4. Row validation

  5. Cleanup: existing tasks/components/services deleted

  6. Default technician creation (if needed)

  7. Bookkeeping category lookup

  8. Task creation:

    • Scheduled: creates Service records

    • Corrective: creates Component + ComponentFailureData records

  9. Import summary and feedback generation