> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Understanding Work Orders
> Understand work orders in AssetOps and how they are administered
A work order is a single, trackable unit of work, such as a routine maintenance task, ad hoc repair, or inspection.
It represents an individual task that is created, assigned, and completed as part of a maintenance activity.
Work orders in AssetOps can be created as one-time or recurring tasks, depending on the maintenance activity you need to complete.
They can be assigned to internal staff or external vendors, with clearly defined due dates and estimated effort.
## Maintenance Types
In AssetOps, work orders are created around predefined maintenance types that ultimately determine the type of work order you create based on the maintenance activity you need to complete. These predefined maintenance types include **corrective maintenance**, **preventive maintenance**, and **inspections**.
These predefined maintenance types allow for both **reactive** maintenance, which addresses issues or failures as they occur, and **proactive** maintenance, which is planned in advance to prevent problems and maintain asset health.
* The **Corrective Maintenance** type refers to maintenance tasks performed on assets that are faulty or and not functioning properly.
It focuses on restoring asset functionality, minimizing downtime, and returning operations to normal as quickly as possible.
* The **Preventive Maintenance** type refers to maintenance tasks carried out routinely on assets to prevent failures and keep them operating efficiently.
It focuses on reducing the likelihood of failures and maintaining asset health through routine checks and servicing.
* The **Inspection** type refers to maintenance tasks aimed at checking and assessing conditions to identify issues or ensure compliance with standards.
It focuses on assessing asset condition and enabling early detection of potential issues.
```mermaid actions={false} theme={null}
---
config:
theme: neutral
---
flowchart LR
subgraph s1["Type Characteristics"]
B1["Reactive"]
B2["Fix after failure"]
end
subgraph s2["Type Characteristics"]
C1["Proactive"]
C2["Scheduled upkeep"]
end
subgraph s3["Type Characteristics"]
E1["Proactive"]
E2["Condition assessment"]
end
A["Maintenance Types"] --->|type| B["Corrective Maintenance"] & C["Preventive Maintenance"] & E["Inspection"]
B -->|approach| B1
B -->|purpose| B2
C -->|approach| C1
C -->|purpose| C2
E -->|approach| E1
E -->|purpose| E2
B1:::Rose
C1:::Class_01
E1:::Class_01
B:::Sky
C:::Sky
E:::Sky
classDef Rose stroke-width:1px, stroke-dasharray:none, stroke:#FF5978, fill:#FFDFE5, color:#8E2236
classDef Sky stroke-width:1px, stroke-dasharray:none, stroke:#374D7C, fill:#E2EBFF, color:#374D7C
classDef Class_01 fill:#B0E4CC, color:#285A48, stroke:#285A48
```
## Work Order Types
AssetOps supports two work order types, **generic** and **scheduled**, and the one you use depends on the maintenance activity you need to complete. Each type is tied to at least one of the predefined [maintenance types](/products/assetops/quickstart/work-orders#maintenance-types) in AssetOps.
### Generic Work Orders
In AssetOps, generic work orders are used to create one-time tasks for maintenance activities, primarily focusing on resolving faults and restoring normal asset operation.
Generic work orders support the Corrective Maintenance type, enabling teams to swiftly address area related issues or faulty assets and manage unplanned maintenance.
```mermaid actions={false} theme={null}
---
config:
theme: neutral
---
flowchart LR
subgraph s1["Work Order Types"]
B2["Corrective Maintenance"]
end
subgraph s3["Assets"]
I["Asset 1"]
I1["Asset 2"]
I2["Asset 3"]
end
subgraph s4["Areas"]
AR1["Area 1"]
AR2["Area 2"]
AR3["Area 3"]
end
A["AssetOps"] --- B["Work Orders"]
B -- Work Order Type --- B2
B2 -- create work order for --- I & I1 & I2 & AR1 & AR2 & AR3
B2:::Sky
I:::Rose
I1:::Rose
I2:::Rose
AR1:::Peach
AR2:::Peach
AR3:::Peach
classDef Sky stroke-width:1px, stroke-dasharray:none, stroke:#374D7C, fill:#E2EBFF, color:#374D7C
classDef Rose stroke-width:1px, stroke-dasharray:none, stroke:#FF5978, fill:#FFDFE5, color:#8E2236
classDef Peach stroke-width:1px, stroke-dasharray:none, stroke:#FBB35A, fill:#FFEFDB, color:#8F632D
```
### Scheduled Work Orders
In AssetOps, schedules are used to generate recurring work orders and ensure that routine maintenance activities are completed consistently and on time.
Scheduled work orders support two maintenance types, Preventive Maintenance and Inspections, enabling teams to proactively manage recurring maintenance jobs and keep assets in optimal condition.
```mermaid actions={false} theme={null}
---
config:
theme: neutral
---
flowchart LR
subgraph s1["Work Order Types"]
B1["Preventive Maintenance"]
B2["Inspection"]
end
subgraph s2["Assets"]
A1["Asset 1"]
A2["Asset 2"]
A3["Asset 3"]
end
subgraph s3["Inspection Types"]
I["Assets"]
I1["Areas"]
I2["General"]
end
A["AssetOps"] --- B["Schedules"]
B -- Work Order Type --- B1 & B2
B1 -- scheduled maintenance --- A1 & A2 & A3
B2 -- scheduled inspection --- I & I1 & I2
B1:::Sky
B2:::Sky
A1:::Rose
A2:::Rose
A3:::Rose
I:::Rose
I1:::Peach
I2:::Class_02
classDef Sky stroke-width:1px, stroke-dasharray:none, stroke:#374D7C, fill:#E2EBFF, color:#374D7C
classDef Ash stroke-width:1px, stroke-dasharray:none, stroke:#999999, fill:#EEEEEE, color:#000000
classDef Peach stroke-width:1px, stroke-dasharray:none, stroke:#FBB35A, fill:#FFEFDB, color:#8F632D
classDef Aqua stroke-width:1px, stroke-dasharray:none, stroke:#46EDC8, fill:#DEFFF8, color:#378E7A
classDef Rose stroke-width:1px, stroke-dasharray:none, stroke:#FF5978, fill:#FFDFE5, color:#8E2236
classDef Class_02 fill:#B0E4CC, color:#285A48, stroke:#285A48
```