# Kanoa Maintenance Training

This section is focused on Kanoa Maintenance: planning maintenance work, getting it to technicians at the right time, recording what they did, and measuring how well the maintenance team is keeping up.

Because Kanoa Maintenance runs inside Kanoa MES, work orders are raised against the same assets you modeled in Kanoa Ops, and can be generated from the same production data, such as run hours and counts.

Kanoa Maintenance separates **planning** from **execution**:

| Planning | Execution |
|---|---|
| A **work order template** says what maintenance should happen, on which asset, with which procedure | A **work order** is one real job generated from the template, assigned to a technician |
| A **schedule type** (One Time, Recurring or Condition) says when work orders are generated | Each work order moves through statuses such as Open, Assigned, In Progress and Completed |

::embed-section{src="../../kanoa-cmms.md" collapsed="true" summary="Reference Materials: Kanoa Maintenance - What Maintenance does and how it fits into Kanoa MES."}

You'll keep CoreForge's **Machine 1** running:

- **Maintenance Setup:** set up the maintenance lookups and a technician, and write a preventive maintenance procedure.
- **Work Orders:** raise a one-time repair, work it through to completion, then schedule recurring and run-hour-based maintenance.
- **Maintenance Analytics:** read the maintenance KPIs, backlog and labor hours.

## Before you start

- Complete [Kanoa Ops Training](../3-training-ops/index.md), or at least [Base Configuration](../3-training-ops/01-base-configuration/index.md). Machine 1 must be running in the simulator for the run-hour lesson.
- Your gateway needs a Kanoa Maintenance license (a trial license is fine).
- Maintenance screens are under **Maintenance** (Work Orders, Maintenance Analytics) and **Configuration → Maintenance** (Work Orders, Procedures).